Bugzilla – Bug 99540
/etc/init.d/boot status does funny things
Last modified: 2007-06-06 17:16:34 UTC
the /etc/init.d/boot script does not check if it is started with a LSB standard parameter, like "status". running it in an already running system does a lot of bad things, so this should be prevented. alternatively (preferably) move non-sysv5 init files out of /etc/init.d
vaild part: /etc/init.d/boot is missing some targets, ok. questionable: there are quite some rc-scripts in /etc/init.d that will have all kinds of effects if started/stopped arbitrarily ... keeping "boot" and "rc" in /etc/init.d does make sense IMHO, but maybe we should implement some handling for "status/start/stop/...", at least to ignore them. Werner, normally this is your area, what do you think ?
there are not that many scripts in /etc/init.d that are not LSB compliant init scripts. Anyway, this bugreport is not about starting / stopping arbitarily doing bad things: thats obvious. However, "query-only" targets like "status" should either not be supported, or not doing anything, and invoking those /etc/init scripts without one of the standard parameters should invoke the "Usage: .." output instead of doing something. At least thats the behaviour the user expects IMHO
/etc/init.d/boot and /etc/init.d/rc are not boot script which handle arguments and even in future those script will not do that. Do never call /etc/init.d/boot or /etc/init.d/rc if you do not know what they are doing. The script /etc/init.d/boot is for system linitialization and executed during system boot, the script /etc/init.d/rc is for changing the current runlevel to an other runlevel. For a description see manual page init.d(7) btw: users which want to use scripts for checking status or restarting a service should use the rc<service> interface.