Oliver, Nothing was written to the scmbug error log. Only status info was written to the activity log. I've appended the activity log from the interval during testing. I restarted the scmbug daemon before the tests.
Is there any other logging I can enable? One other symptom is that a perl process is running at 99% cpu utilization when the commit failure occurs. The svn commit eventually times out with "no response from server". Regards, Mike ---- Tue Jan 15 15:43:58 2008 Read configuration file '/etc/scmbug/daemon.conf' Tue Jan 15 15:43:59 2008 Server started on port '3872' (forked mode) Tue Jan 15 18:05:32 2008 127.0.0.1:50939 Processing connection from loopback Tue Jan 15 18:05:33 2008 127.0.0.1:50939 Connection from loopback processed Tue Jan 15 18:05:33 2008 reaped 30588 Tue Jan 15 20:22:30 2008 127.0.0.1:50940 Processing connection from loopback Tue Jan 15 20:22:30 2008 127.0.0.1:50940 Connection from loopback processed Tue Jan 15 20:22:31 2008 reaped 30776 -----Original Message----- From: Oliver Schäfer [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 16, 2008 1:49 AM To: Brown, Mike Cc: 'scmbug-users@lists.mkgnu.net' Subject: Re: [scmbug-users] very large commit comments break scmbug + bugzilla What about error and activity logs from Scmbug? You took a look into? -- Oliver On Jan 15, 2008, at 10:57 , Brown, Mike wrote: > Bugzilla's error log > doesn't show any entries. _______________________________________________ scmbug-users mailing list scmbug-users@lists.mkgnu.net http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
