On Fri, Nov 24, 2006, Ralf S. Engelschall wrote: > But for dhcpd this confused me. Our dhcpd writes its pidfile fully by > itself and in all of my tests OpenPKG's dhcpd starts, writes the pidfile > and stops correctly by using the written pidfile. Are you really sure > that this package also has this problem? If yes, you have to give me > more details about your platform, etc., please.
I can second that since I have played around a lot with dhcpd during the last days. Start/stop worked perfectly well for me. | # /v/io/sw/lib/openpkg/shtool platform -L -S "" -C "+" -F "%<ap>-%<sp>\n" | ix86-netbsd3.1.0 | # /v/io/sw/bin/openpkg rpm -q dhcpd | dhcpd-3.0.4-2.20061018 | # /v/io/sw/etc/rc.d/rc.dhcpd status | OpenPKG: status: dhcpd. | dhcpd_enable="yes" | dhcpd_usable="unknown" | dhcpd_active="no" | # ps ax | grep dhcpd | grep -v grep | # /v/io/sw/etc/rc.d/rc.dhcpd start | OpenPKG: start: dhcpd. | # ps ax | grep dhcpd | grep -v grep | 27431 ? Ss 0:00.00 /v/io/sw/sbin/dhcpd -q -p 67 fxp0 | # /v/io/sw/etc/rc.d/rc.dhcpd status | OpenPKG: status: dhcpd. | dhcpd_enable="yes" | dhcpd_usable="unknown" | dhcpd_active="yes" | # /v/io/sw/etc/rc.d/rc.dhcpd stop | OpenPKG: stop: dhcpd. | # ps ax | grep dhcpd | grep -v grep | # /v/io/sw/etc/rc.d/rc.dhcpd status | OpenPKG: status: dhcpd. | dhcpd_enable="yes" | dhcpd_usable="unknown" | dhcpd_active="no" The only problem I encountered were when I started dhcpd while being in a directory on a media I mounted temporarily. Apparently dhcpd doesn't change directory to / before spawning the daemon since umount complained about the device being still busy. Adding a 'cd /' in the rc script probably fixes that but I haven't tested yet. -cs ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
