Conreol: tags -1 -moreinfo Hi Dimitris, hi Andrew,
On Fri, 14 Feb 2025 17:40:28 +0200 "Dimitris T." <dimit...@stinpriza.org> wrote: > > Could you please look again and see if logrotation and/or cron jobs > > are actually skipped due to this error (look at the expected action > > in the filesystem)? > > > you're correct, apart from this annoying daily "spam" logrotate/cron > error, nothing else is affected. also tested with daily anacron. thanks for confirming this :) > > (but in general, i would prefer it completely "fixed" = no > errors/spam :) ) ok, I understand. > > -- > > something relative i noticed. > > if i set /etc/logrotate.d/rsyslog -> rsyslog.disabled (so only one > logrotation script for rsyslog ), then logrotate completes > succesfully. but... > > when some runit-services trigger is run following some package > upgrade (eg. rsyslog), then, aa-rsyslog-runit is also renamed to > aa-rsyslog-runit.disabled.. (?!) and there is no (rsys)log rotation!! On Fri, 14 Feb 2025 19:03:48 +0000 Andrew Bower <and...@bower.uk> wrote: > > (1) Ah, looking at d/runit-services.postinst, that looks fixable. > runit-services is trying to make sure that if it adds this file and > rsyslog's rotation is already disabled, then the new file should be > installed as disabled, too. from coding point of view this is fixable, the issue is more on the social and policy side. in short, we risk to be forced to revert due to an escalation from rsyslogd maintainer.. well, there is no reply in #1079270 so as long as it doesn't break usage under systemd maybe he doesn't care. I'll see what I can do.. > > (2) Install an 'inotifywatch' on the log files being moved by > logrotated and then perform sv hup. Yeah... that's excessive! I confess that I considered this already for a second or so when had to fix #1079268, but them, hum, better not.. Another solution that I considered is to have rsyslogd log to stdout and catch logs with svlogd, similar to socklog-run, but the problem is that * it requires editing rsyslog config file on the fly, so it's brittle * users will likely be surprised to find system logs in /var/log/runit/rsyslogd so I discarded that too. Best, Lorenzo
