dccifd: restart after signal 6

MrC lists-dcc@cappella.us
Fri Jun 5 18:38:55 UTC 2009

On 6/5/2009 11:14 AM, Vernon Schryver wrote:

> Signal 6 generally comes from the abort() library function.  That
> ought to be associated with a system log complaint about a major problem.
Yup.  The only other log message I have is generated by amavisd-new, 
which just passed on the info from SpamAssassin:

May 30 16:57:33 glacier amavis[14242]: (14242-02) _WARN: dcc: dccifd -> 
check skipped:  failed to read header at 
line 471.
May 30 16:57:33 glacier dccifd[1484]: restart after signal 6
May 30 16:57:33 glacier dccifd[21099]: 1.3.105 listening to 
/var/dcc/dccifd for ASCII protocol

> There should also be a core file in the DCC home directory.  That core
> file might be useful with gdb if dccifd has been built with
> debugging information.

There was, but I had not built w/debug.

> To rebuild the DCC software with debugging information, run
>     .../libexec/updatedcc -e DBGFLAGS=-g

Done - now awaiting core file production.

> Is that also with NetBSD?


$ uname -smr
NetBSD 4.0.1 i386

More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.