Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [TRACKER] Runit support (Read 14389 times) previous topic - next topic
0 Members and 5 Guests are viewing this topic.

Re: [TRACKER] Runit support

Reply #60 –
Quote
The wiki was intended to follow stable releases, not testing.

Ok, I don't understand, just yesterday you were telling me the right package (20180414-4) should be in gremlins but the repository is not updated yet, now you are saying it is based on stable?
So 20180414-1 would have been fine it was 20180414-2 that messed me up?

If so, then I just picked the wrong damn day to try runit, didn't I?

For the rest of you not knowing what we are talking about, up until 36 hrs ago the pkg in gremlins was "a faulty one", what other faulty packages were there in gremlins since 4/16?

Code: [Select]
 gremlins/runit-artix 20180414-4 (init) [installed]
    Runit initscripts for Artix
 system/runit-artix 20180414-1 [installed: 20180414-4]
    Runit initscripts for Artix

Re: [TRACKER] Runit support

Reply #61 –
Quote from: fungalnet – on
Ok, I don't understand, just yesterday you were telling me the right package (20180414-4) should be in gremlins but the repository is not updated yet, now you are saying it is based on stable?
It's the wiki page that is based on stable. But the right unstable package is on gremlins (-4).

Quote from: fungalnet – on
So 20180414-1 would have been fine it was 20180414-2 that messed me up?

Yes.
now only the dinit guy in artix

Re: [TRACKER] Runit support

Reply #62 –
Ok, I managed by going back and forth to get it back and it is booting fine now, although my networking is still a mess and I need to clear this out still.  I will start another topic but under the runit hierarchy as it pertains to problems that developed from the runit transition.  Right now I have inet4 and inet6 but I have 3 lines of commands in autostart to get to have network access after X start.  Which means at console at stage 2 I have no access unless I run those commands. 

Ram use is comparable to that with OpenRC, by far higher than it is with Void with about the same exact things running on start.
To me that translates to the need to strip unnecessary crud off of it.

While utilizing some of the instructions systemd-free.artixlin...  for moving from that "other" init system into OpenRC, sddm and xorg settings went out of wack.  I was trying to go "back there" so I can move forward again.  I am still running on Gremlins and I will continue to report on development.
Right now I feel like the basement got flooded and I have just been able to move the water out but there is work to do.
 

Re: [TRACKER] Runit support

Reply #63 –
On the rc.conf file why can't there be options of what to run on stage 1 and what not?  (ie lvm, swap, btrfs, raid, etc)

Here is a clip of the s6 .conf file:

Code: [Select]
# Apply kernel runtime [yes|no]
KERNELRUNTIME=yes

# Boot with dmraid support [yes|no]
USEDMRAID=no

# Boot with btrfs support [yes|no]
USEBTRFS=no

# Boot with lvm support [yes|no]
# Do not forget to remake your initramfs with lvm2 hook on it
USELVM=no

#swap support [yes|no]
USESWAP=yes

#enable cgroups [yes|no]
CGROUPS=yes

Instead we get just error messages with runit of things that may not apply to our system.
Now I understand that you don't do runit development here, you just apply what comes from upstream, but can there be a modification?

Re: [TRACKER] Runit support

Reply #64 –
There are shell scripts in /etc/runit/core-services/ that are executed as stage one. I think every example you named is already handled by default (swap, the filesystems, etc.). Not sure about raid though, you might have to configure that one.

Re: [TRACKER] Runit support

Reply #65 –
Quote from: fungalnet – on
On the rc.conf file why can't there be options of what to run on stage 1 and what not?  (ie lvm, swap, btrfs, raid, etc)

Here is a clip of the s6 .conf file:

Code: [Select]
# Apply kernel runtime [yes|no]
KERNELRUNTIME=yes

# Boot with dmraid support [yes|no]
USEDMRAID=no

# Boot with btrfs support [yes|no]
USEBTRFS=no

# Boot with lvm support [yes|no]
# Do not forget to remake your initramfs with lvm2 hook on it
USELVM=no

#swap support [yes|no]
USESWAP=yes

#enable cgroups [yes|no]
CGROUPS=yes

Instead we get just error messages with runit of things that may not apply to our system.
Now I understand that you don't do runit development here, you just apply what comes from upstream, but can there be a modification?

