conf-change reload issue, ui suggestions...

[Scott James Remnant]

On Thu, Mar 29, 2012 at 8:07 PM, David Jeske <davidj at gmail.com> wrote:

> On Thu, Mar 29, 2012 at 7:21 PM, Scott James Remnant <scott at netsplit.com>wrote:
>
>> By design this uses the old version of the configuration because the
>> issuer may not know that the service has been changed and may be relying on
>> features of the old version of the service no longer present in the new.
>>
>
> Is there some discussion you can point me to, or reasoning you can offer
> as to why this common-unix behavior was changed in upstart?
>
>
Because I wanted it to work that way.


> All of the following...
>
> apachectl restart           # custom script
> /etc/init.d/httpd restart   # SysV style
> svc -k httpd                # daemon tools
>
> Mean "stop if running; start with new config".
>
>
Yup, and they're all wrong. Some of them even START apache when it wasn't
already running, and that's clearly wrong.

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/upstart-devel/attachments/20120329/d2887d00/attachment.html>