Re: Strange syslog behaviour [Solved]

2022-10-17 Thread Wayne Sallee
 Original Message  *Subject: *  Re: Strange syslog behaviour [Solved] *From: * Tixy *To: * Debian-user *CC: * *Date: *  2022-10-16  12:40 PM On Sun, 2022-10-16 at 09:09 -0400, Wayne Sallee wrote: It would be nice if updates presented "old file",

Re: Strange syslog behaviour [Solved]

2022-10-17 Thread Wayne Sallee
 Original Message  *Subject: *  Re: Strange syslog behaviour [Solved] *From: * Charles Curley *To: * Debian Users *CC: * *Date: *  2022-10-16  11:09 AM When I do an upgrade I run the upgrade in one terminal, and have Emacs running in another. As these

Re: Strange syslog behaviour [Solved]

2022-10-16 Thread David Wright
On Sun 16 Oct 2022 at 09:09:36 (-0400), Wayne Sallee wrote: > I wrote: > > On Sat 15 Oct 2022 at 13:59:18 (-0400), Wayne Sallee obfuscated the > > following with HTML: > > > > > Jeremy Ardley, did you update your code from " invoke-rc.d rsyslog rotate > > > > /dev/null" to > > > "/usr/lib/rsyslo

Re: Strange syslog behaviour [Solved]

2022-10-16 Thread Tixy
On Sun, 2022-10-16 at 09:09 -0400, Wayne Sallee wrote: > It would be nice if updates presented "old file", "new file", "combined > file"; choice: (1), (2), (3). It does offer several choices, one of them is to show a 'diff' of the old and new files. Only you can know what changes you made and wan

Re: Strange syslog behaviour [Solved]

2022-10-16 Thread Charles Curley
On Sun, 16 Oct 2022 09:09:36 -0400 Wayne Sallee wrote: > > You rejected the new file, which is why it was instead written to > > /etc/logrotate.d/rsyslog.dpkg-dist (which you could have safely > > left or removed—it's harmless). > > Yes, I rejected the new file, causing the other file to be th

Re: Strange syslog behaviour [Solved]

2022-10-16 Thread Wayne Sallee
 Original Message  *Subject: *  Re: Strange syslog behaviour [Solved] *From: * David Wright *To: * Debian-user *CC: * *Date: *  2022-10-16  01:27 AM On Sat 15 Oct 2022 at 13:59:18 (-0400), Wayne Sallee obfuscated the following with HTML: Jeremy Ardley, did

Re: Strange syslog behaviour [Solved]

2022-10-15 Thread David Wright
On Sat 15 Oct 2022 at 13:59:18 (-0400), Wayne Sallee obfuscated the following with HTML: > Jeremy Ardley, did you update your code from " invoke-rc.d rsyslog rotate > > /dev/null" to > "/usr/lib/rsyslog/rsyslog-rotate"? I've added a new post to that part of the thread. I think your problem conc

Re: Strange syslog behaviour [Solved]

2022-10-15 Thread David Wright
While I was composing my second post in this thread, On Tue 12 Apr 2022 at 06:38:34 (+0800), Jeremy Ardley wrote: > On 11/4/22 12:00 pm, Jeremy Ardley wrote: > > On 11/4/22 11:46 am, David Wright wrote: > > > > > > There are tabooext and taboopat directives for ignoring files in > > > logrotated.d

Re: Strange syslog behaviour [Solved]

2022-10-15 Thread Greg Wooledge
On Sat, Oct 15, 2022 at 01:59:18PM -0400, Wayne Sallee wrote: >edit /etc/logrotate.d/rsyslog >Change from > invoke-rc.d rsyslog rotate > /dev/null >to > /usr/lib/rsyslog/rsyslog-rotate Hmm. In /etc/init.d/rsyslog (which is what the old command c

Re: Strange syslog behaviour [Solved]

2022-10-15 Thread Wayne Sallee
Jeremy Ardley, did you update your code from " invoke-rc.d rsyslog rotate > /dev/null" to "/usr/lib/rsyslog/rsyslog-rotate"? So I got my servers straitened out, I think. I will know tomorrow. For anyone else running into this problem, the problem was

Re: Strange syslog behaviour [Solved]

2022-10-15 Thread Greg Wooledge
On Sat, Oct 15, 2022 at 10:13:05AM -0400, Wayne Sallee wrote: >  Original Message  > *Subject: *  Strange syslog behaviour [Solved] > *From: * Jeremy Ardley > > Anyway long story short, at some stage some package updates must have > > written an

Re: Strange syslog behaviour [Solved]

2022-10-15 Thread Wayne Sallee
Thanks for pointing this out. I just noticed this problem a few days ago. Wayne Sallee wa...@waynesallee.com http://www.WayneSallee.com  Original Message  *Subject: *  Strange syslog behaviour [Solved] *From: * Jeremy Ardley *To: * Debian-user *CC: * *Date

Re: Strange syslog behaviour [Solved]

2022-04-11 Thread Jeremy Ardley
On 12/4/22 6:38 am, Jeremy Ardley wrote: And discovered that /etc/logrotate.d/inetutils-syslogd was also being loaded. It had duplicates of many entries in /etc/logrotate.d/rsyslog All I wanted was ping _traceroute_ but I got a world of hurt as well! *this* seems likely to solve the probl

Re: Strange syslog behaviour [Solved]

2022-04-11 Thread David Wright
On Mon 11 Apr 2022 at 12:00:38 (+0800), Jeremy Ardley wrote: > On 11/4/22 11:46 am, David Wright wrote: > > > > There are tabooext and taboopat directives for ignoring files in > > logrotated.d, and I would have thought it reasonable to exclude > > these sorts of housekeeping files by default, bec

Re: Strange syslog behaviour [Solved]

2022-04-11 Thread Jeremy Ardley
On 11/4/22 12:00 pm, Jeremy Ardley wrote: On 11/4/22 11:46 am, David Wright wrote: There are tabooext and taboopat directives for ignoring files in logrotated.d, and I would have thought it reasonable to exclude these sorts of housekeeping files by default, because they're very likely to conta

Re: Strange syslog behaviour [Solved]

2022-04-10 Thread Jeremy Ardley
On 11/4/22 11:46 am, David Wright wrote: There are tabooext and taboopat directives for ignoring files in logrotated.d, and I would have thought it reasonable to exclude these sorts of housekeeping files by default, because they're very likely to contain some duplication. I would file a bug agai

Re: Strange syslog behaviour [Solved]

2022-04-10 Thread David Wright
On Mon 11 Apr 2022 at 10:07:53 (+0800), Jeremy Ardley wrote: > I have systems (armbian) that had anomalous behaviour. > > This included sometimes writing to /var/log/syslog.1 rather than to > /var/log/syslog (which was created, but zero size) > > Additionally the logrotate was happening daily or

Strange syslog behaviour [Solved]

2022-04-10 Thread Jeremy Ardley
I have systems (armbian) that had anomalous behaviour. This included sometimes writing to /var/log/syslog.1 rather than to /var/log/syslog (which was created, but zero size) Additionally the logrotate was happening daily or twice daily when seemingly configured for weekly rotates Anyway lon