Rc-local.service keeps failing after one time success

Question

Actually it's quite weird, every time rc-local.service was enable successfully with boot but then it keeps failing. However, once I modify /etc/systemd /system/rc-local.service( even something that really doesn't matter ), it will be enabled successfully again. but only ONCE each time.
[Unit]
Description=/etc/rc.local compatibility
[Service]
Type=oneshot
ExecStart=/etc/rc.local
TimeoutSec=0
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target

Answer 1

All of those things can be done with udev rules.  I had a Momentus XT, which I now no longer have in my system, but my old rule is still there.  It is as follows:
ACTION=="add", SUBSYSTEM=="block", ATTRS{model}=="ST95005620AS", RUN+="/sbin/hdparm -B 247 /dev/$kernel"
You could also do something like this to apply it to all rotational disks
ACTION=="add", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="0", RUN+="/sbin/hdparm -B 254 /dev/$kernel"
As far as the stuff in /sys, use udevadm to get stuff to put in your rule to identify it.  So something like
$ udevadm info -a -p /sys/kernel/debug/vgaswiteroo
I have also used a rule for my backlight setting on boot.  To find stuff, once again use the udevadm
$ udevadm info -a -p /sys/class/backlight/acpi_video0
My resulting backlight rule is:
ACTION=="add", KERNEL=="acpi_video0", SUBSYSTEM=="backlight", SUBSYSTEMS=="pci", DRIVERS=="i915", ATTR{brightness}="2"
For more info on writing udev rules see http://www.reactivated.net/writing_udev_rules.html but when you get to the part about the udev commands, those no longer apply, as they have now been replaced by the udevadm commands listed above.  The commands are mostly correct, just instead of udevinfo, it is udevadm.
I hope this helps!
Last edited by WonderWoofy (2012-11-02 02:59:59)