F16 startup breaks certain commands in rc.local

[gregscott]

After I made my first script changes and then looked at my boot.log, I was shocked that the output from my changes didn't show up. But then looking at the date, I realized it was 2 days old. There were no variants of boot.log with older dates or sequence numbers.

So I renamed it and booted again and this time got a current and helpful boot.log. But then after some more tinkering with my script, renaming boot.log again, and rebooting, the new boot.log was 0 bytes. The next reboot after that, boot.log was fine.

Go figure.

- Greg

---------- Post added at 11:35 PM ---------- Previous post was at 11:25 PM ----------

re: Vallimar -

> I've mentioned this in the past, but try using the script-launching facilities built into NM.

I always disable NetworkManager in my firewalls and just chkconfig level 345 network on. Simple is good. F16 turns my now obsolete chkconfig into the right systemd command and one day I'll get the new sytemd stuff in my head. I don't think systemd is going a way anytime soon.

[PabloTwo]

I've noticed that the successful writing of boot.log miss-fires at times, for unknown reasons. Awhile back, on one of two of my F16 installs, I disabled livesys.service and livesys-late.service. Since I always install from a "Live" CD, I mistakenly thought that these were no longer needed after an install to hdd. Not until finally wanting to check my boot.log two weeks or so later did I realize the date stamp on the boot.log file was, well, about two weeks old. Doh!

The writing of the boot.log also seems somewhat tied to Plymouth, and who knows what else.