[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: exec 0</dev/null vs. nohup?
|
From: |
Jay K |
|
Subject: |
RE: exec 0</dev/null vs. nohup? |
|
Date: |
Tue, 1 Jun 2010 01:59:54 +0000 |
agreed, I put it back until/unless I see the problem again.
- Jay
----------------------------------------
> Date: Mon, 31 May 2010 21:24:28 +0200
> From: address@hidden
> To: address@hidden
> CC: address@hidden
> Subject: Re: exec 0
>
> Hello Jay,
>
> * Jay K wrote on Wed, May 26, 2010 at 03:17:39PM CEST:
>> I don't have the full background any longer, but I made
>> this change to a configure script:
>>
>> before:
>>
>> exec 7<&0 &1
>>
>> after:
>>
>> exec 6>&1
>>
>> my comment at the time (2008-06-03) was:
>> take minor change to older boilerplate from other nearby
>> configure files, in order to let it work under "nohup", on OpenBSD
>> otherwise there is an error about an invalid file handle
>>
>> Make sense?
>
> Not really, to me at least.
>
>> Clearly you are doing this on purpose though.
>
> Yes, we are. If you need the original standard input during the
> configure script, you can get at it with the AS_ORIGINAL_STDIN_FD
> macro; see `info Autoconf "File Descriptor Macros"'.
>
>> Maybe it just prints an error but there's no error?
>>
>> I just did a quick experiment with just
>>
>> exec 0
>>
>> and nohup but couldn't get an error.
>>
>> I've surely upgraded OpenBSD in the meantime.
>
> Well, if you cannot reproduce an error any more, I'll go and claim
> we shouldn't need to worry until you hit it again. ;-)
>
> Cheers,
> Ralf
>