supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "George Georgalis" <george@galis.org>
Subject: Re: problems with QMAILQUEUE and reading stdin
Date: Mon, 29 May 2006 11:49:32 -0400	[thread overview]
Message-ID: <20060529154932.GA7293@run.galis.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0605291036240.24384@e-smith.charlieb.ott.istop.com>

On Mon, May 29, 2006 at 10:38:19AM -0400, Charlie Brady wrote:
>
>On Mon, 29 May 2006, George Georgalis wrote:
>
>>I'd prefer to specify stdin as an argument, I'd like to retain
>>that style for helping people (including myself) interpret the
>>code.
>
>Why? If someone is reading code and they don't know that programs which 
>read stdin by default actually read stdin if you don't do anything 
>special, then they can't interpret much code at all, can they?

yeah, that's what I was thinking but did not say.

>Add a comment about reading stdin if you really think you need it.

yeah. that's what I did. I'll post the new ipsvd/QMAILQUEUE
program here after some more light mods and testing.

but I'd also like to get to the bottom of what looks like a
/bin/sh or kernel bug.

// George


-- 
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george@galis.org


  reply	other threads:[~2006-05-29 15:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-29  1:58 George Georgalis
2006-05-29  5:23 ` B S Srinidhi
2006-05-29 12:11   ` Charlie Brady
2006-05-29 12:19     ` B S Srinidhi
2006-05-29 13:37       ` George Georgalis
2006-05-29 14:38         ` Charlie Brady
2006-05-29 15:49           ` George Georgalis [this message]
2006-05-29 15:56             ` Charlie Brady
2006-05-29 20:48             ` George Georgalis
2006-05-29 13:59       ` Charlie Brady

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=20060529154932.GA7293@run.galis.org \
    --to=george@galis.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).