Re: key data is not secure

From: Murray S. Kucherawy <>
Date: Tue, 11 Jan 2011 13:54:41 -0800 (PST)

On Tue, 11 Jan 2011, Chris wrote:
> BTW I modified the /etc/init.d/opendkim script to prevent it from
> starting multiple instances. All that was necessary was to add a
> --pidfile arg to the daemon function call. So in the start() function,
> my daemon line looks like this:
> daemon --pidfile=$PID_FILE $DAEMON -x /etc/opendkim.conf

The script we ship in the contrib directory contains:

         od_daemon $DAEMON -x $CONFIG $ARGS

Is that the line you modified?

> I would also like to add a 'reload' argument to this script, so I can
> reload the opendkim config without interrupting anything. I read in the
> manpage that I can send signal SIGUSR1 to the process to trigger a
> config reload. I was only able to get this to work if I signaled the
> *child* process, however. When I send this signal to the parent process,
> it is terminated (with the child left running). Is this a bug, or am I
> doing something wrong?

It is indeed a bug. This is fixed in 2.3.0, which is now available in
Beta for download if you'd like to test it out.

Received on Tue Jan 11 2011 - 21:55:07 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:20:15 PST