Your message dated Thu, 14 Dec 2006 21:14:51 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402574: PATH, start-stop-daemon and dhcp3-server init 
script
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: dhcp3-server
Version: 3.0.1-2

I think there's a little bug in dhcp3-server init script, cron default PATH is very limited (only "/usr/bin" and "/bin" are included) and there are some references to "start-stop-daemon" script which is located at "/sbin/start-stop-daemon". So when I put some script to restart dhcp server via cron I get this error:

/etc/init.d/dhcp3-server: line 37: start-stop-daemon: command not found
/etc/init.d/dhcp3-server: line 24: start-stop-daemon: command not found

Solved changing all references to "/sbin/start-stop-daemon".

I am using Sarge with all stable packages.

--
Santi Saez


--- End Message ---
--- Begin Message ---
Version: 3.0.2-1

On Mon, Dec 11, 2006 at 12:52:42PM +0100, Santi Saez wrote:
> Package: dhcp3-server
> Version: 3.0.1-2
> 
> I think there's a little bug in dhcp3-server init script, cron  
> default PATH is very limited (only "/usr/bin" and "/bin" are  
> included) and there are some references to "start-stop-daemon" script  
> which is located at "/sbin/start-stop-daemon". So when I put some  
> script to restart dhcp server via cron I get this error:
> 
> /etc/init.d/dhcp3-server: line 37: start-stop-daemon: command not found
> /etc/init.d/dhcp3-server: line 24: start-stop-daemon: command not found
> 
> Solved changing all references to "/sbin/start-stop-daemon".
> 
> I am using Sarge with all stable packages.

This is a duplicate of #311723, which was fixed in 3.0.2-1.

regards

Andrew

--- End Message ---

Reply via email to