On Thu, Nov 29, 2012 at 11:36 AM, Alexander E. Patrakov <patra...@gmail.com>wrote:
> Brandon Black <blbl...@gmail.com> wrote: > > The daemon's "fast restart" code does all of the expensive startup > > operations in the new daemon first (e.g. parsing large data input), then > This is not what a restart means in systemd world. What you described is > just a nice way to do a reload. However, as the main pid changes during > this reload, please be careful - several years ago that would hit an > assertion in systemd, and due to my aziness I have not verified the fix. > The current ExecReload code apparently intentionally doesn't allow for a restart-like operation, though. If ExecReload replaces the process with a fresh PID, that PID ends up getting SIGKILL'd by systemd. cf. this post/thread: http://lists.freedesktop.org/archives/systemd-devel/2012-June/005402.html . I've confirmed similar behavior recently with my daemon and F18's copy of systemd.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