I simply think it isn't necessary.

If you look carefully into our filesystems stage1, some will only be triggered if certain binaries are there (read: you installed it through a package). If you don't use btrfs you can uninstall btrfs-progs. If you don't have LVM don't install lvm2.

I would consider it unnecessary bloat.
now only the dinit guy in artix

Re: [TRACKER] Runit support

Reply #66 –
No I have run it with # .. same thing, but dbus is running, it is not like it isn't.
If dbus wasn't running should I or should I not have had network on console.  The problem was at the start of stage 2, not on desktop.

Here is some sv status now, when the problem is not there anymore, but what fixed it I am still trying to find out

Code: [Select]
# sv status /etc/runit/runsvdir/default/*  
run: /etc/runit/runsvdir/default/acpid: (pid 602) 15668s
run: /etc/runit/runsvdir/default/agetty-tty1: (pid 595) 15669s
run: /etc/runit/runsvdir/default/agetty-tty2: (pid 581) 15669s
run: /etc/runit/runsvdir/default/agetty-tty3: (pid 584) 15669s
run: /etc/runit/runsvdir/default/agetty-tty4: (pid 582) 15669s
run: /etc/runit/runsvdir/default/agetty-tty5: (pid 585) 15669s
run: /etc/runit/runsvdir/default/agetty-tty6: (pid 583) 15669s
run: /etc/runit/runsvdir/default/alsa: (pid 658) 15666s
down: /etc/runit/runsvdir/default/avahi-daemon: 0s, normally up, want up
run: /etc/runit/runsvdir/default/cronie: (pid 605) 15668s
fail: /etc/runit/runsvdir/default/dbus: unable to change to service directory: file does not exist
down: /etc/runit/runsvdir/default/dhclient: 1s, normally up, want up
fail: /etc/runit/runsvdir/default/dhcp: unable to change to service directory: file does not exist
run: /etc/runit/runsvdir/default/dhcpcd: (pid 603) 15668s
fail: /etc/runit/runsvdir/default/dhcpd: unable to change to service directory: file does not exist
down: /etc/runit/runsvdir/default/dhcpd4: 1s, normally up, want up
down: /etc/runit/runsvdir/default/dhcpd6: 1s, normally up, want up
run: /etc/runit/runsvdir/default/dmeventd: (pid 32448) 1268s
down: /etc/runit/runsvdir/default/elogind: 0s, normally up, want up
run: /etc/runit/runsvdir/default/haveged: (pid 645) 15667s
down: /etc/runit/runsvdir/default/ip6tables: 1s, normally up, want up
down: /etc/runit/runsvdir/default/iptables: 1s, normally up, want up
down: /etc/runit/runsvdir/default/lm_sensors: 1s, normally up, want up
fail: /etc/runit/runsvdir/default/lvm: unable to change to service directory: file does not exist
fail: /etc/runit/runsvdir/default/lvm2: unable to change to service directory: file does not exist
run: /etc/runit/runsvdir/default/lvmetad: (pid 654) 15666s
run: /etc/runit/runsvdir/default/mdadm: (pid 642) 15667s
run: /etc/runit/runsvdir/default/nfs-server: (pid 609) 15668s
down: /etc/runit/runsvdir/default/ntpd: 1s, normally up, want up
run: /etc/runit/runsvdir/default/rpcbind: (pid 601) 15668s
run: /etc/runit/runsvdir/default/rsyncd: (pid 631) 15667s
down: /etc/runit/runsvdir/default/sddm: 1s, normally up, want up
run: /etc/runit/runsvdir/default/sshd: (pid 596) 15669s
run: /etc/runit/runsvdir/default/statd: (pid 666) 15666s

Re: [TRACKER] Runit support

Reply #67 –
Quote from: fungalnet – on
No I have run it with # .. same thing, but dbus is running, it is not like it isn't.
If dbus wasn't running should I or should I not have had network on console.  The problem was at the start of stage 2, not on desktop.

Here is some sv status now, when the problem is not there anymore, but what fixed it I am still trying to find out

