conf-change reload issue, ui suggestions...
Scott James Remnant
scott at netsplit.com
Fri Mar 30 03:39:18 UTC 2012
On Thu, Mar 29, 2012 at 8:37 PM, David Jeske <davidj at gmail.com> wrote:
> n Thu, Mar 29, 2012 at 8:20 PM, Scott James Remnant <scott at netsplit.com>wrote:
>
>> Yup, and they're all wrong. Some of them even START apache when it wasn't
>> already running, and that's clearly wrong.
>>
>
> I can see why lacking a mechanism like upstart-restart is imprecise, and
> why adding that mechanism is clearly a 'good thing'. I don't, however, see
> anything "wrong" with making common user-operations convenient.
>
> I don't care what it's called, but failing to provide this capability is
> kinda missing the #1 thing some reasonable set of users do (as evidenced by
> the fact that all the other tools are built to do it). We certainly need it
> for our usage.
>
>
Which is why you can do it, as I said in my original e-mail:
initctl stop myprog && initctl start myprog
> Do you have opposition to something like "initctl fstart" (i.e.
> flush/force start) that basically stops if started, forces a config reload,
> and then starts?
>
>
The service(8) wrapper in Ubuntu already provides this for (I think)
force-restart
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/cbc9313d/attachment.html>
More information about the upstart-devel
mailing list