Jeremy Evans <c...@jeremyevans.net> wrote: > This option can be used to implement custom behavior for handling > worker exits. For example, let's say you have a specific request > that crashes a worker process, which you expect to be due to a > improperly programmed C extension. By modifying your worker to > save request related data in a temporary file and using this option, > you can get a record of what request is crashing the application, > which will make debugging easier. > > This is not a complete patch as it doesn't include tests, but > before writing tests I wanted to see if this is something you'd > consider including in unicorn.
What advantage does this have over Ruby's builtin at_exit? AFAIK, at_exit may be registered inside after_fork hooks to the same effect. Thanks. -- unsubscribe: unicorn-public+unsubscr...@bogomips.org archive: https://bogomips.org/unicorn-public/
