You are not logged in.
I was trying to emulate rc.local behaviour with this:
/usr/lib/systemd/system/rc-local.service
[Unit]
Description=/etc/rc.local Compatibility
ConditionPathExists=/etc/rc.local
[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
StandardOutput=tty
RemainAfterExit=yes
SysVStartPriority=99
[Install]
WantedBy=multi-user.target
and my
/etc/rc-local
looks like this
modprobe -r samsung_laptop
But it's not working. When I execute sudo systemctl status rc-local.service I get
rc-local.service - /etc/rc.local Compatibility
Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled)
Active: failed (Result: exit-code) since Fri 2013-03-29 17:54:16 CET; 5min ago
Process: 745 ExecStart=/etc/rc.local start (code=exited, status=203/EXEC)
Last edited by Neky (2013-03-29 18:31:39)
Offline
Why do you have "start" as an argument to /etc/rc.local?
Also, for what you are trying to achieve, why not simply blacklist the module in /etc/modrpobe.d? Then it would not be loaded under any circumstances. Also if this is out of fear of the UEFI bug, I believe that for this particular module, there has been a patch included in the latest kernels that protects this from happening by not allowing writes to the NVRAM if it is 50% full or more.
Offline
Well, I was blindly copy-pasting without reading. Either way, a module should be blacklisted, as you said. This one is solved, thank you.
Offline