Re: Is there an officially Fedora supported replacement for the old rc.local?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



using the rc.local is going to be easier to support than creating your
own systemd service to do exactly the same thing.

I have been using the rc.local stuff for a while for anything that
does not have a native systemd unit file.

I think the comment of not using it is for other developers to not put
into their instructions to add xxx to rc.local and telling them to
create a proper systemd unit file.

There have always been a lot of projects out there that just say add
it to rc.local and do not create a proper startup script to be used.

On Mon, Jul 18, 2022 at 11:01 AM Peter Boy <pboy@xxxxxxxxxxxxx> wrote:
>
> I have to run some scripts at the end of the boot process to establish various workarounds for bugs in systemd. In the days of System V, /etc/rc.d/rc.local would be the right place for this.
>
> My research revealed several solutions with conflicting recommendations:
> (a)
> There is - also in Fedora - systemd-rc-local service. In the man file it is advised not to use it. A Fedora default installation also does not completely create the necessary directory structure. And if one wants to execute this service as far as possible at the end of the boot process, further adjustments are necessary.
>
> (b)
> There is the DIY suggestion to create a service of one's own, and to place it as far as possible at the end of the system start.
>
> (c)
> A suggestion is to insert in the root-crontab at the end
> @reboot systemctl start ….
>
> The latter seems to be the most reliable solution at the moment.
>
> Any recommendations and/or experiences?
>
>
>
>
>
> _______________________________________________
> 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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux