also the problem is not that service wouldn't be up. Service IS UP but
it's not connected to freenode (nothing upstart could fix) it's
problem in wm-bot source code. It actually can reconnect when
connection die, but problem is that wm-bot is using bouncer, and this
bouncer doesn't forward signal when remote server disconnect. This
needs to be fixed by some more coding and that again requires some
other petan who isn't that lazy :)
On Fri, Oct 11, 2013 at 10:49 AM, Petr Bena <benapetr(a)gmail.com> wrote:
I agree, but it requires some work, which I am too
lazy for,
especially since manual restart is almost as hard as typing sudo
service wm-bot restart, it's just like 2 different commands
writing whole upstart script for bouncers and core is lot of work...
Maybe when I have a lot of time I could think of that :P
On Fri, Oct 11, 2013 at 8:45 AM, Antoine Musso <hashar+wmf(a)free.fr> wrote:
> Le 11/10/13 09:24, Petr Bena a écrit :
>> wm-bots components are not configured as services, so restarting them
>> is not as easy as doing sudo service wm-bot restart
>
> Seems you might want to make them upstart services. That will ease
> maintenance, and AFAIK, Ubuntu upstart would even make sure the service
> is up and running.
>
> --
> Antoine "hashar" Musso
>
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
>
https://lists.wikimedia.org/mailman/listinfo/wikitech-l