Problems rebuilding CVSROOT after a commit

[Count Zero]

Hi !

First excuse me but I don't speak (nor write) english very well ;(, and
this is my first post to this group.  Is needed to say that I'm not a CVS
expert ;(, sorry.

This is the situation:
- The client is a Fedora Core 2 using cvs 1.11.15
- The server is a Debian Woody 3.0 using cvs 1.11.1p1 
- Using pserver via inetd.

After a year using CVS without any problem, this week I decided to
incorporate the log_accum (with some changes) script from the contrib dir
of the CVS distribution.

It works very well with all modules without any problem, but with CVSROOT ...

When I make a commit on the CVSROOT module I get this error:

$ cvs -t commit
 -> main loop with CVSROOT=:pserver:address@hidden:/var/cvs
cvs commit: Examining .
 -> Connecting to src.l3jane.net(172.16.0.1):2401
 -> system('/bin/vi' '/tmp/cvszQTutJ')
 -> unlink_file(/tmp/cvszQTutJ)
 -> Sending file `readers' to server
 -> Sending file `writers' to server
S-> checkout (/var/cvs/CVSROOT/readers,v, 1.1, , (function))
[...]
Checking in writers;
/var/cvs/CVSROOT/writers,v  <--  writers
new revision: 1.4; previous revision: 1.3
done
 -> unlink_file(CVS/Base/writers)
 -> Register(writers, 1.4, Sun Jun 27 14:21:29 2004, ,  )
 -> rename(CVS/Entries.Backup,CVS/Entries)
 -> unlink_file(CVS/Entries.Log)
cvs [server aborted]: received broken pipe signal
cvs commit: saving log message in /tmp/cvslBAuTz
 -> Lock_Cleanup()

The first time I see the message I check the server logs and found this:

Jun 27 13:10:00 idoru kernel: grsec: From 192.168.0.2: attempted resource
overstep by requesting 4096 for RLIMIT_CORE against limit 0 by
/usr/bin/cvs[cvs:17215] uid/euid:0/0 gid/egid:0/0, parent
/bin/bash[bash:25187] uid/euid:0/0 gid/egid:0/0

So I disable this restriction to avoid kernel kill the process, check the
write permissions on /var/cvs/CVSROOT, but the problem persists.

Note that I'm connecting to the server via 172.16.0.0/28 network and the
kernel message reports 192.168.0.2 (It's the same computer but in another
network), I don't understand this.

The most curious fact is that the commit succeded, if I make another
commit it reports no changes and the "*,v" files in CVSROOT shows the
changes made.

The only thing that fails is when cvs try to rebuild the
files (put the new commited version on CVSROOT). I belive that this
discards the possibility of a failure on the *info scripts.

The commitinfo and loginfo are this:

CVSROOT /bin/true
DEFAULT /var/cvs/CVSROOT/commit_prep

and

CVSROOT /bin/true
DEFAULT /var/cvs/CVSROOT/log_accum %s

Perhaps I make a great novice (and stupid) error, but I don't see where.

Thanks in advance for any advice or suggestion, if you need more files or
logs ask me them please ;).

Salut
Count