Follow-up Comment #4, sr #109208 (project administration):
Hi Bob,
Not sure if it's related, but there's a cvs/lock directory on vcs0 in
/var/lock/cvs/ .
It has files owned by 'nobody':
root@vcs0:/tmp# ls -ld /var/lock/cvs/sources/gnubg
drwxrwxrwx 3 root root 60 Dec 15 23:32 /var/lock/cvs/sources/gnubg
root@vcs0:/tmp# ls -lA /var/lock/cvs/sources/gnubg
total 0
drwxrwxrwx 23 nobody nogroup 480 Dec 20 22:28 gnubg
root@vcs0:/tmp# find /var/lock/cvs/sources/gnubg | wc -l
50
root@vcs0:/tmp# find /var/lock/cvs/sources/gnubg | head
/var/lock/cvs/sources/gnubg
/var/lock/cvs/sources/gnubg/gnubg
/var/lock/cvs/sources/gnubg/gnubg/#cvs.rfl.vcs0.15281
/var/lock/cvs/sources/gnubg/gnubg/xpm
/var/lock/cvs/sources/gnubg/gnubg/win32
/var/lock/cvs/sources/gnubg/gnubg/textures
/var/lock/cvs/sources/gnubg/gnubg/sounds
/var/lock/cvs/sources/gnubg/gnubg/scripts
/var/lock/cvs/sources/gnubg/gnubg/po
/var/lock/cvs/sources/gnubg/gnubg/po/gnubg-langs
Perhaps they were created by the new cvs binary running under "nobody" ?
I wonder if they are safe to remove, and we can test whether they are
re-created...
I would think that cvs running from SSH runs as the actual user and thus not
owned by 'nobody',
and 'cvs' running as 'pserver' shouldn't need to lock anything...
-assaf
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?109208>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
