From: Kris Maglione <bsdaemon@comcast.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] A simple rc question
Date: Tue, 15 May 2007 20:24:10 -0400 [thread overview]
Message-ID: <20070516002410.GB96831@kris.home> (raw)
In-Reply-To: <13426df10705150838y7148f207m8fbc1631752fc8aa@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 277 bytes --]
Incidentally, might I suggest something to the effect of:
#!/bin/rc
fn cleanup { for(i in $apids) { echo kill >/proc/$i/note } }
fn sigint { cleanup }
fn sigterm { cleanup }
apids=()
for(f) {
tail -f $f | sed 's/^/'$f:/ &
apids = ($apids $apid)
}
wait
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2007-05-16 0:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 15:38 ron minnich
2007-05-15 15:46 ` Charles Forsyth
2007-05-15 15:48 ` erik quanstrom
2007-05-15 16:08 ` ron minnich
2007-05-15 16:18 ` Charles Forsyth
2007-05-16 0:24 ` Kris Maglione [this message]
2007-05-15 23:03 Benn Newman
2007-05-15 23:29 ` ron minnich
2007-05-15 23:35 ` Kris Maglione
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=20070516002410.GB96831@kris.home \
--to=bsdaemon@comcast.net \
--cc=9fans@cse.psu.edu \
/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).