On 22-Feb-2006, Dan Jacobson wrote: > I wish > # /etc/init.d/some_package restart > would be mandatory to act just like > # /etc/init.d/some_package stop > # /etc/init.d/some_package start
What does "act like" mean? I presume you *don't* mean that "restart" should always stop and then start the service, that would not be desirable. Many services have the capability to restart without stopping and starting; that's why the separate command is there. If you mean that "restart" should behave like a transaction that leaves the service in the same state as a transaction involving "stop" followed by "start", that's more understandable; but still ignores the times when the sysadmin deliberately *doesn't* want the same behaviour. > # /etc/init.d/wwwoffle restart > Stopping HTTP cache proxy server: wwwoffled..... ok. > Starting HTTP cache proxy server: wwwoffled (offline mode) done. > WWWOFFLE Now In Autodial Mode > # /etc/init.d/wwwoffle restart > # /etc/init.d/wwwoffle stop > Stopping HTTP cache proxy server: wwwoffled ok. > # /etc/init.d/wwwoffle start > Starting HTTP cache proxy server: wwwoffled (offline mode) done. > > Yikes. Autodial mode. Never expected that... This is indeed a problem; it doesn't seem reasonable for a feature to be enabled on "restart" that is not enabled when "start" is invoked. Can you suggest wording that would forbid the behaviour you describe, while allowing things like "bind9 restart" to invoke the process's native restart mechanism? -- \ "I was married by a judge. I should have asked for a jury." -- | `\ Groucho Marx | _o__) | Ben Finney <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