Code: [Select]
# sv status /etc/runit/runsvdir/default/*  
run: /etc/runit/runsvdir/default/acpid: (pid 602) 15668s
run: /etc/runit/runsvdir/default/agetty-tty1: (pid 595) 15669s
run: /etc/runit/runsvdir/default/agetty-tty2: (pid 581) 15669s
run: /etc/runit/runsvdir/default/agetty-tty3: (pid 584) 15669s
run: /etc/runit/runsvdir/default/agetty-tty4: (pid 582) 15669s
run: /etc/runit/runsvdir/default/agetty-tty5: (pid 585) 15669s
run: /etc/runit/runsvdir/default/agetty-tty6: (pid 583) 15669s
run: /etc/runit/runsvdir/default/alsa: (pid 658) 15666s
down: /etc/runit/runsvdir/default/avahi-daemon: 0s, normally up, want up
run: /etc/runit/runsvdir/default/cronie: (pid 605) 15668s
fail: /etc/runit/runsvdir/default/dbus: unable to change to service directory: file does not exist
down: /etc/runit/runsvdir/default/dhclient: 1s, normally up, want up
fail: /etc/runit/runsvdir/default/dhcp: unable to change to service directory: file does not exist
run: /etc/runit/runsvdir/default/dhcpcd: (pid 603) 15668s
fail: /etc/runit/runsvdir/default/dhcpd: unable to change to service directory: file does not exist
down: /etc/runit/runsvdir/default/dhcpd4: 1s, normally up, want up
down: /etc/runit/runsvdir/default/dhcpd6: 1s, normally up, want up
run: /etc/runit/runsvdir/default/dmeventd: (pid 32448) 1268s
down: /etc/runit/runsvdir/default/elogind: 0s, normally up, want up
run: /etc/runit/runsvdir/default/haveged: (pid 645) 15667s
down: /etc/runit/runsvdir/default/ip6tables: 1s, normally up, want up
down: /etc/runit/runsvdir/default/iptables: 1s, normally up, want up
down: /etc/runit/runsvdir/default/lm_sensors: 1s, normally up, want up
fail: /etc/runit/runsvdir/default/lvm: unable to change to service directory: file does not exist
fail: /etc/runit/runsvdir/default/lvm2: unable to change to service directory: file does not exist
run: /etc/runit/runsvdir/default/lvmetad: (pid 654) 15666s
run: /etc/runit/runsvdir/default/mdadm: (pid 642) 15667s
run: /etc/runit/runsvdir/default/nfs-server: (pid 609) 15668s
down: /etc/runit/runsvdir/default/ntpd: 1s, normally up, want up
run: /etc/runit/runsvdir/default/rpcbind: (pid 601) 15668s
run: /etc/runit/runsvdir/default/rsyncd: (pid 631) 15667s
down: /etc/runit/runsvdir/default/sddm: 1s, normally up, want up
run: /etc/runit/runsvdir/default/sshd: (pid 596) 15669s
run: /etc/runit/runsvdir/default/statd: (pid 666) 15666s

If you really symlinked all directories in /etc/runit/sv to /run/runit/service, then you didn't install dbus-runit and NetworkManager-runit, plain and simple.

If you have both dbus and NetworkManager service running (and by running I meant properly in a runsv process) you should have something like this in your pstree -a output.

