[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug #33134] spurious error when stdout is already closed
From: |
Philip Guenther |
Subject: |
Re: [bug #33134] spurious error when stdout is already closed |
Date: |
Thu, 21 Apr 2011 08:29:14 -0700 |
On Thu, Apr 21, 2011 at 3:50 AM, David Boyce <address@hidden> wrote:
> All quite true and admirably researched but this is not a
> standards-lawyering exercise, it's a software-engineering issue.
Why are you closing stdout instead of redirecting it to /dev/null?
Philip Guenther
- [bug #33134] spurious error when stdout is already closed, David Boyce, 2011/04/20
- Re: [bug #33134] spurious error when stdout is already closed, Philip Guenther, 2011/04/20
- Re: [bug #33134] spurious error when stdout is already closed, David Boyce, 2011/04/20
- Re: [bug #33134] spurious error when stdout is already closed, Philip Guenther, 2011/04/21
- Re: [bug #33134] spurious error when stdout is already closed, David Boyce, 2011/04/21
- RE: [bug #33134] spurious error when stdout is already closed, Martin Dorey, 2011/04/21
- Re: [bug #33134] spurious error when stdout is already closed, Philip Guenther, 2011/04/21
- Re: [bug #33134] spurious error when stdout is already closed, David Boyce, 2011/04/21
- Re: [bug #33134] spurious error when stdout is already closed,
Philip Guenther <=
- Re: [bug #33134] spurious error when stdout is already closed, David Boyce, 2011/04/21
[bug #33134] spurious error when stdout is already closed, David Boyce, 2011/04/21