A few lingering issues with Runit-For-LFS
Okay, I really need some advice from anyone who understands process supervision more than myself.
Currently, I'm still debugging several daemons for usage with Runit and have the following issues:
1. Daemons ran as a user and group state such as Avahi and D-Bus must be ran using the "chpst" utility to accurately launch the service in the user:group it's assigned to. these will be addressed in the next RC2 release which is pending and being worked on.
2. KDM does not allow logins. I'm not sure why this is happening, though I have my suspicions PAM is to blame and if it is then I recommend building without it, otherwise this needs further debugging. The /path/to also must be checked as well as kdm is installed both in /usr/bin and /opt/kde/bin. This will require an if/else checker.
3. sshd states as "down" while the logging doesn't start. This issue is still plaguing sshd. I'm not sure why but I've tried running it as user:group and directly.
4. Any services that perform a check must have the full /path/to for the service state check. This needs to be addressed by a patch to runit, or editing the run files.
5. Other services like winbindd, rsyncd, and other still are non-working also.
Any insight would be necessary.
I've also gained access to Avery Payne's svn until Dec when he is taking it offline. So far I'm touching up several scripts to use the proper execution methods, so hopefully this database will give some much needed insight.
On a side note, I have found one beneficial aspect of the Runit implementation since I built LFS-7.6, and tested it first with sysvinit.
Sysvinit has a nasty lingering bug during shutdown that causes the system to hang because the /(root) drive is still busy. I'm not sure if this is a script error, but it is present with sysvinit. With Runit the shutdown is clean and works without issues.
Last edited by ReaperX7; 11-06-2014 at 09:36 PM.
|
