Re: bash problem

On 1/2/20 8:45 AM, Wheatley, Martin R wrote: > It appears that there may be an issue when bash terminates a shell as a > result of TMOUT expiring. > > I was attempting to enter "dc_command show media | grep YD" to the shell and > this is the terminal output... > > OLDuser@hostname $ dc_command

bash problem

It appears that there may be an issue when bash terminates a shell as a result of TMOUT expiring. I was attempting to enter "dc_command show media | grep YD" to the shell and this is the terminal output... OLDuser@hostname $ dc_command show mediatimed out waiting for input: auto-logout NEWuser@

Re: #! /bin/sh bash problem

Dear Bob, Thank you for your answers. Bob Proulx wrote: John B. Brown wrote: Thank you for that reminder of my mortality. :-) Bob Proulx wrote: Also, /usr/bin/bash is not a normal location for bash. Normally bash would reside in /bin/bash . Perhaps you also have one ther

Re: #! /bin/sh bash problem

John B. Brown wrote: > Thank you for that reminder of my mortality. :-) > Bob Proulx wrote: > >Also, /usr/bin/bash is not a normal location for bash. Normally bash > >would reside in /bin/bash . Perhaps you also have one there? > > > > ls -ld /bin/bash /usr/local/bin/bash I suggested lo

Re: #! /bin/sh bash problem

John B. Brown wrote: -rwsrwsr-x 1 root root 604040 2007-09-21 16:16 /bin/bash* A setuid/setgid root /bin/bash is a really bad idea. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTE

Re: #! /bin/sh bash problem

Dear Bob, Thank you for that reminder of my mortality. Bob Proulx wrote: John B. Brown wrote: Description: Attempting to run 'configure', or any shell script with #! /bin/sh, results in the error message: "bash: ./configure: /usr/bin/bash: bad interpreter: Permission denied" I s

Re: #! /bin/sh bash problem

John B. Brown wrote: From: jbb To: bug-bash@gnu.org Subject: gnu software "configure" error Configuration Information [Automatically generated, do not change]: Machine: i586 OS: linux-gnu Compiler: gcc -I/usr/src/packages/BUILD/bash-3.2 -L/usr/src/packages/BUILD/bash-3.2/../readline-5.2 Compila

Re: #! /bin/sh bash problem

John B. Brown wrote: > Description: Attempting to run 'configure', or any shell > script with #! /bin/sh, results in the error message: > > "bash: ./configure: /usr/bin/bash: bad interpreter: > Permission denied" I suspect that the permissions on /usr/bin/bash are preventing you from run

#! /bin/sh bash problem

From: jbb To: bug-bash@gnu.org Subject: gnu software "configure" error Configuration Information [Automatically generated, do not change]: Machine: i586 OS: linux-gnu Compiler: gcc -I/usr/src/packages/BUILD/bash-3.2 -L/usr/src/packages/BUILD/bash-3.2/../readline-5.2 Compilation CFLAGS: -DPROG

Re: bash problem with #!, rev 2

Thanks for your learned analysis. 1. I kind of like the way zsh handles it. 2. In any case, I'll use #!/usr/bin/env http://Yost.com/computers/compileAndGo 3. I'll change my pages to reflect the change by around noon 15:00 UTC+8. Thanks again. Dave ___

Re: bash problem with #!, rev 2

Dave Yost wrote: > In other words, a program starting with > > #!/usr/local/bin/compileAndGo > > should invoke /usr/local/bin/compileAndGo, and compileAndGo is a > program starting with > > #!/bin/bash That is not a portable combination. The #! needs to be a machine executable and not a s

bash problem with #!, rev 2

[added a diagnosis near the end.] Please see http://Yost.com/computers/compileAndGo That page describes a #!/bin/bash script called compileAndGo, which is used as the program for a #! script. In other words, a program starting with #!/usr/local/bin/compileAndGo should invoke /usr/local/bi

bash problem with #!

Please see http://Yost.com/computers/compileAndGo That page describes a #!/bin/bash script called compileAndGo, which is used as the program for a #! script. In other words, a program starting with #!/usr/local/bin/compileAndGo should invoke /usr/local/bin/compileAndGo, and compileAndGo is