-
pjusticeCould someone explain to me the rationale behind running logadm every hour instead of daily?
-
jperkinI presume to give logs that are configured to be a certain size have a chance of achieving that if they grow quickly, I've never personally been a fan of that though
-
pjusticeDefinitely been causing me assorted heartburn.
-
jperkinI've always had my own logrotate script run at 23:59 (so that the date is correct), split daily and archive foo_YYYYMMDD.gz
-
jperkinmuch easier for historical searching
-
pjusticeGiven logadm.conf says "logadm typically runs early every morning via an entry in root's crontab (see crontab(1))", it's extra deceptive.
-
pjusticeHow much pain am I in for if I replace logadm.conf with one that lacks size limits, and the crontab entry with a once-daily?
-
jperkinI think "it depends", there's always a chance some daemon ends up logging too much and fills a disk.
-
pjusticeEh, that's not what I'm worried about. More like upgrades and such.
-
jperkingz or non-gz?
-
pjusticenon
-
jperkinunaffected by upgrades then, also much less to worry about compared to all the extra stuff running in gz
-
jperkinmy non-gz disables logadm completely
-
jperkinfor aforementioned reasons
-
pjusticeThanks for the consult!