clone 672218 -1 reassign -1 sysv-rc retitle -1 sysv-rc: policy-rc.d/invoke-rc.d should better support unknown actions thanks
On Wed, Jan 23, 2013 at 01:07:07PM +0100, Michael Biebl wrote: > On 23.01.2013 12:41, Paul Slootman wrote: > > On Wed 23 Jan 2013, Michael Biebl wrote: > >> On 23.01.2013 11:47, Paul Slootman wrote: > >> > >>> The message is given by invoke-rc.d, NOT by the init script! > > > >> So it's the policy-rc.d layer which is causing that warning (not error) > >> message. What are you suggesting I should take into account here? > >> The only thing I can do is to stop using that crappy invoke-rc.d > >> altogether. > > Alternatively the sysv-rc people might want to provide some hook for > > invoke-rc.d so that policy-rc.d might indicate what to do with unknown > > actions. I've been looking but can't find any way of suppressing the > > invoke-rc.d output via the policy layer. > > > > invoke-rc.d rsyslog rotate 2>&1 > /dev/null | grep -v 'action rotate is > > unknown' >&2 > > That is super-ugly too. > I'm > more inclined to ditch the usage of invoke-rc.d altogether and simply > call the sysv init script directly or even drop the "action" from the > sysv init script and run "kill -SIGHUP $(cat /var/run/rsyslogd.pid)" > directly in the logrotate script. I'll have to look at the policy-rc.d stuff to see if we can sensibly handle unknown actions. However, I would suspect it's difficult to do so meaningfully primarily because they are unknown, unless we just allow everything (which appears to be the default). Until (and if) this is made possible, it certainly looks like invoke-rc.d is probably not the ideal interface to use here. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
