On Mon, Jul 18, 2022 at 10:50:03PM +0200, Peter Boy wrote:
Am 18.07.2022 um 22:18 schrieb Peter Boy <pboy@xxxxxxxxxxxxx>:
I got it finally working.
After some tests: It isn’t.
The programs I have to start depend on the existence of some (virtual)
network interfaces. rc.local is ordered after network.target, which
doesn’t mean, the network is functional then. Therefore, the program
start via rc.local is in indeterministic process. Sometimes it works,
sometimes not, sometimes only for some.
Maybe this from: SYSTEMD-RC-LOCAL-GENERATOR(8)
Also note that rc-local.service is ordered after network.target, which
does not mean that the network is functional, see systemd.special(7).
If the script requires a configured network connection, it may be
desirable to pull in and order it after network-online.target with a
drop-in:
# /etc/systemd/system/rc-local.service.d/network.conf
[Unit]
Wants=network-online.target
After=network-online.target
Documentation mentions a drop in at
/etc/systemd/system/rc-local.service.d/network.conf. But there is no
subdirectory /etc/systemd/system/rc-local.service.d/
Should I really mess around with vim and mkdir in the directories
managed by the distribution? Seems like a bad idea to me.
Or have I missed something?
Am 18.07.2022 um 18:08 schrieb Tom Horsley <horsley1953@xxxxxxxxx>:
Is it really gone, or are they simply not creating the rc.local
file any longer?
The file is really gone. You have to create it at the right location.
The documentation is inconsistent. Some say /etc/rc.local, some /etc/rc.d/rc.local. The latter is correct.
What I did:
(1)
Create /etc/rc.d/rc.local (with bash shebang), put in the execute commands needed, made it executable for user und group root (but just user root should be ok).
(2)
Executed
/usr/lib/systemd/system-generators/systemd-rc-local-generator
Is not on the path, you have to enter the complete path yourself - great.
This step is indispensable!
(3)
Reboot, voila the included programs got started.
I think, this is a better way than to hide the execute commands in user root’s crontab.
Thanks for all the support!
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
End of included message <<<
--
Jon H. LaBadie jonfu@xxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
