Re: Shellshock-vulnerable version still most obvious on ftp.gnu.org

[Glenn Morris]

Chet Ramey wrote:

> (The link is to
> http://git.savannah.gnu.org/cgit/bash.git/snapshot/bash-master.tar.gz).  I
> cannot change the main bash webpage to include that text.

I'm not sure what you mean by that last sentence; but just in case you
don't know, anyone with write access to the code repository for a
gnu.org project on Savannah also has write access to the web pages
repository.

Simply follow the instructions at http://savannah.gnu.org/cvs/?group=bash
to checkout the web-pages repository, ie:

  export CVS_RSH=ssh
  cvs -z3 -d:ext:@cvs.savannah.gnu.org:/web/bash co bash

Simply committing a change to CVS will update the gnu.org web pages
almost immediately.

Re: Hitting C-c C-c in Emacs' *shell* causes segmentation fault

[Glenn Morris]

Chet Ramey wrote:

> What is C-c C-c supposed to do?

It pretty much just sends SIGINT.

Re: Pesky here-document warnings

[Glenn Morris]

> https://bugzilla.redhat.com/show_bug.cgi?id=486844

Actually, that might not be relevant, sorry.

Re: Pesky here-document warnings

[Glenn Morris]

Mun wrote:

> I'm running on a Red Hat Enterprise Linux 5.5 system, and my guess is
> that the system is running something on my behalf. 

https://bugzilla.redhat.com/show_bug.cgi?id=486844

Re: "Terminated" message from kill

[Glenn Morris]

Chet Ramey wrote:

> This is a classic race condition.

I see. Thanks for the explanation.

"Terminated" message from kill

[Glenn Morris]

Hi,

This is a question similar to one from September 2006:

http://lists.gnu.org/archive/html/bug-bash/2006-09/msg00077.html


Using bash 3.2.39 on x86_64 RHEL5.2, I have a script with contents:


function bar ()
{
sleep 10 &
pid=$!
exec 3>&2 2>/dev/null
kill $pid
#usleep 1
exec 2>&3 3>&-
}

bar


If I run this script 1000 times via a loop, I get a handful of messages
(the number varies) of the form:

/path/to/script: line 14: 10327 Terminated  sleep 10

If I uncomment the "usleep" line, I get no such messages at all.

If I comment out the usleep and both exec lines, I get a handful of messages.

If I then uncomment the usleep line, I get 1000 messages.


Hence, some questions:

1) Shouldn't the production of the "terminated" message be deterministic?

2) Why does sleeping make a difference?

3) Is there a "right" way to suppress the "terminated" message?

Thanks in advance.