The patch looks sane, however I fail to reproduce the issue.
Installing exim4-daemon-light on up-to-date hardy just works for me.
Looking at the Debian bug we are experiencing something different. Their issue was triggered by a change in how start_daemon handles args in lsb>=3.2-9, and hardy runs with 3.2-4ubuntu1. Running the init script in debug mode, in particular, shows no empty ('' '' '') arguments in the start-stop-daemon call :
The patch looks sane, however I fail to reproduce the issue.
Installing exim4-daemon-light on up-to-date hardy just works for me.
Looking at the Debian bug we are experiencing something different. Their issue was triggered by a change in how start_daemon handles args in lsb>=3.2-9, and hardy runs with 3.2-4ubuntu1. Running the init script in debug mode, in particular, shows no empty ('' '' '') arguments in the start-stop-daemon call :
$ sudo EX4DEBUG=1 /etc/init.d/exim4 start stop-daemon --start --nicelevel 0 --quiet --exec /usr/sbin/exim4 --oknodo --pidfile /var/run/ exim4/exim. pid -- -bd -q30m
...
+ /sbin/start-
...
Could someone that experienced that issue confirm lsb-base version and send the result of the "sudo EX4DEBUG=1 /etc/init.d/exim4 start" command ?