Code: [Select]
runit,1
  |-compton,1254
  |-dbus-daemon,1274 --syslog-only --fork --print-pid 5 --print-address 7 --session
  |-dbus-launch,1271 --autolaunch=c22ecdc4b8715fda2bdd99c05a7e7132 --binary-syntax --close-stderr
  |-elogind,1037 --daemon
  |-runsvdir,772 -P /run/runit/service...
  |   |-runsv,778 alsa
  |   |   `-pause,802
  |   |-runsv,779 acpid
  |   |   |-acpid,864 -f
  |   |   `-svlogd,801 -tt /var/log/acpid
  |   |-runsv,780 agetty-tty5
  |   |   `-agetty,804 tty5 38400 linux
  |   |-runsv,781 openntpd
  |   |   |-logger,797 -t openntpd -p daemon notice
  |   |   `-ntpd,863 -d -s
  |   |       `-ntpd,947      
  |   |           `-ntpd,950     
  |   |-runsv,782 socklog
  |   |   |-socklog,862 unix /dev/log
  |   |   `-svlogd,799 /var/log/socklog/cron /var/log/socklog/daemon /var/log/socklog/debug /var/log/socklog/errors ...
  |   |-runsv,783 NetworkManager
  |   |   `-NetworkManager,800 -n
  |   |       |-{NetworkManager},1018
  |   |       `-{NetworkManager},1020
  |   |-runsv,784 agetty-tty1
  |   |   `-login,803     
  |   |-runsv,785 tlp
  |   |   `-pause,796
  |   |-runsv,786 agetty-tty3
  |   |   `-agetty,793 tty3 38400 linux
  |   |-runsv,787 agetty-tty4
  |   |   `-agetty,792 tty4 38400 linux
  |   |-runsv,788 dbus
  |   |   `-dbus-daemon,798 --system --nofork --nopidfile
  |   |-runsv,789 dnscrypt-proxy
  |   |   |   `-{dnscrypt-proxy},1528
  |   |   `-svlogd,805 -t /var/log/dnscrypt-proxy
  |   |-runsv,790 agetty-tty6
  |   |   `-agetty,794 tty6 38400 linux
  |   `-runsv,791 agetty-tty2
  |       `-agetty,795 tty2 38400 linux
  |-udevd,291 --daemon
  `-wpa_supplicant,1043 -u

Note that there are two different dbus processes. One is a child process of a runsv process (PID 798) and one is a direct child of runit (PID 1274). The dbus process with PID 1274 are launched (in this case) by Firefox (and Firefox immediately closed after I manually killed the dbus process), this means that your "running" dbus process will listen to Firefox and only Firefox, and will not work with any other processes (elogind, NetworkManager, wicd, etc.)

