On Sun, 19 Sep 2010, Laurent Guignard wrote:
>
> Hello,

Laurent,

> On Sat, 11 Sep 2010 15:54:15 +0200, Cristian Ionescu-Idbohrn wrote:
> > On Sat, 11 Sep 2010, Laurent Guignard wrote:
> >
> > > I took a week to work on the patch you submit but with my job i have
> > > not finished to read and understand.
> >
> > Please, do not hesitate to ask, if there's more you need to know.
> > I'll do my best to answer your questions.
> > ...
>
> To answer your question about the running function and the fact that
> pidof isn't used. I would not use the pidof command because the upstream
> source was built on Solaris and the upstream init file provided in
> /usr/share/doc/dhcp-probe/examples when package is installed. In
> sources, this the file extras/dhcp_probe.startup.Solaris9
>
> So i could adapt completely to Debian from Solaris but i would like to
> keep the work of the upstream programmer. May be i an wrong ?

Maybe.  My point is to make the script run efficiently on Linux.

> For the patch in start_daemon function, i agree the creation of the
> /var/run/dhcp-probe directory a startup.

Right.

> You suggest to write :
>        $(ip addr show dev eth0)
>
> Here, if i understand, you would like to get the IP address of the
> specified interface and you wrote "statically" the eth0 interface. Is it
> the reason of the failure you notice in comment ?

To be honest, I don't remember :(

> I suggest to write $(ip addr show dev $INTERFACE) here...

That's it!

> May be it could be your network configuration... Could you send me the
> result of the ip addr show dev XXXX command on which interface the
> script fails ?

Sorry Laurent.  I removed the package after finding out it won't run out
of the box.  And I don't remember _which_ machine I installed it on, but I
believe it was a laptop with 2 interfaces.  eth0 (wired, disconnected, no
ipv4 ip-adress on it), and a wireless interface (wlan0/eth1 connected,
with an ipv4 ip-adress on it).


-- 
Cristian



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to