On 29/05/2018 01:00 πμ, Steve Litt wrote:
On Mon, 28 May 2018 17:36:33 +0300
mobinmob <mobin...@disroot.org> wrote:
On 28/05/2018 08:54 πμ, aitor wrote:
As i said in a recent thread, you can shutdown/reboot doing (it
requires granted permissions):
runit-init 0
runit-init 6
I'm working on a logout dialog for runit with suid permissions.
Cheers,
Aitor.
You may want to look at the relevant utilities in void:
https://github.com/voidlinux/void-runit
I use Void's runit every day (and the PID1 once every 5 to 30 days when
I reboot. I have the distinct impression that the Void folks made Runit
more complicated than it needs to be. In an effort to kinda-sorta
implement something like "runlevels" (which I never saw value in
anyway), they have symlinks to symlinks, to the point that it's hard to
know where the real file is.
This becomes a problem for me, when I need to figure out exactly where
to put the one needed symlink (the one in the service directory) when I
add a daemon. So if anyone comes away from Void thinking runit is
complex, well, it *can* be but doesn't need to be.
SteveT
Steve Litt
June 2018 featured book: Twenty Eight Tales of Troubleshooting
http://www.troubleshooters.com/28
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Voidlinux runlevel configuration is exactly what the original author
proposes (two runlevels, default and single):
http://smarden.org/runit/runlevels.html
The service "repo" is in /etc/sv, the symlinks to start/enable services
go to /var/service.
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
