Iñaki Baz Castillo <[email protected]> wrote: > El Jueves, 31 de Diciembre de 2009, Iñaki Baz Castillo escribió: > > In case of using "unicorn -P PIDFILE" when the master receives a USR2 the > > pidfile is deleted and not regenerated anymore. > > > > In case of using "pid" mehotd in config file then it works well. > > > > It seems a bug, do I miss something? > > Definitively I think this is the expected behaviour as the new binary has no > way to know the PIDFILE passed as commandline argument to original binary, am > I right?
All command-line arguments are passed to the child process. We capture the command-line as soon as possible before option parsing happens. When USR2 is received, we create a new pid file for the old binary and add the ".oldbin" suffix to the pathname. That said, "-P" in the command-line and "pid" in the config file should work the same. Despite being officially deprecated, "-P" is used extensively and interchangeably with "pid" in the existing tests. -- Eric Wong _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
