[Server-devel] Debugging network scripts (from udev and explicit ifup invocation)

[John Watlington]

The problem is that the network config script needs to be brought up
before networking is brought up.  And networking is brought up before
syslog is brought up.

I didn't find any solution, and instead debugged networking on already
booted systems.

I originally renamed all the interface with nice logical names, but ran
into problems (don't remember exactly) and moved back to the Fedora
standard ones.

Cheers,
wad

On Aug 28, 2008, at 12:08 AM, Martin Langhoff wrote:

> Is there a way to get the network script invocations to get logged
> somewhere? Something like /etc/sysconfig/network supporting
> DEBUGLOGGING=YesPlease -
>
> Jerry got me started with some good network configuration scripts for
> the funky network setup of the XS. Not all things work 100%, but I'm
> not sure where are things going wrong. Being able to trace them would
> be fantastic. (And a huge help in learning more about the network
> infra. Is there a "how it fits together" doc somewhere?)
>
> Using bash -x from the cli helps somewhat, though some things only
> misbehave under udev. Or under udev on initial boot. So a global
> logging knob would help... if it exists! Any tricks or nasty hacks
> welcome too.
>
> (What's wrong? br0 is not brought up automatically even though
> ifup-local should trigger it. And after some minor edits and a reboot,
> misteriously wlan0 and msh0 stopped auto-ifup'ing.)
>
> thanks,
>
>
>
> m
> -- 
>  martin.langhoff at gmail.com
>  martin at laptop.org -- School Server Architect
>  - ask interesting questions
>  - don't get distracted with shiny stuff - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
> _______________________________________________
> Server-devel mailing list
> Server-devel at lists.laptop.org
> http://lists.laptop.org/listinfo/server-devel