Problem with logging into Director - Project locked

ray.wurlod · Post by **ray.wurlod** » Tue Sep 21, 2010 9:05 pm

chulett wrote: the shear number of people

Is that people with bad haircuts?

chulett · Post by **chulett** » Tue Sep 21, 2010 9:19 pm

Ark ark. Why, yes it is.

vivekgadwal · Post by **vivekgadwal** » Fri Oct 15, 2010 12:23 pm

I have enabled the "dsdlockd" daemon in both Development and Test areas. So far so good with respect to the locks, although next week we are planning to run the production process on test to do a pre-load and that should be the acid test to this daemon. This process will take about a week to finish and has a lot of complicated stuff in the jobs.

However, I am still seeing a lot of "dscs" and "dsapi_slave" processes being stuck there. People say that they are consciously exiting the client components before they are changing from Wired to Wireless or at home too. I don't understand why these processes are still being open.

The biggest problem is that there are quite a few (two to three) runaway processes, almost every day. They are appearing on the jobs which aborted. They are occupying 99% CPU (even long after the jobs aborted). The "dsdlockd" is NOT doing anything with those defunct/runaway processes. This is becoming a big thorn in our side

Any valuable suggestions on eradicating these??