Hi,
I noticed in Rocky Linux 8.7 LXC container image that they've added a
message to /etc/rc.d/rc.local:
# In contrast to previous versions due to parallel execution during boot
# this script will NOT be run after all other services.
I created an issue report on this at github:
https://githu
I forgot to add that I also disabled /usr/lib/systemd/system-generators/systemd-rc-local-generator from running as it added rc-local.service to multi-user.target (in /run/systemd).Best regards,AkiOn Apr 24, 2023 11:57 AM, Aki Ketolainen wrote:
I tried to set After=systemd-update-utmp-runlevel.service but I got some cyclic dependency problem. Would you know how to do that?Best regards,AkiOn Apr 24, 2023 12:24 PM, killermoe...@gmx.net wrote:
as Lennard already told you in the GitHub issue that "last" just
doesn't make sense in systemd, there is also no need to change the
dependencies
global for everyone. Especially as there are systems out there which
doesn't have crond installed (because there are .timer).
Your best bet is really
> I tried to set After=systemd-update-utmp-runlevel.service but I got some
cyclic dependency problem. Would you know how to do that?
>
> Best regards,
>
> Aki
>
This totally depends on the unit you wrote. Without it, we can't help.
In general, ignore and forget the run level concept.
BR
Silvio
> > This totally depends on the unit you wrote. Without it, we can't help. In
general, ignore and forget the run level concept.
> > BR
> > Silvio
> > I only changed these settings in rc-local.service:
> >
> [Unit]
> After=systemd-update-utmp-runlevel.service
>
> [Install]
> WantedBy=default.targe
Would it be possible to change the rc-local.service configuration as
follows, so that it could be used similarly as before
i.e. running close to the end of the "runlevel" or systemd target:
[Unit]
After=crond.service
Why crond? Why is that the "end of the runlevel"?
I checked the service star
If you'd still like to continue using /etc/rc.d/rc.local, and it would
be
enough for it to be executed "after boot", IOW, after the default
runlevel at boot is reached, the following four commands might help
you:
$ cat >/tmp/order-last.conf <
Isn't that the same as running "systemctl edit rc-
If you'd still like to continue using /etc/rc.d/rc.local, and it would
be
enough for it to be executed "after boot", IOW, after the default
runlevel at boot is reached, the following four commands might help
you:
$ cat >/tmp/order-last.conf <
Did you test this yourself? I couldn't get it to
On 2023-12-07 23:03, Lennart Poettering wrote:
The 503 is a system user. So, just to try it out, I created a user,
which got the UID 1001. Using that UID gave me the same result as
the 503.
It's a bad idea to run user stuff as system user.
Lennart
Why's that?
Best regards,
Aki
10 matches
Mail list logo
