Daniel Brown wrote:
>> It's just file descriptor 3, that's all. In the old days, it was
>> occasionally called "stdaux", but AFAIK that's not used any more.
>
> Now that you mention it, I do seem to recall the term "STDAUX,"
> but I'm not sure if it's an actual memory or just one of those thi
On Mon, Mar 9, 2009 at 11:14, Per Jessen wrote:
>
> "UNIX Channel 3" ??
Sorry, Per, I must've stuttered. Yes, I said, "UNIX Channel 3."
For lack of a better reference. That not withstanding, the direct
response to Lynch's question still holds true.
> It's just file descriptor 3, that's all
From: Per Jessen
> Daniel Brown wrote:
>
>> On Sun, Mar 8, 2009 at 22:35, Richard Lynch wrote:
>>> I have a program sending/receiving data to/from my CLI script using:
>>>
>>> 0 stdin
>>> 1 stdout
>>> 2 stderr
>>> 3 ??
>>
>> UNIX Channel 3 is a non-standard stream resource, though I don'
Daniel Brown wrote:
> On Sun, Mar 8, 2009 at 22:35, Richard Lynch wrote:
>> I have a program sending/receiving data to/from my CLI script using:
>>
>> 0 stdin
>> 1 stdout
>> 2 stderr
>> 3 ??
>
> UNIX Channel 3 is a non-standard stream resource, though I don't
> believe it's even yet been
On Sun, Mar 8, 2009 at 22:35, Richard Lynch wrote:
> I have a program sending/receiving data to/from my CLI script using:
>
> 0 stdin
> 1 stdout
> 2 stderr
> 3 ??
UNIX Channel 3 is a non-standard stream resource, though I don't
believe it's even yet been given a name, so we'll have to cha
I have a program sending/receiving data to/from my CLI script using:
0 stdin
1 stdout
2 stderr
3 ??
0, 1, and 2 are trivial.
How do I access 3?
I tried /dev/fd/3 and failed to open it...
Got no error messages about why it failed to open, it just failed.
Am I missing something?
--
Some p
6 matches
Mail list logo