dhclient existing when run early in startup

[Tobias Roth]

On Wed, Feb 22, 2006 at 06:41:42PM +0100, Tobias Roth wrote:
> On Wed, Feb 22, 2006 at 09:02:12AM -0800, Kevin Oberman wrote:
> > I have dhclient almost working on -current. I just added the following 3
> > lines before running dhclient:
> >   if ! [ -d "/var/empty" ]; then
> >     mkdir /var/empty
> >   fi
> > 
> > I don't delete the directory, so it's only created once and just sits
> > there forever.
> 
> I'll add that to the next revision. I'm installing and setting up
> -CURRENT right now so I can continue development there.

By the way, do you know why you have no /var/empty in the first place?
I just tried profile with a vanilla current from feb 7, and it works
even without your trick above, since I already had a /var/empty.

> > Now, the correct profile is selected, but I now hang in dhclient in
> > netif. This may be impacted by the fact that I am running ISC
> > dhcp-client because my Prism 2.5 does not play will with the one in
> > -current. 
> 
> Yeah, in rev 25I adapted profile from the old ISC dhcp to the new
> OpenBSD dhcp. You might want to revert this if you depend on ISC.

On second thought, I am now confused. Are you saying that you use
both dhclients concurrently? The OpenBSD one during profile (since
it is run before mountcritlocal and you probably have isc-dhclient
installed under /usr/local), and isc after mountcritlocal has been
executed?

greets, Tobias