From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1926 Path: news.gmane.org!not-for-mail From: "Ciprian Dorin Craciun" Newsgroups: gmane.comp.sysutils.supervision.general Subject: runsv and runsvdir problems Date: Mon, 27 Oct 2008 19:12:21 +0200 Message-ID: <8e04b5820810271012h3d798033t3599cdc468482c89@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1225127551 8789 80.91.229.12 (27 Oct 2008 17:12:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 27 Oct 2008 17:12:31 +0000 (UTC) To: supervision@list.skarnet.org Original-X-From: supervision-return-2161-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Oct 27 18:13:33 2008 connect(): Connection refused Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by lo.gmane.org with smtp (Exim 4.50) id 1KuVel-0007VT-MF for gcsg-supervision@gmane.org; Mon, 27 Oct 2008 18:13:31 +0100 Original-Received: (qmail 5551 invoked by uid 76); 27 Oct 2008 17:12:44 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 5535 invoked from network); 27 Oct 2008 17:12:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=8aZhETp7bxX2KvHzdIFla4NE8RehNZ/eX9sQgMVbeAA=; b=RJPiLNAGPCZoLtejLIGr3ixryooPjx/aHCDfEqBk5uIk8nGyeedBD2OtdmRy0Rojo9 JSSzpgrepj6oy44e/H0FUQdVOnWtpDkYqMl2k7qI+mH5BeIpLGVA8UAd+Bcb2b8AQC18 7hUPi9hOYe6+NAdsk75I/oxrCFufwl0TiB1nE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=I7HUWLRlN9LlCZvOIsLqlGZ28ceHBnkJhR9/OiUkFPrkG6kv0MwBl15Wozf+Wiis8V Q/Xhfa1rpPPOCE0aC0EfYmvYL7+6JQIVMI6MGd5u85wc52cxL7TfMfnrHb/fkyD1Qngg 7w6L6CVdwE7bFeTCjRRHoxEsPzrdaJ4l1Z/1M= Content-Disposition: inline Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1926 Archived-At: Hello all! First of all I must say I like the runit suite very much, and for about half a year I use it to manage almost all my services (normal ones and personal ones) on my laptop. Usually it runs smoothly, without any big problems, with a few exceptions: * first of all I use runsvdir for all the system services (like udev, getty, etc.); * also I allow each user (my self for now) to have a special service that runs another runsvdir; * as my services I use anything, from the X server and client, bittorent client, to the music player; Something like -- runsvdir /services \-- runsv /services/udev \-- runsv /services/getty-1 ... \-- runsv -> runsvdir /services/ciprian \-- runsv x \-- runsv vpn \-- ... But there are a couple of problems with this setup (so I propose some feature requests): * first of all a lot of services are not started by default (by using the 'down' file), but this doesn't stop runsv to start the logger => could there be an option to start the loggers only when the server actually starts? * if I send HUP to runsvdir /services it sends TERM to runsv /services/ciprian, which in turn sends TERM to runsvdir /services/ciprian which breaks, and leaves all my services dangling... => could there be an option to actually pass the same signal down the chain? (for example if I send TERM to runsv or runsvdir, it should send TERM downpath, and so for any other signal, for example USR1, etc.) * if I want to stop the runsvdir /services it sends the signal to all its children, but exists immediatly, and this is a problem if I stop it from an rc.0 or 6 script, because it should wait for all the children to actually stop; for now it leaves them dangling, and the unmounting of the file systems breaks... => could there be an option to actually make runsvdir to wait for it's children? * if a process takes to long to terminate (when it receives TERM signal), it would be nice for runsv to actually send KILL, but this should be configurable, as I wouldn't like to have runsv kill runsvdir like this; * (a small annoyance) it would be nice to be able to combine runsv and runsvdir into a single command, as this would reduce the number of runsv processes, until I actually need to start a service; So I repeat that runit suite is a very good one, but I would be very happy to see these problems solved. Thanks all, and keep up the good work, Ciprian Dorin Craciun.