On 6/5/2009 7:10 AM, Petar Bogdanovic wrote:
Hi,
I just noticed the following irregularity since we replaced 1.3.103 with
1.3.105 on a NetBSD 4.0 machine (no virtualization):
Jun 4 16:10:14 dccifd: restart after signal 6
Jun 4 16:10:14 dccifd: 1.3.105 listening to /var/dcc/dccifd (...)
Jun 4 16:10:14 spamd: dcc: dccifd -> check skipped: failed to read header
(...)
Jun 4 18:20:12 dccifd: restart after signal 6
According to kill(1) on NetBSD, signal 6 is ``ABRT (abort)''. What
could that be? It certainly never occured when we used 1.3.103.
I had the same experience, and didn't have time to track the issue. I
reverted to dccproc for the time being. I'd be curious about the
situation too.
Regards,
Mike
_______________________________________________
DCC mailing list [email protected]
http://www.rhyolite.com/mailman/listinfo/dcc
