On Sun, 14 Jul 2002, Bernd Eckenfels wrote: > After short discussion on debian-devel it is obvious, that the section on > policy about the restart and force reload of daemons in init.d scripts could
I agree with that. We do not define what force-reload does if the service is not running [and it does indeed support configuration reloading]. > be more verbose. There are two options, one is to document the current > behavior (which can be found in the skel script) the other is a change in The current behaviour is not consistent. There are packages doing it either way. THAT is the real problem. > the behavior, which is less desirable. Oh, quite the opposite. It is *desirable* to have force-reload defined as "force a full configuration reload of the service, if it is running. Fail otherwise". But the code to do so is more complicated. > reporting an error. This behavior is also allowed for 'force-reload' if it > is linked to the restart method. Other methods of 'force-reload' (like > signalling or null implementation, because of automatic config reload) do > not need to start a terminated process. In this case a non null error level > should be returned. I object to this change. We should choose a method for force-reload, and have it consistently implemented. We probably should also try to get the LSB to fix "force-reload" in their standard as well. They have exactly the same problem: "force-reload: cause the configuration to be reloaded if the service supports this, otherwise restart the service" -- LSB 1.3 draft What should be done if the service supports the reload, but is not running? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
