You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JVM has a bad habit (for our use case) to still own child processes.
This means that when the JVM receives an interrupt signal, it will forward it to child processes.
The means that if the client creates a daemon receives a SIGINT, the daemon won't be able to survive.
The daemon needs to call setsid in order to detach. The jansi library would be a good candidate for this function since it already contains a bunch of posix functions.
The text was updated successfully, but these errors were encountered:
Is this the case only when the daemon is started from mvnd.sh - i.e. from a stock JVM? I am asking because the daemon seems to survive when I interrupt the mvnd native client with CTRL+C.
gnodet
changed the title
When spawning a daemon, the daemon should somehow call setsid
The daemon created by the client should survive if the client is interrupted using Ctrl+C
Nov 13, 2020
The JVM has a bad habit (for our use case) to still own child processes.
This means that when the JVM receives an interrupt signal, it will forward it to child processes.
The means that if the client creates a daemon receives a SIGINT, the daemon won't be able to survive.
The daemon needs to call
setsid
in order to detach. The jansi library would be a good candidate for this function since it already contains a bunch of posix functions.The text was updated successfully, but these errors were encountered: