<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.sysutils.supervision.general">
    <title>gmane.comp.sysutils.supervision.general</title>
    <link>http://blog.gmane.org/gmane.comp.sysutils.supervision.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2206"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2200"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2198"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2189"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2184"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2182"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2181"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2174"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2169"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2165"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2163"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2162"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2161"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2158"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2149"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2147"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2133"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2130"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2127"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2112"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2206">
    <title>Suddenly sv does not start, gives a timeout</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2206</link>
    <description>&lt;pre&gt;One of our servers has started to have a problem with runit. Even after a
reboot we get this:

$ sv start ./service/unicorn/
timeout: down: ./service/unicorn/: 1s, normally up, want up

This has just started without (as far as we can tell) there being any
change to the server. I've even nuked the ./service/* directory so that it
will get rebuilt when the application is deployed (via capistrano - this is
a Rails app) but that does not seem to help.

The other 23 servers which are set up in the same way have no problem so I
am at a loss as to where to start looking.

Any idea of where I should look for clues?
&lt;/pre&gt;</description>
    <dc:creator>Peter Hickman</dc:creator>
    <dc:date>2013-05-22T09:30:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2200">
    <title>Default permissions on supervise/ok</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2200</link>
    <description>&lt;pre&gt;I'd like to allow any user to access supervise/ok, in order to run
`sv stat`, but not to access supervise/control. My understanding is that
this is safe, as supervise/ok is a read-only interface. Is this accurate,
and is this a reasonable idea? Anything I should be warned about? Am I
overlooking anything important?

chmod 755 supervise
chmod 666 supervise/ok



&lt;/pre&gt;</description>
    <dc:creator>eam&lt; at &gt;frap.net</dc:creator>
    <dc:date>2013-05-20T23:52:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2198">
    <title>s6-portable-utils-1.0.0 compile error</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2198</link>
    <description>&lt;pre&gt;Hi

This seems to be corner case as I have never before set the
flag-usert, flag-usemon, flag-noipv6, flag-forcedevr flags for
skalibs.

exec ./compile s6-ln.c
exec ./load s6-ln -lrandom -lstdcrypto -lstddjb `cat socket.lib`
/package/prog/skalibs/library/libstddjb.a(taia_clockmon.o): In function `taia_clockmon':
taia_clockmon.c:(.text+0x22): undefined reference to `clock_gettime'
/package/prog/skalibs/library/libstddjb.a(taia_clockmon.o): In function `taia_clockmon_init':
taia_clockmon.c:(.text+0xce): undefined reference to `clock_gettime'
/package/prog/skalibs/library/libstddjb.a(sysclock_get.o): In function `sysclock_get':
sysclock_get.c:(.text+0x21): undefined reference to `clock_gettime'
collect2: ld returned 1 exit status
make[2]: *** [s6-ln] Error 1
make[2]: Leaving directory `/package/admin/s6-portable-utils-1.0.0/compile/skaembutils'
make[1]: *** [.done] Error 2
make[1]: Leaving directory `/package/admin/s6-portable-utils-1.0.0/compile/skaembutils'
make: *** [.done] Error 2

&lt;/pre&gt;</description>
    <dc:creator>Vallo Kallaste</dc:creator>
    <dc:date>2013-05-14T20:17:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2189">
    <title>Installing on Centos</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2189</link>
    <description>&lt;pre&gt;I've installed runit on a Centos 5.8 box thus

wget http://smarden.org/runit/runit-2.1.1.tar.gz
tar zxf runit-2.1.1.tar.gz
(cd admin/runit-2.1.1; ./package/install; ./package/install-man)

No problem with that (so far) but when I compare it to my Ubuntu 10.04
installation I seem to be missing things like

1) /etc/sv and /etc/service
2) When is ps ax it does not appear to be running anywhere...
3) The sv command only seems to be available to root, unlike on Ubunto
where other accounts can access it

Have I missed a step in the installation somewhere. Googling produces too
many results and not a lot of information.
&lt;/pre&gt;</description>
    <dc:creator>Peter Hickman</dc:creator>
    <dc:date>2013-05-07T09:30:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2184">
    <title>runit logging questions</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2184</link>
    <description>&lt;pre&gt;Hi,

Logging:

* Do you need to create 2 run scripts (/etc/sv/myservice/run,
/etc/sv/myservice/log/run)? Or does the log/run supersede the myservice/run
script?
* The directory specified in the log run script to svlogd (eg ./main)--does
this live in the log directory?
* Do I need to create the log directory or does the svlogd directory do
that for me
* Where does the log go? I've looked in this main directory, and it is
still empty.

Cheers!

/Raymond
&lt;/pre&gt;</description>
    <dc:creator>Raymond Barlow</dc:creator>
    <dc:date>2013-04-30T19:43:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2182">
    <title>[announce] s6-1.0.0</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2182</link>
    <description>&lt;pre&gt; Hello,
 As a part of a massive series of skarnet.org releases, s6-1.0.0 is out.

 This release fixes a very rare bug in s6-log. It also includes the
ucspilogd program (previously shipped as a standalone package). Most
importantly, it adds support for non-slashpackage installations, which
means that distributors may now install the binaries wherever they want.

 http://skarnet.org/software/s6/

 Enjoy,
 Bug-reports welcome.

&lt;/pre&gt;</description>
    <dc:creator>Laurent Bercot</dc:creator>
    <dc:date>2013-02-12T10:38:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2181">
    <title>[announce] perp-2.07: persistent process supervision</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2181</link>
    <description>&lt;pre&gt;Announcing the latest release of perp, a persistent process
supervisor and service management framework for un!x:

 http://b0llix.net/perp/distfiles/perp-2.07.tar.gz


What's New:

 * not much!

 * PERP_SVPID and PERP_SVSECS defined for reset runscripts!

 * slightly bigger release number!

 * not much else!


Get your free copy now!!!

Download:
 http://b0llix.net/perp/distfiles/perp-2.07.tar.gz

Checksums:
 http://b0llix.net/perp/distfiles/perp-2.07.md5
 http://b0llix.net/perp/distfiles/perp-2.07.sha1

Changes:
 http://b0llix.net/perp/site.cgi?page=CHANGES


What the Heck?

perp is a persistent process supervisor and service management
framework, similar in purpose to the venerable daemontools
package, while providing a modern update with many advantages:

 * easy configuration: in place service activation and no
   symlinks!

 * everthing administered in /etc/perp

 * fully FHS compatible

 * scanner/supervisor/controller runs as a single process

 * all context switching for multiple supervisor processes&lt;/pre&gt;</description>
    <dc:creator>Wayne Marshall</dc:creator>
    <dc:date>2013-01-14T10:52:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2174">
    <title>s6-log taking 100% CPU</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2174</link>
    <description>&lt;pre&gt;Hi

I have noticed that s6-log enters busyloop after failing to rotate
the log. Some data:

 * I don't have strace output at hand, but from memory it was
   infinite stream of identical poll() related lines.
 * s6-log runs as: s6-log -b s16777215 n25 S0 !xz -0q /var/service/nslcd/log
 * Happens only for service loggers missing the log/state file. Most
   service loggers do not have the log/state file, this is probably
   my mistake in some deployment script. 
 * There are following lines in s6-svscan log:

s6-log (processor child): fatal: unable to open_readb /var/service/nslcd/log/state: No such file or directory
s6-log: warning: processor failed in /var/service/nslcd/log

It seems that this is caused by my mistake but perhaps it could be
handled better?

BR,
&lt;/pre&gt;</description>
    <dc:creator>Vallo Kallaste</dc:creator>
    <dc:date>2012-12-13T14:19:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2169">
    <title>s6-0.17</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2169</link>
    <description>&lt;pre&gt;Trying to compile against dietlibc:

Making subsystem pipe-tools...
make[1]: Entering directory `/package/admin/s6-0.17/compile/pipe-tools'
exec ./gen-EXPORT &amp;gt; EXPORT-
./gen-Makefile &amp;gt; Makefile.real &amp;amp;&amp;amp; make -f Makefile.real &amp;amp;&amp;amp; : &amp;gt; .done
make[2]: Entering directory `/package/admin/s6-0.17/compile/pipe-tools'
exec ./compile s6-cleanfifodir.c
exec ./load s6-cleanfifodir -lftrigw -lstddjb
exec ./compile s6-ftrig-listen.c
s6-ftrig-listen.c:15:22: fatal error: execline.h: No such file or directory
compilation terminated.
make[2]: *** [s6-ftrig-listen.o] Error 1
make[2]: Leaving directory `/package/admin/s6-0.17/compile/pipe-tools'
make[1]: *** [.done] Error 2
make[1]: Leaving directory `/package/admin/s6-0.17/compile/pipe-tools'
make: *** [.done] Error 2


s6-0.16 compiles without problems, same computer, same conf-compile
contents, same skalibs (1.2.8), and same execline (1.1.6).

TIA
&lt;/pre&gt;</description>
    <dc:creator>Jorge Almeida</dc:creator>
    <dc:date>2012-11-14T19:01:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2165">
    <title>s6-log does not obey umask</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2165</link>
    <description>&lt;pre&gt;Hi

I am not sure if it is intended behaviour or not.
echo |/command/umask 0027 s6-log /some/dir will create lock and
state files with permissions 0640, but current with 0744. It is the
world-readable bit I am concerned with.
&lt;/pre&gt;</description>
    <dc:creator>Vallo Kallaste</dc:creator>
    <dc:date>2012-11-13T20:46:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2163">
    <title>background does not set LASTPID</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2163</link>
    <description>&lt;pre&gt;Hi

I noticed that 'background' does not set LASTPID.
&lt;/pre&gt;</description>
    <dc:creator>Vallo Kallaste</dc:creator>
    <dc:date>2012-11-11T16:19:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2162">
    <title>Further chpst mods: alarm, documenting -r and -t, etc.</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2162</link>
    <description>&lt;pre&gt;I've put my changes to chpst in a small fork of runit here:
https://github.com/pilcrow/runit .  A diff against "vendor" branch
shows all changes.

Features:

 - '-N' reopens '-012' to /dev/null, before any chroot, rather than closing
 - '-2' no longer swallows errors
 - '-A n' sets an alarm(2) for n seconds, or clears inherited alarm if n is zero
 - rlimit options accept '=', just like softlimit(8)
 - ./package/check (crudely) tests the new '-N' switch

Perhaps better than the above:

 - man and html document previously undocumented '-r' and '-t' switches
 - man and html clarify that rlimit opts are soft limits, silently
capped at the hard limit

-Mike

&lt;/pre&gt;</description>
    <dc:creator>Mike Pomraning</dc:creator>
    <dc:date>2012-10-02T05:03:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2161">
    <title>[PATCH] chpst qua softlimit: fix usage message</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2161</link>
    <description>&lt;pre&gt;Issue:  chpst sometimes displays its primary usage text when invoked
as 'softlimit', which text is inappropriate for that utility.

Demonstration:

  # OK
  $ ./chpst -b softlimit ./chpst
  usage: softlimit [-a allbytes] [-c corebytes] ...

  # oops!
  $ ./chpst -b softlimit ./chpst -a INVALID
  usage: softlimit [-vP012] [-u user[:group]] [-U user[:group]] ...

Patch:

