supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gnu.org>
To: debian-hurd@lists.debian.org
Cc: supervision@list.skarnet.org
Subject: runit for Debian GNU/Hurd
Date: Thu, 2 Aug 2007 00:35:57 +0200	[thread overview]
Message-ID: <20070801223557.GH6234@fencepost.gnu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2043 bytes --]

[CCed to <supervision@list.skarnet.org> purely for your information.]


Hello!

Michael, could you please do the following: apply the following patch to
the `runit' source package, run a Hurd package with the fifo patch I just
posted to bug-hurd
(<http://lists.gnu.org/archive/html/bug-hurd/2007-08/msg00002.html>; or
ask me to simply provide you with a fixed `/hurd/fifo' binary), build the
`runit' package and upload to GNUAB.


So far I don't really have an idea what is going wrong here, but I shall
describe what is supposed to happen:

`current' contains some data lines.  ``t2'' is written into `config'.
``foo'' is piped into the `svlogd' program.  The `svlogd' program will be
left running for three seconds.  During this three seconds the following
is supposed to happen inside the `svlogd' program: ``foo'' is appended to
`current'; two seconds after the last modification of `current' (remind
the ``t2'' configuration string in `config') the file `current' is
supposed to be rotated away and afterwards be empty.  What does happen on
a Hurd system is that apparently three seconds are not enough to do this
job (which I can't really believe...) or that something goes wrong when
`svlogd' is reading the last-modified time stamp of `current'.
Nevertheless, enlarging the time interval to five seconds is enough to
make it work as expected...


#v+
--- admin/runit-1.7.2/src/svlogd.check~	2007-08-02 00:16:35.910000000 +0200
+++ admin/runit-1.7.2/src/svlogd.check	2007-08-02 00:16:35.920000000 +0200
@@ -20,7 +20,7 @@
 cat "${ctmp}"/current
 
 echo t2 >"${ctmp}"/config
-( echo foo; sleep 3 ) |svlogd "${ctmp}"
+( echo foo; sleep 5 ) |svlogd "${ctmp}"
 echo $?
 cat "${ctmp}"/current
 
#v-

For being able to apply the patch, you first have to unpack the included
tarball.  This is most easily done by simply starting to build the
package, wait until the test suite fails (perhaps it'll also simply work
for you?  ;-), then apply the patch and resume the build.


Regards,
 Thomas

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

             reply	other threads:[~2007-08-01 22:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 22:35 Thomas Schwinge [this message]
2007-08-01 23:52 ` Thomas Schwinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070801223557.GH6234@fencepost.gnu.org \
    --to=tschwinge@gnu.org \
    --cc=debian-hurd@lists.debian.org \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).