Dimitrie O. Paun writes:
>
> We get very often locks left around the repository. For example, today we've
> got:
>
> [root@redpill evolve-client]# find -name "*cvs*"
> ./images/#cvs.rfl.redpill.redcelsius.on.ca..1647
> ./images/#cvs.rfl.redpill.redcelsius.on.ca..1660
> [root@redpill evolve-client]# ps aux | grep cvs
> cvs 7519 0.0 0.1 2064 364 ? S 08:15 0:00
> cvs --allow-root=
> cvs 7520 0.1 0.7 3324 2044 ? S 08:15 0:28
> cvs --allow-root=
> cvs 8587 0.0 1.6 5448 4348 ? S 14:21 0:00
> cvs --allow-root=
> cvs 8588 0.0 0.9 3980 2356 ? S 14:21 0:00
> cvs --allow-root=
>
>
> What is going on? What can be the problem?
The last part of the lock file name is the PID of the process that
created the lock -- since there doesn't appear to be any current CVS
process with those PIDs, I'd say that you have a problem with CVS
crashing. You're not running with PreservePermissions enabled, are you?
That's the quickest way I know to crash CVS. If not, you're going to
have to do some investigating to find out what's causing the crashes.
Have you had complaints from users? Do you have any core dumps lying
around?
-Larry Jones
Do you think God lets you plea bargain? -- Calvin