diff --git a/src/chpst.c b/src/chpst.c
index f1b8ed9..2886e96 100644
--- a/src/chpst.c
+++ b/src/chpst.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -446,7 +446,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; void getlarg(long *l) {
   unsigned long ul;

   if (str_equal(optarg, "=")) { *l =-1; return; }
-  if (optarg[scan_ulong(optarg, &amp;amp;ul)]) usage();
+  if (optarg[scan_ulong(optarg, &amp;amp;ul)]) softlimit_usage();
   *l =ul;
 }
 void softlimit(int argc, const char *const *argv) {

-Mike

&lt;/pre&gt;</description>
    <dc:creator>Mike Pomraning</dc:creator>
    <dc:date>2012-09-29T04:21:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2158">
    <title>[PATCH] chpst in/out/err enhancement</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2158</link>
    <description>&lt;pre&gt;The attached patch:

1. Preserves complaints to standard error even under '-2'
2. Adds a '-N' ("null device") flag which modifies '-[012]' to
redirect /dev/null with appropriate access modes, rather than merely
closing fds
3. Documents #2

Rationale:  #1 above helps me debug otherwise quiet ``chpst -2
/oops/enoent'' typographical errors.  #2 guards against some programs'
naive assumptions about the availability and nature of fds 0, 1 and 2.

Implementation notes:  The '-N' flag redirects before chroot, and
respects the improved semantics of '-2' (that is, chpst can still
complain of exec failures).  Unmodified '-[012]' are now implemented
with close-on-exec rather than close().  Other than the possibility of
new complaints to stderr under '-2', the patch is behaviorally
backward compatible.

Let me know if you think this is wrong-headed.

-Mike
&lt;/pre&gt;</description>
    <dc:creator>Mike Pomraning</dc:creator>
    <dc:date>2012-09-27T20:58:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2149">
    <title>[magic sv logging]</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2149</link>
    <description>&lt;pre&gt;Hi,
I am trying to write a python script which can be put in place of
svlogd/multilog, but I am stuck just at the beginning.

The test script is pretty simple, it just forwards stdin to stdout:

def main():

    while True:
        try:
            line = raw_input()
            print 'got', line
        except EOFError:
            print 'done'
            pass

  if __name__ == '__main__':
    main()

It works, but not as desired, as the script is being restarted by runsv
constantly, it seems after it finishes reading stdin. Could you
please help me how can run that continuously listening to stdin?

cheers,
Serge
&lt;/pre&gt;</description>
    <dc:creator>Sergiusz Pawlowicz</dc:creator>
    <dc:date>2012-09-20T23:35:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2147">
    <title>s6-ftrigrd link dosn't install in /command</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2147</link>
    <description>&lt;pre&gt;Hi laurent,

I did a build of s6 with special slashpackages path.
I succeeded to build and install on filesystem the result.

But in using binary s6-ftrig-listen1, it complains about /command/s6-ftrigrd which is link missing
even if the link target exists.

Could you confirm that please??
Many thanks.

Regards,
 

Vincent de RIBOU
région Ouest - France
belzo2005-dolphin&amp;lt; at &amp;gt;yahoo.fr&lt;/pre&gt;</description>
    <dc:creator>Vincent de RIBOU</dc:creator>
    <dc:date>2012-09-10T15:05:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2133">
    <title>What is the process group hack</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2133</link>
    <description>&lt;pre&gt;Hello,

I Could not figure out what "process group hack" is supposed to be
utilized for ??
Is it used to supervise daemons that stubbornly fork into the background.
Could anyone please explain with an example, i would be really helpful.
I have to the best of my abilities RTFM'ed and searched the internet.

Thank you,
Harish

&lt;/pre&gt;</description>
    <dc:creator>harish badrinath</dc:creator>
    <dc:date>2012-04-26T15:15:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2130">
    <title>Getting a process to run as root</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2130</link>
    <description>&lt;pre&gt;I have an application that scans log files that is written in Ruby. It
is installed as the user log_watcher but needs to be run as root so
that it can have the rights to read the various log files that it
needs. Essentially the service/log_watcher/run file comes down to
"sudo ruby log_watcher.rb", the log_watcher user has passwordless sudo
rights.

We have runit / supervise installed but when we try and start the
application it complains about supervise/ok or supervise/lock being
unavailable which means that the process is not being restarted after
a reboot.

How do I get to run the process as root from the log_watcher user.
I've tried various things I've seen in the wiki and got back from
googling but nothing seems to work. Or perhaps there is another way
around this?

&lt;/pre&gt;</description>
    <dc:creator>Peter Hickman</dc:creator>
    <dc:date>2012-04-25T10:20:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2127">
    <title>[announce] perp-2.05: persistent process supervision</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2127</link>
    <description>&lt;pre&gt;Announcing the latest release of perp, a persistent process
supervisor:

 http://b0llix.net/perp/distfiles/perp-2.05.tar.gz


What's New:

 * a couple of bugfixes for bigfuxes!

 * enhanced runuid(8) utility!

 * bigger release number!


About:

perp is a service supervisor similar in purpose to the venerable
daemontools package, providing a modern update with many
advantages:

 * easy configuration: in place service activation and no
   symlinks!

 * everthing administered in /etc/perp

 * fully FHS compatible

 * scanner/supervisor/controller runs as a single process

 * all context switching for multiple supervisor processes is
   eliminated

 * service reset capability

 * pretty good troff -man documentation

 * colorized(!) service lister, readable timestamps...

 * no slashpackage, no slashcommand, no slashdoc...


More:

 http://b0llix.net/perp/


Best regards,

Wayne

&lt;/pre&gt;</description>
    <dc:creator>Wayne Marshall</dc:creator>
    <dc:date>2012-01-11T12:52:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2112">
    <title>Per-user service managers</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2112</link>
    <description>&lt;pre&gt;Hello,

I wrote this little program that manages per-user runsv instances.
For each user in the "svusers" group it starts a service manager in
their ~/.sv directory.  The service manager runs as that user, so as
long as they can run the sv program, they can manage their own
services.

Per-user service managers run independently of user logins.

I've released this under the BSD license, and it's available on github.

https://github.com/eichlan/usersv

I hope you find this program useful, I know I have.

--Mike Buland

&lt;/pre&gt;</description>
    <dc:creator>Mike Buland</dc:creator>
    <dc:date>2011-10-20T16:26:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2111">
    <title>announce: s6-0.14</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.supervision.general/2111</link>
    <description>&lt;pre&gt; s6-0.14 is out.

 This release fixes a bug that caused a SIGPIPE handler to not be
properly reset after a call to ftrigw_notify().
(The bug was introduced by the sig_restore() semantics change in
skalibs-1.0.3, which was a good thing, but ftrigw_notify() relied on the
old semantics.)
 Sorry about that.

 http://www.skarnet.org/software/s6/

 Enjoy.
 Bug-reports always welcome.

&lt;/pre&gt;</description>
    <dc:creator>Laurent Bercot</dc:creator>
    <dc:date>2011-08-09T08:36:45</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.sysutils.supervision.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.sysutils.supervision.general</link>
  </textinput>
</rdf:RDF>
