Loading…
 ssantos
Translation uploaded |
Context
Master subprocess watcher.Start and watch the configured runners, ensuring that they stay alive and
kicking. Each runner is forked and exec'd in turn, with the master waiting
on their process ids. When it detects a child runner has exited, it may
restart it.
The runners respond to SIGINT, SIGTERM, SIGUSR1 and SIGHUP. SIGINT,
SIGTERM and SIGUSR1 all cause a runner to exit cleanly. The master will
restart runners that have exited due to a SIGUSR1 or some kind of other
exit condition (say because of an uncaught exception). SIGHUP causes the
master and the runners to close their log files, and reopen then upon the
next printed message.
The master also responds to SIGINT, SIGTERM, SIGUSR1 and SIGHUP, which it
simply passes on to the runners. Note that the master will close and
reopen its own log files on receipt of a SIGHUP. The master also leaves
its own process id in the file specified in the configuration file but you
normally don't need to use this PID directly.
Start and watch the configured runners, ensuring that they stay alive and
kicking. Each runner is forked and exec'd in turn, with the master waiting
on their process ids. When it detects a child runner has exited, it may
restart it.
The runners respond to SIGINT, SIGTERM, SIGUSR1 and SIGHUP. SIGINT,
SIGTERM and SIGUSR1 all cause a runner to exit cleanly. The master will
restart runners that have exited due to a SIGUSR1 or some kind of other
exit condition (say because of an uncaught exception). SIGHUP causes the
master and the runners to close their log files, and reopen then upon the
next printed message.
The master also responds to SIGINT, SIGTERM, SIGUSR1 and SIGHUP, which it
simply passes on to the runners. Note that the master will close and
reopen its own log files on receipt of a SIGHUP. The master also leaves
its own process id in the file specified in the configuration file but you
normally don't need to use this PID directly.
Inicia e monitora os runners configurados, garantindo que eles permaneçam
vivos e funcionando. Cada runner é bifurcado e executado por sua vez, com
o mestre a esperar pelos IDs de processo dele. Quando ele detecta que um
runner filho foi encerrado, ele pode reiniciá-lo.
Os runners respondem a SIGINT, SIGTERM, SIGUSR1 e SIGHUP. SIGINT, SIGTERM
e SIGUSR1 fazem com que um runner seja encerrado normalmente. O mestre
reiniciará os runners que forem encerrados devido a um SIGUSR1 ou algum
tipo de outra condição de saída (digamos, devido a uma exceção não
detectada). O SIGHUP faz com que o mestre e os runners fechem os
ficheiros de log deles e os reabram na próxima mensagem impressa.
O mestre também responde a SIGINT, SIGTERM, SIGUSR1 e SIGHUP, que ele
simplesmente passa aos runners. Observe que o master irá fechar e
reabrir os próprios ficheiros de log dele ao receber um SIGHUP. O mestre
também deixa o próprio id dele de processo no ficheiro especificado no
ficheiro de configuração, mas normalmente não precisa usar este
PID diretamente.