Mon 18 May 2009 06:31:27 PM UTC, original submission:
This bug was originally reported to Debian on September 5th, 2006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386153
It doesn't look like it was corrected in the Ximbiot CVS, though. I've reproduced the bug report below, substituting my exact errors:
When a remote pserver operation is interrupted for some reason, cvs will get a recursive error trying to tell the disconnected client that it has been disconnected. This recursive error generates a series of syslog entries with LOG_DAEMON|LOG_EMERG which is highly excessive for a simple client disconnect.
A sample broadcast of the error message:
Message from syslogd@myhost at Mon May 18 14:13:17 2009 ...
myhost cvs[29626]: [ID 702911 daemon.emerg] cvs [checkout aborted]: flow control EOF
Message from syslogd@myhost at Mon May 18 14:13:17 2009 ...
myhost cvs[29626]: [ID 702911 daemon.emerg] cvs [checkout aborted]: received broken pipe signal
Message from syslogd@myhost at Mon May 18 14:13:17 2009 ...
myhost cvs[29626]: [ID 587406 daemon.emerg] error (1, 0) called recursively. Second message was:
Message from syslogd@myhost at Mon May 18 14:13:17 2009 ...
myhost cvs[29626]: [ID 233912 daemon.emerg] error (1, 0) called recursively. Original message was:
These messages are generated in src/error.c after the recursion_error: label around 216. I would suggest that these syslog messages do not need to be any higher than LOG_ERR, and could quite reasonably be even lower.
These errors were generated using cvs-1.12.13 pserver, configured as an inetd-managed SMF service, on a Sun Fire V215 running Solaris 10.
|