Am 29.04.2024 um 19:57 schrieb George R Goffe via users
<users(a)lists.fedoraproject.org>:
Hi,
I noticed some time ago that rc.local became a service. I'm just getting around to
address this issue but am having trouble getting my fedora 41 system to "notice"
my efforts.
Can someone post what they're doing to implement this new way of doing things,
please?
Best regards,
George...
--
We use it to autostart nspawn containers at system boot, after the system project disabled
the systemctl enable option for nspawn container.
(Re-)activation of rc.local
———— edit ------
[…]# vim /etc/rc.d/rc.local # create and edit file
#!/bin/bash
systemctl start systemd-nspawn@CONTAINER_NAME
[[ <esc> wq ]]
[…]# chmod ug+x /etc/rc.d/rc.local # adjust permissions of created file
[…]# #### Just in case you depend on a specific network service ####
[…]# mkdir /etc/systemd/system/rc-local.service.d/
[…]# vim /etc/systemd/system/rc-local.service.d/network.conf
# /etc/systemd/system/rc-local.service.d/network.conf
[Unit]
Wants=network-online.target
After=network-online.target
[[ <esc> wq ]]
[…]#
[…]# /usr/lib/systemd/system-generators/systemd-rc-local-generator # execute
------
Each time you modify /etc/rc.d/rc.local you must rerun systemd-rc-local-generator!
Issue with F 36/37: When called, the message: "This program takes one or three
arguments." is displayed. The parameter "-h" causes the output of an error
message, e.g. that rc.local is not executable.
A "man systemd-rc-local-generator" does not mention anything about required
parameters, a "systemd-rc-local-generator --help" gives a lot of options and
shows "file ..." as a parameter, but no explanation of which files.
It works nevertheless.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast