To *run Linux from RAM *I have a hook that copies the contents of the root
device to a zram device. Here is a snip from the hook:
mkdir /real_root/
mount ${root} /real_root/
modprobe zram
zRAM__DEV=$(zramctl -f -fs $(free -m | awk '/Mem/ {print
int($2*2)"M"}') -a lzo -t
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 Fr, 21.04.23 18:36, Caeri Tech (caerit...@gmail.com) wrote:
> I've been running Linux from RAM for a couple years without issue.
> However, since the upgrade from 252 to 253 the load to RAM fails and the
> computer hangs with the message below:
>
> [!!] Failed to start up manager.
> [
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
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
On Mo, 24.04.23 13:01, Aki Ketolainen (a...@mykolab.com) 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?
s-u-u-r.s is a legacy service that will update utmp *after* all
services that constitute a
On Mon, Apr 24, 2023 at 01:20:09PM +0300, Aki Ketolainen wrote:
> > as Lennart 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
> >
On Mo, 24.04.23 11:57, Aki Ketolainen (a...@mykolab.com) wrote:
> 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
> > 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]
>
Am 24.04.2023 um 12:52 schrieb Aki Ketolainen :
>> 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]
>
> 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
> Am 24.04.2023 um 12:20 schrieb Aki Ketolainen :
>
>> 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
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
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:
> Am 24.04.2023 um 10:57 schrieb Aki Ketolainen :
>
> 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 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:
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:
On Mon, Apr 24, 2023 at 7:04 AM jaimin bhaduri wrote:
> Cgroups v2 is enabled in almalinux 9.1 with 5.14.0-70.22.1.el9_0.x86_64
> kernel and systemd 250 (250-12.el9_1.3).
>
> Content of /etc/systemd/system/user-1002.slice.d/override.conf:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
18 matches
Mail list logo
