Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

systemd pid1 / runit service supervision

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
Bulkley
Posts: 6382
Joined: 2006-02-11 18:35
Has thanked: 2 times
Been thanked: 39 times

systemd pid1 / runit service supervision

#1 Post by Bulkley »

Because I wanted to know what would happen :wink: . . .

Bullseye with Openbox.

Code: Select all

 # aptitude install runit-systemd
Reboot.

Code: Select all

# aptitude install runit-run runit
Reboot

Code: Select all

$ cat /proc/1/comm
systemd

Code: Select all

$ systemctl status runit.service
● runit.service - Runit service supervision
     Loaded: loaded (/lib/systemd/system/runit.service; enabled; vendor preset:>
     Active: active (running) since Wed 2021-08-25 18:38:57 PDT; 25min ago
       Docs: http://smarden.org/runit/
   Main PID: 408 (runsvdir)
      Tasks: 1 (limit: 2340)
     Memory: 284.0K
        CPU: 38ms
     CGroup: /system.slice/runit.service
             └─408 runsvdir -P /etc/service log: ..............................>

Warning: some journal files were not opened due to insufficient permissions.
The crazy thing works. Doing it this way separates init from service supervision. Systemd is still in place so I didn't have to change instructions for shutdown and reboot.

I am a bit puzzled by the warning. Which "journal files were not opened due to insufficient permissions?" Does that matter?

Post Reply