Re: [Morphix-devel] Silly Q about eth0 going down during boot

Responding to myself:

The "criminal" is pump.

Although there is no DHCP server, and although a static IP is defined,
it insists on turning off eth0.

Since it is running as a daemon, the fact that loadmod.sh is running
AFTER morphix-start (the launcher of pump) doesn't help.

So the only workarounds:

1. Add the flag "nodhcp" to the boot params (but this workaround
   requires booting it manually, which is not a real option usually).
2. Run "pump -k" before setting up eth0.

If this is how pump works, then it sucks.
It should not touch anything as long as no DHCP server responds to it.

I wrote:
> 
> [I was not sure if it should go to "devel" or to "user", so I posted to
> both; Sorry if this is wrong...]
> 
> Hi,
> 
> I've always used Morphix (0.5pre5) with a running DHCPD in the LAN, and
> its networking has worked perfectly.
> 
> Yesterday I tried with no DHCP server. When I did it manually, either
> by the "ifconfig" command, or by editing "/etc/network/interfaces" +
> running "/etc/init.d/networking restart", it worked perfectly.
> 
> Then I tried to do it through a mini-module boot command (I don't know
> the exact terminology, but I'm talking about the commands that Morphix
> executes when it is loading a mini-module, which were defined by option
> #2 of minimod-gen).
> 
> It didn't work by either of the ways (neither by the same ifconfig
> command which worked manually, nor by changing /etc/network/interfaces
> and restarting /etc/init.d/networking).
> 
> I went on, checked the interface, and found out that everything was
> defined correctly, but "somebody" turned off eth0, so its definitions
> were correct, but it was not active.
> 
> I checked further, by inserting logging into my script (the script that
> was called in the initialization of my mini-module. This script had 2
> versions: one with ifconfig, and the other with modifications to
> /etc/network/interfaces + restarting of /etc/init.d/networking). I
> logged the output of basic networking commands such as "ping", to a
> temporary file.
> 
> In both of the versions of the script, the output of the logging was
> perfect.
> 
> So the clear conclusion is that "somebody" screws it up (or, actually,
> down...) after my script (i.e. my mini-module) is called.
> 
> How can I find the "criminal" scipt?  (or isn't it a script?)
> 
> Thanks,

-- 
Eli Marmor
[email protected]
CEO, Netmask (El-Mar) Internet Technologies Ltd.
__________________________________________________________
Tel.:   +972-9-766-1020          8 Yad-Harutzim St.
Fax.:   +972-9-766-1314          P.O.B. 7004
Mobile: +972-50-5237338          Kfar-Saba 44641, Israel


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click