On 10/17/2011 01:10 PM, Clyde E. Kunkel wrote:
On 10/17/2011 10:20 AM, Bruno Wolff III wrote:
> I want to try to modprobe netconsole during boot, but it needs to happen
> after the network is up. Is there any standard place (rc.local and
> modules-load seem to happen too early) to do this?
>
> I filed
https://bugzilla.redhat.com/show_bug.cgi?id=746481 against systemd,
> but it has been closed notabug. So I am looking for simple alternatives
> to do this. If there aren't any, then it looks like I need to make a custom
> service that waits for networking to be up.
FWIW, I have been struggling with this for awhile. And now, in what
seems like "magic," it is working fine in rawhide but not in F16 (tho it
does in maybe 1 in 20 boots). I followed the procedure in
https://fedoraproject.org/wiki/Netconsole. Since the e-net card is
renamed to a local bus name (p37p1 in my case), specifying eth0 in the
netconsole parms wasn't working and systemd was reporting an error and
specifying p37p1 wasn't working since the device was eth0 at the time.
Since updating systemd to systemd-37-1.fc17.x86_64, specifying eth0 now
works nicely to start netconsole logging well before NetworkManager does
its thing and I still get a eth0 network using NetworkManager.
...
Well, spoke too soon, seems I had a run of good luck with netconsole
loading early. No longer true. Need to figure out how to get this working:
$ systemctl status fedora-loadmodules.service
fedora-loadmodules.service - Load legacy module configuration
Loaded: loaded (/lib/systemd/system/fedora-loadmodules.service; static)
Active: failed since Mon, 17 Oct 2011 13:36:20 -0400; 16min ago
Process: 632 ExecStart=/lib/systemd/fedora-loadmodules (code=exited,
status=1/FAILURE)
CGroup: name=systemd:/system/fedora-loadmodules.service
Sorry for the noise.
--
Regards,
OldFart