So no. In your case, dbus is not running as a proper service. It is likely that you're not installing both dbus-runit and networkmanager-runit and you didn't enable both services (because the service doesn't even exist).

Code: (fungalnet) [Select]
fail: /etc/runit/runsvdir/default/dbus: unable to change to service directory: file does not exist

Also, the problem is likely fixed by enabling the dhcpcd runit service.
now only the dinit guy in artix

Re: [TRACKER] Runit support

Reply #68 –
What I did (remember the day the reps weren't working and got the bad runit-artix ---3 instead of 4) was to make a list of all the runscripts I had installed and find the corresponding -runit pkgs.  Except for a few that had no match, I removed ALL the -openrc and replaced them with -runit + runit + runit-artix
Then I had no network and decided to get rid of networkmanager
Then I still had problems with dhcpd which was running, but something was missing and by enabling (linking all services I had installed and available somehow cured the network problem). 
I have no firefox, I have palemoon, which might be working the same way.
But dbus-runit was installed all along.  If I hadn't linked dbus or any of those other ones that produce the error it wouldn't show up in sv status when I run it for the whole run directory
A week has gone by and the only thing I get is that I did something wrong, and I am not asking for blame, but I did follow ALL instructions on the wiki, just did it when a bad runit-artix file was in the repositories.

Now WHAT?

Re: [TRACKER] Runit support

Reply #69 –
Could you post your output of a couple of things?

Code: [Select]
$ ls /run/runit/service

And also

Code: [Select]
$ pstree -a

Re: [TRACKER] Runit support

Reply #70 –
Need I remind you that the installation does not have functionality problems now, but the way I fixed it was by linking pretty every service there was to the active directory
I just replace some of the ids with 111s and 000s
Code: [Select]
$ ls  /run/runit/service
acpid        agetty-tty4  avahi-daemon  dhcp    dhcpd6    ip6tables   lvm2        ntpd     sshd
agetty-tty1  agetty-tty5  cronie        dhcpcd  dmeventd  iptables    lvmetad     rpcbind  statd
agetty-tty2  agetty-tty6  dbus          dhcpd   elogind   lm_sensors  mdadm       rsyncd
agetty-tty3  alsa         dhclient      dhcpd4  haveged   lvm         nfs-server  sddm



$ pstree -a
runit
  |-at-spi-bus-laun
  |   |-dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf 
--nofork--print-addre
  |   `-3*[{at-spi-bus-laun}]
  |-at-spi2-registr --use-gnome-session
  |   `-2*[{at-spi2-registr}]
  |-conky -c /home/artix2/.conky/TeejeeTech/ProcessPanel
  |   `-3*[{conky}]
  |-conky -c /home/artix2/.conky/TeejeeTech/CpuPanel
  |   `-8*[{conky}]
  |-dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
  |-dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
  |-dbus-launch --autolaunch 1111111111111111111111111 --binary-syntax --close-stderr
  |-dbus-launch --autolaunch=1111111111111111111111111 --binary-syntax --close-stderr
  |-gconfd-2
  |-lxpolkit
  |   `-2*[{lxpolkit}]
  |-runsvdir -P /run/runit/service...
  |   |-runsv agetty-tty4
  |   |   `-agetty tty4 38400 linux
  |   |-runsv agetty-tty2
  |   |   `-agetty tty2 38400 linux
  |   |-runsv nfs-server
  |   |   `-rpc.mountd --foreground
  |   |-runsv sshd
  |   |   `-sshd -D
  |   |-runsv agetty-tty6
  |   |   `-agetty tty6 38400 linux
  |   |-runsv dhcpcd
  |   |   `-dhcpcd -B -M
  |   |-runsv dhclient
  |   |-runsv dhcpd4
  |   |-runsv rpcbind
  |   |   `-rpcbind -f
  |   |-runsv agetty-tty3
  |   |   `-agetty tty3 38400 linux
  |   |-runsv mdadm
  |   |   `-mdadm --monitor --scan --syslog
  |   |-runsv iptables
  |   |-runsv dmeventd
  |   |   `-dmeventd -f
  |   |-runsv haveged
  |   |   `-haveged -w 1024 -v 1 -F
  |   |-runsv dhcpd6
  |   |-runsv agetty-tty5
  |   |   `-agetty tty5 38400 linux
  |   |-runsv rsyncd
  |   |   `-rsync --daemon --no-detach
  |   |-runsv alsa
  |   |   `-pause
  |   |-runsv elogind
  |   |-runsv ip6tables
  |   |-runsv sddm
  |   |-runsv statd
  |   |   `-rpc.statd -F -d
  |   |-runsv cronie
  |   |   `-crond -n
  |   |-runsv lm_sensors
  |   |-runsv lvmetad
  |   |   `-lvmetad -f
  |   |-runsv agetty-tty1
  |   |   `-login     
  |   |       `-bash
  |   |           `-sudo sddm
  |   |               `-sddm
  |   |                   |-Xorg -nolisten tcp -auth ...
  |   |                   |   `-4*[{Xorg}]
  |   |                   |-sddm-helper --socket 
/tmp/sddm-auth00000000000000000000000000000 ...
  |   |                   |   `-openbox --startup /usr/lib/openbox/openbox-autostart OPENBOX
  |   |                   |       `-lxterminal
  |   |                   |           |-bash
  |   |                   |           |   `-pstree -a
  |   |                   |           |-bash
  |   |                   |           |   `-nano /tmp/tmpnote
  |   |                   |           `-{lxterminal}
  |   |                   `-{sddm}
  |   |-runsv ntpd
  |   |-runsv acpid
  |   |   `-acpid -f
  |   `-runsv avahi-daemon
  |-sh /home/artix2/.config/openbox/autostart
  |   `-conky -c /home/artix2/.conky/Gotham/Gotham
  |       `-3*[{conky}]
  `-udevd --daemon


$ sudo sv status *
run: acpid: (pid 627) 1712s
run: agetty-tty1: (pid 623) 1713s
run: agetty-tty2: (pid 622) 1713s
run: agetty-tty3: (pid 620) 1713s
run: agetty-tty4: (pid 624) 1713s
run: agetty-tty5: (pid 621) 1713s
run: agetty-tty6: (pid 625) 1713s
run: alsa: (pid 641) 1712s
down: avahi-daemon: 1s, normally up, want up
run: cronie: (pid 645) 1712s
fail: dbus: unable to change to service directory: file does not exist
down: dhclient: 1s, normally up, want up
fail: dhcp: unable to change to service directory: file does not exist
run: dhcpcd: (pid 642) 1712s
fail: dhcpd: unable to change to service directory: file does not exist
down: dhcpd4: 1s, normally up, want up
down: dhcpd6: 1s, normally up, want up
run: dmeventd: (pid 639) 1712s
down: elogind: 1s, normally up, want up
run: haveged: (pid 638) 1712s
down: ip6tables: 1s, normally up, want up
down: iptables: 1s, normally up, want up
down: lm_sensors: 0s, normally up, want up
fail: lvm: unable to change to service directory: file does not exist
fail: lvm2: unable to change to service directory: file does not exist
run: lvmetad: (pid 643) 1712s
run: mdadm: (pid 636) 1712s
run: nfs-server: (pid 646) 1712s
down: ntpd: 1s, normally up, want up
run: rpcbind: (pid 640) 1712s
run: rsyncd: (pid 631) 1712s
down: sddm: 1s, normally up, want up
run: sshd: (pid 628) 1712s
run: statd: (pid 632) 1712s

Re: [TRACKER] Runit support

Reply #71 –
Looking at that output, I honestly don't know how your system is running okay because it just looks completely broken to me. Here's my output right now (with admittedly much fewer services but you get the picture).

Code: [Select]
$ ls /run/runit/service 
agetty-tty1  agetty-tty2  agetty-tty3  agetty-tty4  agetty-tty5  agetty-tty6  cgmanager  cupsd	dbus  dhcpcd  elogind


$ pstree -a
runit
  ├─at-spi-bus-laun
  │   ├─dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
  │   └─3*[{at-spi-bus-laun}]
  ├─at-spi2-registr --use-gnome-session
  │   └─2*[{at-spi2-registr}]
  ├─dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
  ├─dconf-service
  │   └─2*[{dconf-service}]
  ├─gconfd-2
  ├─git-credential- /home/user/.cache/git/credential/socket
  ├─gvfs-udisks2-vo
  │   └─2*[{gvfs-udisks2-vo}]
  ├─gvfsd
  │   ├─gvfsd-dnssd --spawner :1.2 /org/gtk/gvfs/exec_spaw/5
  │   │   └─2*[{gvfsd-dnssd}]
  │   ├─gvfsd-network --spawner :1.2 /org/gtk/gvfs/exec_spaw/2
  │   │   └─3*[{gvfsd-network}]
  │   ├─gvfsd-trash --spawner :1.2 /org/gtk/gvfs/exec_spaw/0
  │   │   └─2*[{gvfsd-trash}]
  │   └─2*[{gvfsd}]
  ├─gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
  │   └─5*[{gvfsd-fuse}]
  ├─gvfsd-metadata
  │   └─2*[{gvfsd-metadata}]
  ├─ibus-daemon -drx
  │   ├─ibus-dconf
  │   │   └─3*[{ibus-dconf}]
  │   ├─ibus-engine-sim
  │   │   └─3*[{ibus-engine-sim}]
  │   ├─ibus-extension-
  │   │   └─3*[{ibus-extension-}]
  │   ├─ibus-ui-gtk3
  │   │   └─3*[{ibus-ui-gtk3}]
  │   ├─python /usr/share/ibus-anthy/engine/main.py --ibus
  │   │   └─3*[{python}]
  │   └─2*[{ibus-daemon}]
  ├─ibus-portal
  │   └─2*[{ibus-portal}]
  ├─ibus-x11 --kill-daemon
  │   └─2*[{ibus-x11}]
  ├─palemoon
  │   └─55*[{palemoon}]
  ├─pcmanfm
  │   └─2*[{pcmanfm}]
  ├─polkitd --no-debug
  │   └─15*[{polkitd}]
  ├─pulseaudio --start
  │   └─{pulseaudio}
  ├─runsvdir -P /run/runit/service...
  │   ├─runsv agetty-tty2
  │   │   └─agetty tty2 38400 linux
  │   ├─runsv cgmanager
  │   │   └─cgmanager -q -m name=systemd
  │   ├─runsv agetty-tty6
  │   │   └─agetty tty6 38400 linux
  │   ├─runsv agetty-tty1
  │   │   └─login     
  │   │       └─sway
  │   │           ├─Xwayland :0 -rootless -terminate -listen 32 -listen 33 -wm 37
  │   │           │   └─9*[{Xwayland}]
  │   │           ├─sway
  │   │           ├─swaybar -b bar-0
  │   │           │   └─sh -c while :; do date +'%Y-%m-%d %H:%M:%S %p'; sleep 1; done
  │   │           │       └─sleep 1
  │   │           ├─swaybg 0 /usr/share/backgrounds/warty-final-ubuntu.png fill
  │   │           └─{sway}
  │   ├─runsv dhcpcd
  │   │   └─dhcpcd -B -M
  │   ├─runsv agetty-tty5
  │   │   └─agetty tty5 38400 linux
  │   ├─runsv cupsd
  │   │   └─cupsd -f
  │   ├─runsv agetty-tty3
  │   │   └─agetty tty3 38400 linux
  │   ├─runsv elogind
  │   │   └─elogind
  │   ├─runsv dbus
  │   │   └─dbus-daemon --system --nofork --nopidfile
  │   └─runsv agetty-tty4
  │       └─agetty tty4 38400 linux
  ├─udevd --daemon
  ├─udisksd
  │   └─4*[{udisksd}]
  ├─urxvt
  │   └─zsh
  │       └─weechat
  │           └─8*[{weechat}]
  ├─urxvt
  │   └─zsh
  │       └─R -q
  └─urxvt
      └─zsh
          └─pstree -a


$ sudo sv status *
run: agetty-tty1: (pid 639) 28256s
run: agetty-tty2: (pid 643) 28256s
run: agetty-tty3: (pid 640) 28256s
run: agetty-tty4: (pid 641) 28256s
run: agetty-tty5: (pid 642) 28256s
run: agetty-tty6: (pid 638) 28256s
run: cgmanager: (pid 647) 28256s
run: cupsd: (pid 646) 28256s
run: dbus: (pid 644) 28256s
run: dhcpcd: (pid 649) 28256s
run: elogind: (pid 645) 28256s

Looking at the output of the /run/runit/service directory, I don't know where in the world "dhcp", "dhcpd", "dhcpd4",  "dhcpd6", "lvm", or "lvm2" came from. Those aren't proper names for any of those. The dhcpcd-runit package gives you the "dhcpcd" directory which is the correct one. It also looks like dbus and elogind are both down which is probably not good and will give you trouble later. Try force reinstalling the dbus-runit and elogind-runit packages. There may be some other things wrong in there but I don't use most of those services so I don't really know for sure.

Re: [TRACKER] Runit support

Reply #72 –
I had already tried reinstalling, from what I had in cache.  No difference.
dbus now is giving me the correct output.  What I did was using sv restart
The screen turned black and everything controlling anything valished.  I had to kill it with the button.
When I rebooted dbus was running fine, (it was running before as well but was giving the error about directory not found, although it was there)?
I tried the same with lvm* and dhcp* but no change.
If dhcp is not running, although I see the processes going up and down the process list) how come I have a flawless connection now?

Re: [TRACKER] Runit support

Reply #73 –
You also have "dhcpcd" in your directory which is the correct name of the service (which is why you have internet). The other ones are extra folders you should get rid of. It's good that you have dbus working properly. Is elogind running ok now as well? If you get rid of those extra/unneeded directories ("dhcp", "dhcpd", "dhcpd4",  "dhcpd6", "lvm", and "lvm2"),  I think your output should be normal.

Re: [TRACKER] Runit support

Reply #74 –
Quote from: fungalnet – on
Now WHAT?

Calm down. You seem to be very worked up. Be patient.

Quote from: fungalnet – on
What I did (remember the day the reps weren't working and got the bad runit-artix ---3 instead of 4) was to make a list of all the runscripts I had installed and find the corresponding -runit pkgs.  Except for a few that had no match, I removed ALL the -openrc and replaced them with -runit + runit + runit-artix

runit-artix has nothing to do with this. We're talking purely about dbus-runit since your problem is with NetworkManager (and really, why go back to this thread when we have a separate thread). When you did something and you're corresponding with someone over the forums to troubleshoot your problem about your "network problems", you immediately notfiy them. You're a little too late.

Quote from: fungalnet – on
But dbus-runit was installed all along.  If I hadn't linked dbus or any of those other ones that produce the error it wouldn't show up in sv status when I run it for the whole run directory

Did you even read your own error?

Code: (fungalnet) [Select]
fail: /etc/runit/runsvdir/default/dbus: unable to change to service directory: file does not exist

However, since your problem is resolved, I'm not replying to you anymore for this matter since this discussion is quickly turning into a flamefest (if it isn't a flamefest already).
now only the dinit guy in artix