Hello,
I've run into another "side-effect" of systemd's supervisory power
over processes. The application is a simple ruby webrick daemon. It
get's started just fine. It provides web service configuration to an
appliance. One of the service calls gives clients the ability to power
down the system. Previously this was an external system call to
"shutdown -h now". Doing the same thing or even a systemctl isolate
poweroff.target yields the same results: namely, a timeout is logged
while trying to shutdown the ruby daemon that has made the system call.
Shutting down any other way goes just fine.
How can I get systemd to shut the system down without thinking it
has to sit around waiting for itself to shutdown as part of "completing"
the ruby call to systemctl or the shutdown command so that it will
shutdown quickly regardless of how the shutdown is initiated?
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
