Re: Transition to supervision-scripts
Currently, sshd and winbindd just will not operate regardless of what is used or done. sshd complains the log service is not working and the service is down. Winbindd won't even start even if nmbd and smbd are both started as well. We even have issues getting kdm to login, unless it is working but auto-reloads itself. Rsyncd doesn't work either. Not sure about winbindd or rsyncd but the problem with sshd is that you need a reader for /dev/log. I'm pretty sure this isn't configurable without rebuilding openssh. The easiest is to run a supervised copy of rsyslog since it'll handle all the syslog logging channels correctly, plus enough other programs are going to expect a reader on the /dev/log socket that it's going to end up a requirement. Presumably you could also bypass this requirement by creating a fifo in some chroot directory (say /chroots/sshd/dev/log) and then running sshd funny chrooted with a reader (svlogd for example) using that file as input. It might fail depending on how sshd writes to the log socket though. I've been running xdm under supervision as my display manager for over a year, so my guess is that kdm is missing some supports. I'm still wanting to push for a RC2 release by December but at the rate scripts are still not working this may not happen, and I still have a lot of other scripts to get working as well. If anyone could get a checkout of the svn at the runit-for-lfs project page https://code.google.com/p/runit-for-lfs/ and see where we're going wrong, it would greatly help. Thanks. Jim -- If the doors of perception were cleansed every thing would appear to man as it is, infinite. For man has closed himself up, till he sees all things thru' narrow chinks of his cavern. -- William Blake
Re: Transition to supervision-scripts
I'd love to help with this. Any way we can move the runit scripts to github instead of svn / googlecode? Instead of rsyslog, socklog works great. Remote log forwarding handled by either svlogd or one of many other log forwarders. Rsyslog does too much and ends up having nasty failure scenarios that can lock up a system that I'd recommend trying to avoid. On Nov 7, 2014, at 12:31 PM, Colin Booth cathe...@gmail.com wrote: Currently, sshd and winbindd just will not operate regardless of what is used or done. sshd complains the log service is not working and the service is down. Winbindd won't even start even if nmbd and smbd are both started as well. We even have issues getting kdm to login, unless it is working but auto-reloads itself. Rsyncd doesn't work either. Not sure about winbindd or rsyncd but the problem with sshd is that you need a reader for /dev/log. I'm pretty sure this isn't configurable without rebuilding openssh. The easiest is to run a supervised copy of rsyslog since it'll handle all the syslog logging channels correctly, plus enough other programs are going to expect a reader on the /dev/log socket that it's going to end up a requirement. Presumably you could also bypass this requirement by creating a fifo in some chroot directory (say /chroots/sshd/dev/log) and then running sshd funny chrooted with a reader (svlogd for example) using that file as input. It might fail depending on how sshd writes to the log socket though. I've been running xdm under supervision as my display manager for over a year, so my guess is that kdm is missing some supports. I'm still wanting to push for a RC2 release by December but at the rate scripts are still not working this may not happen, and I still have a lot of other scripts to get working as well. If anyone could get a checkout of the svn at the runit-for-lfs project page https://code.google.com/p/runit-for-lfs/ and see where we're going wrong, it would greatly help. Thanks. Jim -- If the doors of perception were cleansed every thing would appear to man as it is, infinite. For man has closed himself up, till he sees all things thru' narrow chinks of his cavern. -- William Blake
Re: Transition to supervision-scripts
On Fri, Nov 7, 2014 at 1:09 PM, John Albietz inthecloud...@gmail.com wrote: I'd love to help with this. Any way we can move the runit scripts to github instead of svn / googlecode? True, runit-for-lfs is svn hosted, and supervision-scripts is mercurial. But git should push/pull both with little to no effort. I pull from git with mercurial all the time can push back changes. Just pulled the runit-for-lfs stuff onto a windows box using tortoisehg today, certainly a cross-platform cross-protocol cross-repository adventure, and everything survived. On Nov 7, 2014, at 12:31 PM, Colin Booth cathe...@gmail.com wrote: Not sure about winbindd or rsyncd but the problem with sshd is that you need a reader for /dev/log. I'm pretty sure this isn't configurable without rebuilding openssh. The easiest is to run a supervised copy of rsyslog since it'll handle all the syslog logging channels correctly, plus enough other programs are going to expect a reader on the /dev/log socket that it's going to end up a requirement. I suspect you are right about /dev/log. Some of my installs have socklog, some are still running rsyslog. So, yeah, in all cases, there is something listening to /dev/log on the other end...which would explain why my sshd works fine for me. The migration to a framework-agnostic set of scripts has exposed all kinds of warts, and logging is one of them. There's lots of stuff that is baked-in to use /dev/log, so there's a ton of development inertia that propels us to provide some kind of remedial support for it. I've been running xdm under supervision as my display manager for over a year, so my guess is that kdm is missing some supports. I guarantee that the kdm/gdm/lightdm display issues are all related to missing libraries and services. Lightdm uses dbus, but if dbus isn't up, the restart until it works kicks in and it will flicker the display so badly you'll want to punch the reset button. Even after I got lightdm up and stable, there are missing bits and pieces that are just implied to be there, but if they aren't then all kinds of options are simply non-functional. Yeah, fun times.
RE: Transition to supervision-scripts
Date: Mon, 3 Nov 2014 10:41:05 -0800 Subject: Transition to supervision-scripts From: avery.p.pa...@gmail.com To: supervision@list.skarnet.org The transition is complete and all framework-specific dependencies are being replaced with generic redirects. The runit-scripts repository will be deleted January 1st. Current the runit-for-lfs project has been studying how to get better control of some of the scripts we use also. Our project is still mostly incomplete with several services still unable to function. Avery, we actually used some of your scripts as a reference point as well with using chpst as a way to execute a service inside a group:user setting. However we still have a long ways to go with stabilizing the services. Thank you for hosting them. Currently, sshd and winbindd just will not operate regardless of what is used or done. sshd complains the log service is not working and the service is down. Winbindd won't even start even if nmbd and smbd are both started as well. We even have issues getting kdm to login, unless it is working but auto-reloads itself. Rsyncd doesn't work either. I'm still wanting to push for a RC2 release by December but at the rate scripts are still not working this may not happen, and I still have a lot of other scripts to get working as well. If anyone could get a checkout of the svn at the runit-for-lfs project page https://code.google.com/p/runit-for-lfs/ and see where we're going wrong, it would greatly help. Thanks. Jim
