I've confirmed that this issue occurs when starting the opendkim daemon directly and is not an issue with start-stop-daemon or the /etc/init.d/opendkim script. I've also confirmed that the problem occurs whether I start the daemon as a non-root user via sudo or as user root without sudo. The following does NOT start the opendkim daemon approximately 10% of the time.
I see essentially identical behavior for the dk-filter daemon. Additionally, the behavior is the same for 10.04 lucid, 10.10 maverick, and 11.04 beta 2 natty. I have NOT been able to replicate the problem on 9.10 karmic (but since it is a timing issue, I'm not sure if this really is a new issue introduced since karmic).
Adding "&& sleep 1" to the command keeps the pty open long enough for the daemon to be launched properly. With the one-second sleep in place, I have not be able to replicate the issue.
I've confirmed that this issue occurs when starting the opendkim daemon directly and is not an issue with start-stop-daemon or the /etc/init. d/opendkim script. I've also confirmed that the problem occurs whether I start the daemon as a non-root user via sudo or as user root without sudo. The following does NOT start the opendkim daemon approximately 10% of the time.
ssh -tt root@maverick '/usr/sbin/opendkim -x /etc/opendkim.conf -u opendkim -P /var/run/ opendkim/ opendkim. pid -p inet:8891@ localhost'
I see essentially identical behavior for the dk-filter daemon. Additionally, the behavior is the same for 10.04 lucid, 10.10 maverick, and 11.04 beta 2 natty. I have NOT been able to replicate the problem on 9.10 karmic (but since it is a timing issue, I'm not sure if this really is a new issue introduced since karmic).
Adding "&& sleep 1" to the command keeps the pty open long enough for the daemon to be launched properly. With the one-second sleep in place, I have not be able to replicate the issue.