1

systemd migration, some questions esp. rc.local

view story
linux-howto

https://bbs.archlinux.org – HelloAlthough I'm not a fan of dzillions of config files I decided to try systemd. Most of the things seem to work fine but some things are unclear to me:1.) Things are working fine with rc-local.service, however I tried to make unit files for my entries in rc.local:hdparm -B 254 /dev/sdaMy unit file:[Unit] Description=hdparm control script After=local-fs.target [Service] ExecStart=/usr/local/sbin/hdparm.sh [Install] WantedBy=multi-user.targetHere I'm not sure about the After=local-fs.target. AFAIU I've to make sure that /dev/sda is ready before using hdparm. I read in another (HowTos)

Songlist's picture
Submitted by Songlist on 09/16/2012

Stories similar to systemd migration, some questions esp. rc.local

Systemd: shutdown order 38 weeks 3 days ago

Is there a counterpart to 'After=' for shutting down services in a particular order?I wrote a unit file that shall wrap an old init-script which handles initialization and backup of some ramdisks (tmpfs):[Unit] Description=Persistent ramdisks Requires=local-fs.target After=local-fs.target

[Service] Type=simple RemainAfterExit=true ExecStart=/etc/rc.d/ramdisks start ExecStop=/etc/rc.d/ra

Systemd issue 36 weeks 6 days ago

I understand that you have still initscripts installed, because it contains /usr/lib/systemd/system/rc-local.service, correct?1) You can create /etc/systemd/system/rc-local.service with something like.include /usr/lib/systemd/system/rc-local.service [Unit] After=multi-user.targetBut this will cause very slow boot up time.2) I suggest moving all items into separate service files - AFAIK rc.local is

I haven't seen anything like this before.  Upon rebooting:% hdparm /sbin/hdparm: /sbin/hdparm: cannot execute binary fileThe permissions are fine:ls -l /sbin/hdparm -rwxr-xr-x 1 root root 105440 Nov 3 02:47 /sbin/hdparmIf I capture its md5sum:% md5sum /sbin/hdparm 321ff7b32611a82c719ec7f7a7b5a67c /sbin/hdparmNow, I reinstall and everything is fine; note the DIFFERENT md5sum:% sudo pa

Privoxy Bug? 37 weeks 5 days ago

Further investigation indicates that the problem lies in the privoxy.service file.This file, included in the latest version of the package fails: [Unit] Description=Privoxy Web Proxy With Advanced Filtering Capabilities After=network.target

[Service] Type=forking PIDFile=/run/privoxy.pid ExecStart=/usr/sbin/privoxy --pidfile /run/privoxy.pid --user privoxy.privoxy /etc/privoxy/config

[Install] W

systemd rc.local like service 37 weeks 6 days ago

65kid: Here is the new version,[Unit] Description=Send IP over SMS After=network.target

[Service] Type=oneshot ExecStart=/root/bin/sendip.sh TimeoutSec=0 StandardInput=tty

[Install] WantedBy=multi-user.targetBut there is still something wrong.

rc.local or service - systemd 42 weeks 4 days ago

I think making service files is definitely the way to go. We can still use rc.local with systemd (using initscripts-systemd to get the wrapper service). However, it means that everything you do in rc.local is considered as "one" service.

If there are those who share my dilemna, I have found a not elegant hack which will keep sasc-ng alive until it truly is initiated by systemd itself. This works with both the open-sasc-ng and open-sasc-dkms AUR packages.1) If on a new intall, install latest version of initscripts. It's no longer installed by default2) Create a rc-local.service file and put it in /etc/systemd/system.

Can't get rc.local to work 42 weeks 2 days ago

Hi,

I'm trying to get rc-local.service working on my Fedora 17 64-bit system but it keeps failing. I've made it executable and here is the contents:

Quote:

#!

After boot-up process systemd starts agetty, but after 1--2 seconds additional messages are appeared:

How to avoid this?

I use Arch Linux, systemd 194.

$ grep '^[^#]' /etc/systemd/system/getty.target.wants/getty@tty1.service [Unit] Description=Getty on %I Documentation=man:agetty(8) After=systemd-user-sessions.service plymouth-quit-wait.service After=rc-local.service Before=getty.target Ignor