You are not logged in.
I have following options enabled in /etc/rc.conf on a Beowulf 3.0 with OpenRC-0.42-1. Boot time is around 39 seconds from rEFIt menu to gdm3 login screen. Honestly, I don't really feel any reduction in time taken. But, just curious if these options being enabled is safe and OK?
rc_parallel="YES"
rc_logger="YES"
rc_loopsolver_enable="YES"
rc_loopsolver_warnings="YES"
rc_tty_number=12
rc_send_sighup="YES"
rc_timeout_stopsec="YES"
rc_send_sigkill="YES"
This is the /var/log/rc.log:
https://paste.debian.net/1158276/
Last edited by Debuser2018 (2020-07-30 10:06:53)
Offline
I did not feel any speed benefit. Reverted back to original configuraiton, that is:
rc_loopsolver_enable="YES"
rc_loopsolver_warnings="YES"
Offline
I did not feel any speed benefit
Devuan already uses the startpar package to parallelise sysvinit and I think it may also work with OpenRC.
if these options being enabled is safe and OK?
Take note of the warning given by the OpenRC developers:
Brianna Ghey — Rest In Power
Offline
Debuser2018 wrote:I did not feel any speed benefit
Devuan already uses the startpar package to parallelise sysvinit and I think it may also work with OpenRC.
Debuser2018 wrote:if these options being enabled is safe and OK?
Take note of the warning given by the OpenRC developers:
Better to go with default values in /etc/rc.conf. Never heard about startpar. But, when I measured the boot time, both are equal (almost). No significant difference in boot time.
Offline
I had noticed the warnings, but I have tried running OpenRC with parallel turned on and have not had any real problems with it. The only difficulty I noticed was the logging gets untidy as the messages from different parts get interleaved. I had not noticed any great increase in the boot speed. While I have been looking at using openrc-init as PID 1, I turned off the parallelism to make the logging clearer. There is also a small problem where some blocks of logging output get duplicated. I have not been able to track this down, but may be related to the early logging getting stored somewhere in memory and then copied to disk later.
Geoff
Offline
@Geoff 42: Yeah. When parallel enabled, the boot messages are messed up. But, I heard we can use lighter init software with openRC. Like runit. Not sure whether these are any better, though.
Offline
I have tried using Runit as a process supervisor, with SysVinit as PID 1.
https://dev1galaxy.org/viewtopic.php?id=1748
I then looked at using OpenRC
https://dev1galaxy.org/viewtopic.php?id=2072
and also using Runit as a process supervisor under OpenRC
https://dev1galaxy.org/viewtopic.php?id=2078
although OpenRC now comes with its own supervisor.
https://dev1galaxy.org/viewtopic.php?pid=9501#p9501
I have also looked at using OpenRC as PID 1, which can work well
although there is a remaining bug, although I offer a patch to
fix it.
https://dev1galaxy.org/viewtopic.php?id=2788
https://dev1galaxy.org/viewtopic.php?id=3371
Geoff
Offline