I suspect the change in PID is as a result of the previous instance having been killed and the error message coming from the new instance being (re)started with an invalid argument.
<takes shotgun and aims at foot> Looks like the problem is with Webmin. I've updated its config to use /etc/rc.d/dhcpd start/stop/restart instead of the defaults, and the problem has gone away. </> Mea culpa. I've been away from OpenBSD for about 5 years and was using Webmin to ease the transition back into things. I'll log this with Webmin. Apologies for the noise. On Sun, 8 Nov 2015 16:33:00 -0500 Sonic <sonicsm...@gmail.com> wrote: > On Sun, Nov 8, 2015 at 3:35 PM, Jeremy <open...@smartpoint.co.nz> > wrote: > > No I only have one instance running. > > > > # ps aux | grep dhcp > > _dhcp 7784 0.0 0.1 756 1340 ?? Ss 9:00AM > > 0:00.00 /usr/sbin/dhcpd em0 > > Interesting a bit that the log shows two different PID's - it changes > between 08:25:34 and 08:25:46. > ========================================= > Nov 6 08:25:34 janus dhcpd[11758]: DHCPACK on 192.168.7.36 to > b4:ae:2b:2f:b6:bf via em0 > Nov 6 08:25:46 janus dhcpd[24427]: Can't open f: No such file or directory > ========================================= > > Not sure of the "Can't open f:", besides the config file there's the > /var/db/dhcpd.leases file.
