I was getting this during my last checkin: cvs server: [00:00:33] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:01:03] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:01:33] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:02:03] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:02:33] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:03:03] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:03:33] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:04:04] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:04:34] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:05:04] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:05:34] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs cvs server: [00:06:04] waiting for xemacs's lock in /usr/CVSroot/XEmacs/xemacs ... On investigation, I found a stale lock file, which I renamed as follows: -rw-rw-rw- 1 xemacs xemacs 0 Feb 5 07:45 save-#cvs.rfl.camelot-soft.camelot-soft.com.10195 The process appears to still be running. I hope nothing bad happens. Martin