FS Daemon not terminating
This is an issue from 2.0.0.2
When I use the lscm lightweight command line client for a subcommand that requires the FS Daemon, the lscm either creates the daemon or uses an existing daemon that doesn't have any sandboxes attached to it.
In the latter case, the once the client that started the original daemon terminates, the daemon times out and terminates as well. However, in the first case, the daemon does not terminate at all unless manually terminated by scm daemon stop.
Is there a way to control the lifetime of the daemon when using lscm, or is the only way to end the daemon the scm daemon stop subcommand?
When I use the lscm lightweight command line client for a subcommand that requires the FS Daemon, the lscm either creates the daemon or uses an existing daemon that doesn't have any sandboxes attached to it.
In the latter case, the once the client that started the original daemon terminates, the daemon times out and terminates as well. However, in the first case, the daemon does not terminate at all unless manually terminated by scm daemon stop.
Is there a way to control the lifetime of the daemon when using lscm, or is the only way to end the daemon the scm daemon stop subcommand?
One answer
The default inactive time out is 120 mins. Did you verify that it timed out after 120 mins? You could also set the SCM_DAEMON_INACTIVE_TIME_OUT env var which is in milliseconds.
This is an issue from 2.0.0.2
When I use the lscm lightweight command line client for a subcommand that requires the FS Daemon, the lscm either creates the daemon or uses an existing daemon that doesn't have any sandboxes attached to it.
In the latter case, the once the client that started the original daemon terminates, the daemon times out and terminates as well. However, in the first case, the daemon does not terminate at all unless manually terminated by scm daemon stop.
Is there a way to control the lifetime of the daemon when using lscm, or is the only way to end the daemon the scm daemon stop subcommand?