dhcpcd-discuss

On 2014-09-15 02:51, Amit Uttamchandani wrote:
> On Sun, Sep 14, 2014 at 04:05:23PM +0100, Roy Marples wrote:
>
> [snip]
>
> > > With dhcpcd's carrier management, the daemon itself is spawned for eth0
> > > and then times out and exits (30s I think). So you're saying to set
> > > dhcpcd timeout to 0 so that the daemon never exits and thus handles
> > > carrier detection?
> >
> > It's because you started it with zero flags and an interface.
> > Try using the -M flag or not specifying an interface.
> > If you wish to restrict interfaces, another option is to use the
> > allowinterface / denyinterface options in dhcpcd.conf
>
> The manual says -M is master mode, couldn't find any other references 
> to
> master mode in the man pages, what does this do?

Master mode is controlling >1 interface
Updated the man page to reflect this here:
http://roy.marples.name/projects/dhcpcd/fdiff?v1=b7c9a9866b962d2c932c3715fb574e85e455650d&v2=1e2385e03ed296dfa208401ff74f91194b1197d1&sbs=0

> Yes, currently no interfaces are specified, dhcpcd is started up on
> startup by /etc/init.d/dhcpcd which pretty much just launches
> /sbin/dhcpcd without any options.

From your log file /var/run/dhcpcd-eth0.pid

That tells me dhcpcd has been called like so

dhcpcd $options eth0

If eth0 wasn't there it would be /var/run/dhcpcd.pid

Roy