On Sep 21 2020, Dale R. Worley wrote:
> Andreas Schwab writes:
>> On Sep 10 2020, Chet Ramey wrote:
>>
>>> yy. Process substitution processes now get their input from /dev/null, since
>>> they are asynchronous, not interactive, and not jobs.
>>
>> That breaks scripts that want to filter stdin
On Tue, Sep 22, 2020 at 2:01 PM Robert Elz wrote:
> Date:Tue, 22 Sep 2020 10:02:07 +0800
> From:Clark Wang
> Message-ID: <
> cadv8-ogf0hev-ckegxy9dq1ypcz4bdpkjy_7aex83o1db93...@mail.gmail.com>
>
> | In an interactive shell (in case this matters), run bash -c 'sleep
Date:Tue, 22 Sep 2020 16:47:39 +0800
From:Clark Wang
Message-ID:
| Ah right. I misunderstood something else. When I run
|
| $ ssh 127.0.0.1 '{ sleep 120 | cat; } & exit'
Yes, in that case the shell running the command list (the {} thing)
typically hangs aro
On 9/21/20 11:57 AM, Adam Stewart wrote:
> Thanks Chet,
>
> That patch did the trick! All tests pass now. Thanks again for your help!
Glad to help.
> P.S. I'm going to add this patch to the Spack package manager. Would you or
> anyone else be interested in "maintaining" Spack's bash build recip
On Tue, Sep 22, 2020 at 5:07 PM Robert Elz wrote:
>
> With -t, there's no pty, when the shell exits, everything ends up
> closed - but the mechanism for this escapes me (what bash &/or sshd
> sees differently). You'd do better to ask on an ssh related list
> I expect.
>
Found the question at h
On 9/22/20 5:07 AM, Robert Elz wrote:
> | Then, how should we explain that
> |
> | $ ssh -t 127.0.0.1 'sleep 120 &'
> |
> | would complete immediately?
>
> With -t, there's no pty
The opposite -- -t forces pty allocation.
--
``The lyf so short, the craft so long to lerne.'' - Chauce
The documentation says:
'ENV'
Similar to 'BASH_ENV'; used when the shell is invoked in POSIX Mode
(*note Bash POSIX Mode::).
However, as described elsewhere in the manual, BASH_ENV is used
specifically for non-interactive shells, whereas ENV is used specifically
for interactive shells.
Clark Wang writes:
> Then, how should we explain that
>
> $ ssh -t 127.0.0.1 'sleep 120 &'
>
> would complete immediately?
One thing to check is whether ssh is giving you a pty in various
circumstances. Execute the "tty" command, e.g. "ssh 127.0.0.1 tty".
Once you know whether the remote Bash
Andreas Schwab writes:
> On Sep 21 2020, Dale R. Worley wrote:
>
>> Andreas Schwab writes:
>>> On Sep 10 2020, Chet Ramey wrote:
>>>
yy. Process substitution processes now get their input from /dev/null,
since
they are asynchronous, not interactive, and not jobs.
>>>
>>> That
