Hi!

Two questions (In Linux it's possible to replace the image of the binary that 
is executed on disk):

1) It seems my version of systemd (228) does not detect that a binary has 
changed since the service was started. In case it's still true in the current 
version, is it difficult to indicate that fact in "systemctl status .."?

2) Given 1), would it make sense to allow an option like "RestartIfBinary 
Changed"?

I noticed a file ".nfs00000000000451710000000a", a typical indicator of an 
unlinked inode that's still in use; in my case the binary being executed...

Regards,
Ulrich



_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to