From: B S Srinidhi <srinidhi@deeproot.co.in>
Subject: Re: problems with QMAILQUEUE and reading stdin
Date: Mon, 29 May 2006 10:53:01 +0530 [thread overview]
Message-ID: <1148880181.19941.3.camel@avirat> (raw)
In-Reply-To: <20060529015814.GA15937@run.galis.org>
Hi,
On Sun, 2006-05-28 at 21:58 -0400, George Georgalis wrote:
> I'm dealing with a frustrating problem where my QMAILQUEUE program
> is not working because it cannot read stdin.
>
> 2006-05-29_00:58:31.79998 tcpsvd: info: status 3/20
> 2006-05-29_00:58:31.80038 tcpsvd: info: pid 10614 from 204.152.190.11
> 2006-05-29_00:58:31.80098 tcpsvd: info: start 10614 sta.galis.org:69.31.23.138 ::204.152.190.11:51459 ./peers.cdb/0
> 2006-05-29_00:58:32.04704 /var/qmail/bin/prequeue: cannot open /dev/stdin: error 9
> 2006-05-29_00:58:32.15075 tcpsvd: info: end 10614 exit 0
>
'error 9' means "Bad file number". So, its nothing to with your
permissions or anything else.
> This is the line from /var/qmail/bin/prequeue that's causing the
> error:
>
> tmp="$pq/`/usr/pkg/bin/safecat "$pq/tmp" "$pq" </dev/stdin`" || exit 71 # put message to disk, if possible
>
hmm... I don't know what exactly should happen here, but wouldn't it be
possible to do this:
`cat /dev/stdin | /usr/pkg/bin/safecat "$pq/tmp" "$pq"`
??
Hope this helps.
Srinidhi.
--
ASCII ribbon campaign ( ) B S Srinidhi
- against HTML email X http://srinidhi.deeproot.co.in
& vCards / \ DeepRoot Linux
next prev parent reply other threads:[~2006-05-29 5:23 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 [this message]
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
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=1148880181.19941.3.camel@avirat \
--to=srinidhi@deeproot.co.in \
/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).