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 Jun 4 18:20:12 dccifd: 1.3.105 listening to /var/dcc/dccifd (...) Jun 4 18:20:12 spamd: dcc: dccifd -> check skipped: failed to read header (...) Jun 4 20:30:19 dccifd: restart after signal 6 Jun 4 20:30:19 dccifd: 1.3.105 listening to /var/dcc/dccifd (...) Jun 4 20:30:19 spamd: dcc: dccifd -> check skipped: failed to read header (...) Jun 4 22:31:11 dccifd: restart after signal 6 Jun 4 22:31:11 dccifd: 1.3.105 listening to /var/dcc/dccifd (...) Jun 4 22:31:11 spamd: dcc: dccifd -> check skipped: failed to read header (...) Jun 5 00:41:07 dccifd: restart after signal 6 Jun 5 00:41:07 dccifd: 1.3.105 listening to /var/dcc/dccifd (...) Jun 5 00:41:07 spamd: dcc: dccifd -> check skipped: failed to read header (...) Jun 5 03:14:51 dccifd: restart after signal 6 Jun 5 03:14:51 dccifd: 1.3.105 listening to /var/dcc/dccifd (...) Jun 5 03:14:51 spamd: dcc: dccifd -> check skipped: failed to read header (...) Jun 5 06:37:53 dccifd: restart after signal 6 Jun 5 06:37:53 dccifd: 1.3.105 listening to /var/dcc/dccifd (...) Jun 5 06:37:53 spamd: dcc: dccifd -> check skipped: failed to read header (...) Jun 5 08:53:25 dccifd: restart after signal 6 Jun 5 08:53:25 dccifd: 1.3.105 listening to /var/dcc/dccifd (...) Jun 5 08:53:25 spamd: dcc: dccifd -> check skipped: failed to read header (...) Jun 5 12:35:06 dccifd: restart after signal 6 Jun 5 12:35:06 dccifd: 1.3.105 listening to /var/dcc/dccifd (...) Jun 5 12:35:06 spamd: dcc: dccifd -> check skipped: failed to read header (...) Jun 5 15:01:19 dccifd: restart after signal 6 Jun 5 15:01:19 dccifd: 1.3.105 listening to /var/dcc/dccifd (...) Jun 5 15:01:19 spamd: dcc: dccifd -> check skipped: failed to read header (...) 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. Thanks, Petar Bogdanovic _______________________________________________ DCC mailing list [email protected] http://www.rhyolite.com/mailman/listinfo/dcc
