Addressing hanging daemons
![]()
Dana Maxfield (23●4●6)
| asked Mar 18 '14, 3:46 p.m.
edited Mar 19 '14, 3:46 a.m. by Ralph Schoon (63.3k●3●36●46)
We have a custom build environment that we are adjusting to work with RTC. The issue that we have found is that with our current functionality, we are experiencing hanging daemons; 90 of them hanging at once in 7 days. When we set the SCM_DAEMON_INACTIVE_TIME_OUT environment variable, our daemons aren't starting at all.
So my question.... if we issue the command to stop a daemon, and that daemon is not hanging but is actually doing something, will the daemon finish what it is doing before it is stopped? |
One answer
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Are you running scm commandline commands in the buil? Just to make sure we understand, where the daemons are launched.
No scm command line commands from the build, but our automated build management tool runs lscm.bat whenever our UI needs to refresh or one of our build branches polls.
That shouldn't happen. Assuming that you aren't doing any operations on a sandbox (load, accept, commit, etc) then a single daemon should be started and reused by each invocation of 'lscm'.
Is the user's home directory on a filesystem that supports locks (e.g. NFS)? If not, 'lscm' won't be able to acquire a mutex necessary to find the daemon and will start a new one.
Are you using %SCM_CONFIG_DIRECTORY% or --config to set the CLI configuration directory? If so, make sure the value is always the same.