On Thu, 07.06.12 19:36, Sam Varshavchik (mr...@courier-mta.com) wrote: > Dave Reisner writes: > > >On Thu, Jun 07, 2012 at 08:41:54AM -0400, Sam Varshavchik wrote: > > > >This is wrong. ExecReload should not cause the process to change PIDs. > >Not that this was ever allowed, but the below commit is was causes the > >SIGKILL behavior you're seeing: > > > >http://cgit.freedesktop.org/systemd/systemd/commit/?id=8f53a7b8ea9b > > Thanks for confirming that this SIGKILL comes from systemd. > > This, however, blocks re-exec()ing of a secure, non-root daemon that > runs in a chroot jail. The workaround that's needed to work around > this obstacle, is messy.
It appears to me that you your reload shouldn't be called "reload". I mean, if you just sop and restart your service, then we already have that, it's called "restart", and is implemented implicitly for you. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
