|FROM ||Dudemanguy via artix-general
|SUBJECT ||Re: [Hangout - NYLXS] [artix-general] [s6] not booting/rebooting
|On 9/23/20 8:30 PM, Javier via artix-general wrote:
> How can I have a nest s6-rc? Please let me know. I don't call s6-rc manually at all, unless restarting a service, or installing a new one on the fly. And I don't have modified services/oneshots (the /etc/s6/* stuff is vanilla). But not sure if there might be some non able to shutdown services though. If there's one non dying service, perhaps that's it. But how could I know?
Just a thought. Since earlier you said that poweroff/reboot worked fine
when I broke your s6-rc scripts, perhaps you are somehow having a
deadlock on this machine (although I don't know how). One easy way to
verify is to edit /etc/s6/current/scripts/rc.init and comment out the
s6-rc-init and exec lines. Maybe shutdown/poweroff will work then. If
so, at least we'd finally be on the right track.
> BTW, I doubt the scripts are messed up, since upon a fresh install of the package, they shouldn't be corrupted or messed up, right? And I don't touch them at all...
Well I mean you surely have a default bundle right? That's always
executed on startup.
> Is there a way to make s6-rc verbose, so that we can see what's it waiting for? Like making it print on the screen waiting for X service to go down, and when Y service is down, also indicating service Y already down... So somehow we can see 1st the last service waited for, and then see if all the ones waited for, were already down...
Definitely, you can add a -v2 argument (or maybe increase the verbosity
even more) to the s6-rc call in /etc/s6/current/script/rc.shutdown. It
will spam a bunch of stuff on tty1. You should also be able to check
/run/uncaught-logs/ later for that output.
artix-general mailing list
Hangout mailing list