Re: DHCP issues 2

     OK, this seems a little odd, but maybe it is normal operation.  
Shouldn't the daemon be writing to the leases file? It doesn't seem to 
be.  It creates two files per server, one named xxx.leases and one named 
xxx.leases~.  The "~" usuallty means a temporary file, doesn't it?  
Neither is written to after the daemon is stable.

On 6/2/2022 5:52 PM, Leslie Rhorer wrote:
> On 6/2/2022 2:00 PM, Simon wrote:
>> Leslie Rhorer <[email protected]> wrote:
>>
>>>      2. Stopping the service does not actually do anything.  The 
>>> .pid file remains intact and the service remains in memory.  Having 
>>> to manually delete the .pid file and manually kill the daemon is a 
>>> pain, especially right now since I am setting things up and 
>>> restarting the service a lot.
>> That is easy to answer - it’s NOT a DHCP server issue, that’s a 
>> distro/packaging issue.
>> Since I don’t use systemd, I can’t help further in terms of the 
>> startup/shutdown problems.
>
>     I would be inclined to agree, except for two things:
>
> 1.  Why is it happening on the secondary and not the primary? They are 
> the same version of the same distro.
>
> 2.  Why is dhcpd sending an exit code of 1?  That is why systemd 
> thinks there is a failure.  Dhcpd (or any daemon) is supposed to send 
> an exit code of 0.
>
-- 
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.

dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users