From: Andreas Schwab <schwab@suse.de>
To: "Dirk Försterling" <dirk.foersterling@eorga.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: stdin/pipe problem with kernel 2.4.9
Date: 21 Sep 2001 12:40:56 +0200 [thread overview]
Message-ID: <jebsk4j07b.fsf@sykes.suse.de> (raw)
In-Reply-To: <3BA9D8F8.5000801@eorga.com>
In-Reply-To: <3BA9D8F8.5000801@eorga.com> (Dirk Försterling's message of "Thu, 20 Sep 2001 13:54:32 +0200")
Dirk Försterling <dirk.foersterling@eorga.com> writes:
|> I repost this because you may have been distracted by the date contained
|> in the old subject line. So far there was no response at all. No hint,
|> no trick, no RTFM (pointers?) or whatever. So far I wasn't able to find
|> anything related using google, the kernel docs and the linux-kernel archive.
|> The SuSE support won't help me with 2.4 and the support database doesn't contain
|> any (findable) article related to my problem. So I decided to repost my question.
This has nothing to do with the kernel, it's a problem with some versions
of cron (which closes stdin/out/err at startup instead of redirecting them
to /dev/null and subsequently gets confused when spawning the jobs).
Andreas.
--
Andreas Schwab "And now for something
Andreas.Schwab@suse.de completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
prev parent reply other threads:[~2001-09-21 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 11:54 stdin/pipe problem with kernel 2.4.9 Dirk Försterling
2001-09-21 10:40 ` Andreas Schwab [this message]
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=jebsk4j07b.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=dirk.foersterling@eorga.com \
--cc=linux-kernel@vger.kernel.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