Bug#981407: sysv-generator is really annoying with an eccessive verbosity

[Francesco P. Lovergine]

On Tue, Feb 16, 2021 at 12:17:49AM +0100, Michael Biebl wrote:
>Am 02.02.21 um 10:11 schrieb Francesco P. Lovergine:
>>Well, the truly annoying thing is that it warns even for init 
>>scripts disabled, but never removed (sometimes on purpose, sometimes 
>>due to package errors). I discovered a few of them still around 
>>since years, and reduced
>>a bit the noisei by purging.
>
>But isn't this a good thing, that it shows you that there is old cruft?
>

Yes, but while it is reasonable at upgrade time, it is annoying at every
restart of services.

> For sure this system is up since 28th of
>>Jan and dmesg shows
>>only messages after 30th of Jan currently. So generally, at every restart
>>of services the syslog is populated with those warnings in good quantity.
>>
>>Any system upgraded several times and/or used for development will present
>>tons of this warnings during its life cycle. I know upstream already 
>>refused to take in consideration the possibility of on/off that 
>>warns by option. At least, using debug priority would move those 
>>warns to a different log file in default configuration, not too bad.
>
>Fwiw, I don't think either that an On/Off switch would be a good idea.
>
>Assuming we remove the old SysV generator at some point, we do need to 
>warn users in advance, so they can prepare. If we downgrade those 
>messages to debug, I fear users will never see them and take 
>appropriate steps.
>

Well, a skilled admin will simply add a filtering expression for rsyslog to 
send all those messages to /dev/null. A newbie shall have just some more good 
reasons to curse. I still think that using debug priority is a reasonable 
choice for both them.

-- 
Francesco P. Lovergine