Hi, I will have a look at how we can do this with the current scripts developed, as currently a daemon service starts (nodemanager in this case that does not use any daemin tools other than itself) and attaches to the root process.
It seems i am coding to solve an issue that does not exist if run directly on the host. Regards Nicholas Irving On 21 Apr 2015 8:25 am, "Brian Coca" <[email protected]> wrote: > If these are services they should really use a service manager like > init, systemd, upstart, daemontools, supervisor, monit, runit, etc. > 'manually' starting services is unreliable, pollutes their environment > with yours and makes checking them and/or stopping them also > unreliable. > > > -- > Brian Coca > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAJ5XC8nbyOuSou%2BDfheC82_pc83RTLKrONT7J435tYr2Rrz8sw%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAMqs2CYNesbMZzmKbhtoyMcRYgwdoW41v7AK8EexCYF_-o_vJg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
