Eli Marmor wrote:
> Tzafrir Cohenwrote:
> 
> 
>>On Fri, Jul 01, 2005 at 10:47:55AM +0300, Eli Marmor wrote:
>>
>>>...
>>>I've always used Morphix (0.5pre5) with a running DHCPD in the LAN, and
>>>its networking has worked perfectly.
>>
>>dhcp cliet, not dhcpd, right?
> 
> 
> I mentioned a DHCPD running in the LAN (i.e. under another computer),
> so it's clear that this is a DHCP server (=DHCPD) and not a client.
> 
> Of course, there is always a client too, in this case the Morphix runs
> a client.
> 
> Let me summarize my question in a way that will make the connection to
> DHCP clearer:
> 
> In the beginning, the Morphix "inherited" its IP/routing from a DHCP
> server, and everything went right.
> 
> In the second phase, I turned off the DHCPD, booted the Morphix, and
> configured the IP/routing by ifconfig and route. It still went
> perfectly. I also tried it by modifying "/etc/network/interfaces" and
> then restarting "/etc/init.d/networking: perfect.
> 
> In the third phase, I wrote a script that executed exactly the same
> commands, and asked Morphix to run it as an init command of a mini-
> module. The script was ran, the definitions were defined, but the
> interface was off.
> 
> I even inserted checks in the scripts, and found out that immediately
> after the ifconfig/route (or the 2nd way), everything was perfect, so
> there was a later process that screwed everything up.

You can try to use some system wide tracing such as syscalltrack, if the
kernel is newish enough (2.6.11 and above) you can use kprobes to write
a small kernel module to trace the system and find who calls exec and
runs ifdown.

A simple solution though would be to replace the ifdown program with
another one that would print its parent-pid and then run ifdown.

That is assuming someone actually calls ifdown to down the interface, a
program like a dhcp client might take the interface down on its own
without using ifdown.

Baruch

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to