18:33:35 <pjustice> Could someone explain to me the rationale behind running logadm every hour instead of daily?
18:38:31 <jperkin> I 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
18:39:43 <pjustice> Definitely been causing me assorted heartburn.
18:39:53 <jperkin> I've always had my own logrotate script run at 23:59 (so that the date is correct), split daily and archive foo_YYYYMMDD.gz
18:40:11 <jperkin> much easier for historical searching
18:44:22 <pjustice> Given logadm.conf says "logadm typically runs early every morning via an entry in root's crontab (see crontab(1))", it's extra deceptive.
18:46:03 <pjustice> How 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?
18:50:46 <jperkin> I think "it depends", there's always a chance some daemon ends up logging too much and fills a disk.
18:57:06 <pjustice> Eh, that's not what I'm worried about.  More like upgrades and such.
19:00:08 <jperkin> gz or non-gz?
19:00:34 <pjustice> non
19:01:35 <jperkin> unaffected by upgrades then, also much less to worry about compared to all the extra stuff running in gz
19:02:26 <jperkin> my non-gz disables logadm completely
19:02:40 <jperkin> for aforementioned reasons
19:04:33 <pjustice> Thanks for the consult!