Re: One Crash per Log-in Caused by: echo '' > >(echo)

2019-03-22 Thread jake
It is intermittent. Let's not give up just yet. I just reproduced it again after reading your response. https://www.dropbox.com/s/7yy6kbpjlx1zpty/Reproduced.png?dl=0 Have your tried booting into runlevel 1 or 3 and doing it first thing? Recall it only happens once per log-in, so if you have

Re: "here strings" and tmpfiles

2019-03-22 Thread Greg Wooledge
On Fri, Mar 22, 2019 at 10:28:52AM -0400, Chet Ramey wrote: > On 3/20/19 8:19 AM, Greg Wooledge wrote: > > > Even if Chet changed how here docs work in bash 5.1, nobody would > > be safe to use those features in their "I'm feeding a password with > > a here string" scripts for at least 20 years, b

Re: "here strings" and tmpfiles

2019-03-22 Thread Chet Ramey
On 3/20/19 8:19 AM, Greg Wooledge wrote: > Even if Chet changed how here docs work in bash 5.1, nobody would > be safe to use those features in their "I'm feeding a password with > a here string" scripts for at least 20 years, because there will > still be people running older versions of bash for

Re: "here strings" and tmpfiles

2019-03-22 Thread Chet Ramey
On 3/19/19 9:07 AM, Daniel Kahn Gillmor wrote: > Thanks for the feedback, Eduardo-- > > On Mon 2019-03-18 17:40:17 -0700, Eduardo A. Bustamante López wrote: >> I don't think the implementation details of herestrings are documented >> anywhere, >> and I'm not too sure if they should (i.e. IMO if y

Re: "here strings" and tmpfiles

2019-03-22 Thread Chet Ramey
On 3/20/19 7:36 AM, Daniel Kahn Gillmor wrote: > On Tue 2019-03-19 09:31:55 -0400, Greg Wooledge wrote: >> There are scripts that *rely* on the seekability of the temporary files >> created by here-documents and here-strings. "Improving" the "situation" >> would break backward compatibility. > >

Re: "here strings" and tmpfiles

2019-03-22 Thread Chet Ramey
On 3/19/19 8:49 PM, Robert Elz wrote: > Date:Tue, 19 Mar 2019 08:25:50 -0400 > From:Greg Wooledge > Message-ID: <20190319122550.khv5jp66iobjo...@eeg.ccf.org> > > | Yes, just like here documents do. And have always done, in all shells. > > That's not correct. The

Re: "here strings" and tmpfiles

2019-03-22 Thread Chet Ramey
On 3/18/19 8:40 PM, Eduardo A. Bustamante López wrote: > Having said that, have you tried process substitution as an option? > > You should be able to do something like: > > > mycommand < <(printf %s 'super secret') > > > That will: > > - not write the 'super secret' string to the file-sys

Re: "here strings" and tmpfiles

2019-03-22 Thread Chet Ramey
On 3/19/19 8:25 AM, Greg Wooledge wrote: > On Mon, Mar 18, 2019 at 05:18:10PM -0400, Daniel Kahn Gillmor wrote: >> strace -o tmp/bash.herestring.strace -f bash -c 'cat <<<"hello there"' >> It turns out that this creates a temporary file, actually touching the >> underlying filesystem: > > Yes,

Re: "here strings" and tmpfiles

2019-03-22 Thread Chet Ramey
On 3/18/19 5:18 PM, Daniel Kahn Gillmor wrote: > hi bash developers-- > > I ran the following command to get a sense of how bash deals with here > strings under the hood: > > strace -o tmp/bash.herestring.strace -f bash -c 'cat <<<"hello there"' > > (i'm testing with bash 5.0-2 on debian tes