On Wed, 05 Jul 2006 15:10:03 -0500, Todd Denniston <[EMAIL PROTECTED]> wrote:
>
> are you sure martin is not doing anything in the repo?
> how old are the files, e.g.,
> cd /var/lib/cvs/siprebi/sql; ls -ltrh \#cvs*
>
> how long has the machine been up?
> are there any cvs processes up with the PIDs listed on the ends of the
> files,
> i.e.,
> ps aux |grep cvs
[snip]
> If you are working in client server mode, something is killing the cvs
> server
> with extreme prejudice, like a 'kill -9' or the power being pulled.
I'm experiancing a new problem now. On a second workstation I'm trying to
update the revisions commit from earlier, and I get the cvs killed with signal
10:
$ cvs up
? gestion.sql
cvs update: Updating .
Terminated with fatal signal 10
$
After that I can find a read lock in the sql directory, but why am I getting a
kill -10?
> What version(s) of CVS are you using??
$ cvs --version
Concurrent Versions System (CVS) 1.12.13 (client/server)
--
---------------------------------------------------------
Lic. Martín Marqués | SELECT 'mmarques' ||
Centro de Telemática | '@' || 'unl.edu.ar';
Universidad Nacional | DBA, Programador,
del Litoral | Administrador
---------------------------------------------------------
_______________________________________________
info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
