Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 07 Feb 2012 19:56:07 +0100
From:      Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no>
To:        freebsd-stable@freebsd.org
Subject:   Re: FreeBSD 8.2-stable: devd fails to restart
Message-ID:  <20120207195607.919234a7.torfinn.ingolfsen@broadpark.no>
In-Reply-To: <alpine.BSF.2.00.1202060001390.73167@wonkity.com>
References:  <20120202212222.e940f64c.torfinn.ingolfsen@broadpark.no> <CAE-mSOJkwbc%2BrPKhhEEXKRrCrgx7-D_Y7g158OFnB_b_oBdTqg@mail.gmail.com> <20120203204110.cc933dc5.torfinn.ingolfsen@broadpark.no> <20120204043756.GA67863@DataIX.net> <20120204164423.ba815842.torfinn.ingolfsen@broadpark.no> <20120204165214.6f14f4a5.torfinn.ingolfsen@broadpark.no> <alpine.BSF.2.00.1202041029550.59919@wonkity.com> <20120204230409.338a597b.torfinn.ingolfsen@broadpark.no> <alpine.BSF.2.00.1202060001390.73167@wonkity.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 06 Feb 2012 00:08:55 -0700 (MST)
Warren Block <wblock@wonkity.com> wrote:

> On Sat, 4 Feb 2012, Torfinn Ingolfsen wrote:
> 
> > On Sat, 04 Feb 2012 10:34:19 -0700 (MST)
> > Warren Block <wblock@wonkity.com> wrote:
> >
> >>
> >> Possibly relevant:
> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=140462&cat=
> >>
> >> (Using DHCP from /etc/rc.conf leaves a lock on devd.pid.  SYNCDHCP does
> >> not.)
> >>
> >> And the thread:
> >> http://lists.freebsd.org/pipermail/freebsd-current/2009-October/012749.html
> >
> > Yes, it seems to be that problem. Tested on my other machine, which hasn't changed since the problem was discovered:
> > root@kg-v7# service devd status
> > devd is not running.
> > root@kg-v7# ll /var/run/devd.pid
> > -rw-------  1 root  wheel  3 Jan 12 20:40 /var/run/devd.pid
> > root@kg-v7# lsof /var/run/devd.pid
> > COMMAND   PID  USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
> > dhclient 1075  root    5w  VREG   0,70        3 918547 /var/run/devd.pid
> > dhclient 1091 _dhcp    5w  VREG   0,70        3 918547 /var/run/devd.pid
> > root@kg-v7#
> >
> > So, if this was worked on back in 2009, why isn't fixed yet?
> 
> I switched to using SYNCDHCP which avoids the problem, didn't enter a 
> PR, and quickly forgot about it.  It would be nice to have it fixed.

I'm all for getting it fixed, even if I don't know how yet.
Should a PR be against devd, dhclient, or ... something else?
-- 
Torfinn




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120207195607.919234a7.torfinn.ingolfsen>