You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by hongkongkiwi April 22, 2022
So I jumped into rescue mode to test it out (I have sulogin on my system) it seems the internal finit communication doesn't work properly (is this intentional?)
I noticed it as I like to type (reboot):
# reboot
reboot: Failed connecting to finit: No such file or directory
# ls -lh /sbin/reboot
lrwxrwxrwx 1 root root 7 Apr 7 2021 /sbin/reboot -> initctl
# which reboot
/sbin/reboot
Same thing happens with initctl
# initctl status
initctl: Failed connecting to finit: No such file or directory
# which initctl
/sbin/initctl
# ls -lh /sbin/initctl
-rwxr-xr-x 1 root root 49.6K Apr 7 2021 /sbin/initctl
Also finit itself:
# finit 6
initctl: Failed connecting to finit: No such file or directory
Using the exit command works fine to continue to boot the system as normal (presumably because it's a builtin shell command)
The text was updated successfully, but these errors were encountered:
Fixed, sort of. When using the bundled sulogin reboot(initctl) can detect it's in sulogin mode and trigger over to default to -f (force). Nothing can be done about initctl's other commands since Finit is paused in the background when running the system in this diminished mode. This has been documented.
reboot/poweroff/shutdown/etc
family of commands should work from asulogin
(rescue) session.Discussed in #243
Originally posted by hongkongkiwi April 22, 2022
So I jumped into rescue mode to test it out (I have sulogin on my system) it seems the internal finit communication doesn't work properly (is this intentional?)
I noticed it as I like to type (reboot):
Same thing happens with initctl
Also finit itself:
Using the
exit
command works fine to continue to boot the system as normal (presumably because it's a builtin shell command)The text was updated successfully, but these errors were encountered: