RE: logout from interactive subshell

> What about in your login (.bash_profile, etc) exporting a > variable, say > ROOT_PID=$$ and having a command/function/alias 'kill -s SIGHUP > $ROOT_PID'? This is equivalent to killing the rlogin connection, but > should clean up nicely if all you have are shells. Excellent idea! Thank you fo

Re: bash 3.2 match operator problem

Ok, so at least I'm not crazy; there is some kind of bug. When you have a patch I'm eager to help test it. Thank you, JGH On Thu, 12 Oct 2006, Chet Ramey wrote: Ok, here is a smaller 3 line test case. I have attempted to handle the parenthesis as you instructed. Under bash 3.0.17 BASH_REMAT

[patch] touchup ulimit docs in bash-3.2

looks like the latest release is missing just 1 last thing in the ulimit documentation with the new rlimit features ... patch attached -mike pgpYzDtWR3t3W.pgp Description: PGP signature add missing docs for -e and -r options --- builtins/ulimit.def +++ builtins/ulimit.def @@ -24,7 +24,7 @@ $BU

Re: logout from interactive subshell

Very often I do the following pattern: (1) rlogin to a foreign host (2) Invoke a subshell (for example because I'm setting a Clearcase View) (3) Logout from the host Step (3) needs two steps: First I have to type 'exit' to leave the subshell, and then either 'exit' or 'logout' to leave

Re: logout from interactive subshell

Com MN PG P E B Consultant 3 wrote: Does someone know how to deal with the following situation? Very often I do the following pattern: (1) rlogin to a foreign host (2) Invoke a subshell (for example because I'm setting a Clearcase View) (3) Logout from the host Step (3) needs two step

Re: bash 3.2 match operator problem

> Ok, here is a smaller 3 line test case. I have attempted to handle > the parenthesis as you instructed. Under bash 3.0.17 BASH_REMATCH > gets the 4 pieces. Under bash 3.2 I only get BASH_REMATCH=() > True, it no longer crashes. But it doesn't work either... I understand the problem, and have

Re: bash 3.2 match operator problem

Ok, here is a smaller 3 line test case. I have attempted to handle the parenthesis as you instructed. Under bash 3.0.17 BASH_REMATCH gets the 4 pieces. Under bash 3.2 I only get BASH_REMATCH=() True, it no longer crashes. But it doesn't work either... #!/bin/bash [[ jbig2dec-0.9-i586-001.tgz

Re: bash 3.2 match operator problem

John Gatewood Ham <[EMAIL PROTECTED]> writes: > Thank you for your reply. > > I removed the quotes and the script crashes. There must be more > required to convert my code and I hope someone will help. It is > only 1 line, and once I know the new rules I can convert everything > else on my own.

Re: bash 3.2 match operator problem

Thank you for your reply. I removed the quotes and the script crashes. There must be more required to convert my code and I hope someone will help. It is only 1 line, and once I know the new rules I can convert everything else on my own. I get this when just removing teh quotes on the right ha

Re: bash 3.2 match operator problem

> Machine Type: i586-pc-linux-gnu > > Bash Version: 3.2 > Patch Level: 0 > Release Status: release > > Description: > I just upgraded to bash 3.2 and my scripts quit working for matching. > The test case below will say 'Life is good' in bash 3.1.17, but on bash > 3.2 I get 'Upgrade of doom retu

Re: bash-3.2 parse error

Greg Schafer wrote: > Hi > > ncurses-5.5 fails to build with bash-3.2 installed as sh. Here's the > distilled testcase: > > > cat > testcase << "EOF" > TABSIZE=`grep -v '^[ #]' $CAPS | grep -v "^$" | grep -v "^capalias"| grep -v > "^infoalias" | wc -l` > EOF > > $ bash -n testcase > testcase:

Re: Bash-3.2 available for FTP

On Thu, Oct 12, 2006 at 09:29:33AM -0400, Chet Ramey wrote: > Introduction > > > The first public release of bash-3.2 is now available with the URLs Is this version supposed to use the Translation Project ? The last bash versi

Readline-5.2 available for FTP

The first public release of the GNU Readline library, version 5.2, is now available for FTP with the URLs ftp://ftp.cwru.edu/pub/bash/readline-5.2.tar.gz ftp://ftp.gnu.org/pub/gnu/readline/readline-5.2.tar.gz and from the usual GNU mirror sites. This distribution is essentially a standalone vers

Bash-3.2 available for FTP

Introduction The first public release of bash-3.2 is now available with the URLs ftp://ftp.cwru.edu/pub/bash/bash-3.2.tar.gz ftp://ftp.gnu.org/pub/gnu/bash/bash-3.2.tar.gz and from the usual GNU mirror sites. This tar file does not include the formatted documentation (postscript, d

RE: logout from interactive subshell

> >(1) rlogin to a foreign host > >(2) Invoke a subshell (for example because I'm setting a > Clearcase > > View) > >(3) Logout from the host > > > > Step (3) needs two steps: First I have to type 'exit' to leave the > > subshell, and then either 'exit' or 'logout' to leave the > log

RE: logout from interactive subshell

> > I can't use traps here, because I know only at "exit time", whether > > I want to logout completely, or just go up one level. > > $ call_and_exit() { "$@"; if test $? -eq 42; then exit; fi; } > $ call_and_exit cleartool ... > $ exit 42 This looks clever. Maybe one should use "exit 42" too in

Re: logout from interactive subshell

"Com MN PG P E B Consultant 3" <[EMAIL PROTECTED]> writes: > I can't use traps here, because I know only at "exit time", whether > I want to logout completely, or just go up one level. $ call_and_exit() { "$@"; if test $? -eq 42; then exit; fi; } $ call_and_exit cleartool ... $ exit 42 Andreas.

RE: logout from interactive subshell

> >(1) rlogin to a foreign host > >(2) Invoke a subshell (for example because I'm setting a > Clearcase > > View) > > Is it a subshell or a second-level shell? (In the first case, $$ and > $PPID remain the same.) Could you kindly explain the difference? I thought it's always the same - a

RE: logout from interactive subshell

> >rlogin foobar > >DO SOME STUFF > >cleartool setview myview # this creates a subshell > >DO MORE STUFF > >cleartool setview yourview # now I'm two subshells deep > >DO STILL MORE STUFF > ># Now I want to exit > >exit > >exit > >logout > > > > I would like t

Re: logout from interactive subshell

On 2006-10-12 10:47:38 +0200, Com MN PG P E B Consultant 3 wrote: > Does someone know how to deal with the following situation? > > Very often I do the following pattern: > >(1) rlogin to a foreign host >(2) Invoke a subshell (for example because I'm setting a Clearcase > View) Is it a s

Re: logout from interactive subshell

"Com MN PG P E B Consultant 3" <[EMAIL PROTECTED]> writes: > A typical application would go like this: > >rlogin foobar >DO SOME STUFF >cleartool setview myview # this creates a subshell >DO MORE STUFF >cleartool setview yourview # now I'm two subshells deep >DO STILL MORE

RE: logout from interactive subshell

> How about > function rlogin() {command rlogin "$@"; exit} > ? H I don't see how this could help me. Actually, your solution would EXIT the shell I came from, after the login has finished!! So I not only have to type all the "exit"s on the remote host, I would even loose my current shell

Re: logout from interactive subshell

On Thu, Oct 12, 2006 at 10:47:38AM +0200, Com MN PG P E B Consultant 3 wrote: >(1) rlogin to a foreign host >(2) Invoke a subshell (for example because I'm setting a Clearcase > View) >(3) Logout from the host > > Step (3) needs two steps: First I have to type 'exit' to leave the > sub

logout from interactive subshell

Does someone know how to deal with the following situation? Very often I do the following pattern: (1) rlogin to a foreign host (2) Invoke a subshell (for example because I'm setting a Clearcase View) (3) Logout from the host Step (3) needs two steps: First I have to type 'exit' to leav

bash-3.2 parse error

Hi ncurses-5.5 fails to build with bash-3.2 installed as sh. Here's the distilled testcase: cat > testcase << "EOF" TABSIZE=`grep -v '^[ #]' $CAPS | grep -v "^$" | grep -v "^capalias"| grep -v "^infoalias" | wc -l` EOF $ bash -n testcase testcase: line 1: unexpected EOF while looking for match