dhcpcd-discuss

Hi Roy,

ok assuming something else started it, then the issue slightly different.

Then why the ipv6 dhcpcd did not daemonize?
It should of daemonized to handle router advertisement expirations, and new
advertisements.

On Tue, Dec 1, 2020 at 8:56 AM Roy Marples <roy@xxxxxxxxxxxx> wrote:

> Hi Boris
>
> On 01/12/2020 13:29, Boris Krasnovskiy wrote:
> > Hi Roy,
> >
> > the problem is actually a bit stranger:
> >
> > on the 1st execution, no daemon created, on the 2nd execution and any
> subsequent
> > as I described.
> >
> >   killall dhcpcd
> > killall: dhcpcd: no process killed
> > # dhcpcd -t 5 -6 eth0
> > dhcpcd-9.3.4 starting
> > DUID 00:01:00:01:0d:2b:80:16:c0:ee:40:c0:17:3d
> > eth0: IAID 40:51:4e:0e
> > eth0: soliciting an IPv6 router
> > eth0: Router Advertisement from fe80::a273:876b:598:9dcf
> > eth0: no global addresses for default route
> > timed out
> > dhcpcd exited
> > # ps ax | grep dhcpcd
> >    940 root     grep dhcpcd
> >
> > # killall dhcpcd
> > killall: dhcpcd: no process killed
> > # dhcpcd -t 5 -6 eth0
> > dhcpcd-9.3.4 starting
> > DUID 00:01:00:01:0d:2b:80:16:c0:ee:40:c0:17:3d
> > eth0: IAID 40:51:4e:0e
> > eth0: soliciting an IPv6 router
> > eth0: Router Advertisement from fe80::a273:876b:598:9dcf
> > eth0: no global addresses for default route
> > timed out
> > dhcpcd exited
> > # ps ax | grep dhcpcd
> >    988 root     dhcpcd: eth0 [ip4] [ip6]
> >   1097 root     grep dhcpcd
>
> I can only summarise that something else is starting dhcpcd for you.
> I tested this on Alpine and Devuan Linux, NetBSD and FreeBSD - all worked
> fine,
> at no point did any other dhcpcd process start.
>
> Roy
>


-- 
Thank you,
Boris Krasnovskiy