On Thu, Aug 27, 2009 at 01:54:08AM -0400, Joey Hess wrote: > /etc/init.d/privoxy start|stop returns without printing anything. > > Apparently it does this because /proc/cmdline contains "quiet", > but that should have nothing to do with an init script being run > at the command line. > > Policy is quite clear: > > * When daemons are started > > If the script starts one or more daemons, the output should look > like this (a single line, no leading spaces): > Starting <description>: <daemon-1> ... <daemon-n>.
Actually, this behaviour is the same as /etc/init.d/skeleton, provided by the initscripts package since 2.86.ds1-13. Looking for the "quiet" option to set VERBOSE value comes from initscripts 2.86.ds1-21. An quick archive wide searh on today's unstable (amd64) resulted in positive hits searching "VERBOSE.*no.*Starting" for the following packages: ample amule-daemon auditd bird bird6 chillispot citadel-server citadel-webcit console-tools ddclient deejayd dovecot-common fail2ban flumotion fso-frameworkd fso-gpsd fuse-utils glusterfs-server gridengine-exec gridengine-master hdapsd initscripts iodine ipkungfu ipmitool kbd krb5-admin-server krb5-kdc lldpd mailscanner mandos mumble-server nfdump nodm openafs-fileserver pcscd privoxy root-system-proofd root-system-rootd root-system-xrootd sec shishi-kdc silcd snmptt steam strongswan strongswan-starter teamspeak-server webgui wicd wu-ftpd So if there really is a policy issue, looks like it started to grow. :D Maintainers of the initscripts package, could your comments on this? Cheers, -- Jérémy Bobbio .''`. [email protected] : :Ⓐ : # apt-get install anarchism `. `'` `-
signature.asc
Description: Digital signature
