On Sat 15 Feb 2014, Perry Hutchison wrote: > Hiroyuki Ikegami <ike...@mixallow.net> wrote: > > 2014-02-15 7:39 GMT+09:00 Grozdan <neutri...@gmail.com>: > > > Yesterday, I changed my rsyncd.conf file to add one more module to it. > > > Then I sent a kill -HUP $pid signal to rsync running in daemon mode, > > > but what gives? It just died so I had to start it up again. I though > > > sending a HUP would just make it reload its config file, no? > > > > Many softwares catches SIGHUP as a trigger to reload configurations. > > But it is a kind of software design. If the programmer does not want to > > write signal handling code, the programs received HUP just dies. > > This really ought to go on the to-do list. It is a very > longstanding convention that a daemon should reinitialize itself > (for some reasonable definition of reinitialize) upon receiving > a SIGHUP.
Why should the code be modified to help those that don't read the docs properly? From the rsyncd.conf manpage: Note that you should not send the rsync daemon a HUP signal to force it to reread the rsyncd.conf file. The file is re-read on each client con‐ nection. Paul -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html