On Fri, Jan 06, 2006 at 03:19:58AM -0500, sean finney wrote: > a while back, i noticed that there seems to be some rather inconsistent > behaviour wrt doing "/etc/init.d/foo reload". > > typically this results in a HUP or something similar sent to the daemon in > question, causing it to reload configuration, but in some cases the > init script's actions are identical to what would happen with the > "restart" target.
[..] > reload > > cause the configuration of the service to be reloaded without > actually stopping and restarting the service, [..] > my take on this is that, while optional, the reload target must not > stop and start a service if implemented in an init script. it would > then logically follow that reload must not start a service which is > not running. > > is my interpretation of this correct, or am i over-analyzing things? I agree with your interpretation... and believe that most init.d scripts behave this way. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
