Re: =~ behaves differently in bash 3.2 and 3.0
Thanks for all of your replies. BTW: I didn't find FAQ E14 in 3.2.39's `doc/FAQ' file. It's not updated yet?
Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client
Chet Ramey wrote: Serge Dussud - Sun Microsystems wrote: -z interpose . Could it be the explanation and a possible solution ? Well, let's try it. OK, great. Shall I understand that you're going to make a patch for this, or is there something else ? Serge Chet
Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client
Serge Dussud - Sun Microsystems wrote: > > > Chet Ramey wrote: >> Serge Dussud - Sun Microsystems wrote: >> >> >>> -z interpose >>> >>> . >>> >>> >>> Could it be the explanation and a possible solution ? >>> >> >> Well, let's try it. >> > OK, great. Shall I understand that you're going to make a patch for > this, or is there something else ? I was not going to issue a patch to 3.2 for this, but the change to configure.in will be in the next release. Chget -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client
Chet Ramey wrote: Serge Dussud - Sun Microsystems wrote: Chet Ramey wrote: Serge Dussud - Sun Microsystems wrote: -z interpose . Could it be the explanation and a possible solution ? Well, let's try it. OK, great. Shall I understand that you're going to make a patch for this, or is there something else ? I was not going to issue a patch to 3.2 for this, but the change to configure.in will be in the next release. ah OK, so I guess I need to work on a customized patched for 3.2 then. Any ideas yet of what the exact change will be in configure.bin so that I can apply to same in our deliveries ? Also, do you or would you have a bug # for reference ? TIA, Serge Chget
Re: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client
> ah OK, so I guess I need to work on a customized patched for 3.2 then. > Any ideas yet of what the exact change will be in configure.bin so that > I can apply to same in our deliveries ? *** ../bash-3.2-patched/configure.in2007-12-14 21:12:29.0 -0500 --- configure.in2008-10-23 09:10:57.0 -0400 *** *** 992,997 --- 1009,1017 sco3.2*) LOCAL_CFLAGS=-DMUST_UNBLOCK_CHLD ;; sunos4*) LOCAL_CFLAGS=-DSunOS4 ;; solaris2.5*) LOCAL_CFLAGS="-DSunOS5 -DSOLARIS" ;; + solaris2.8*) LOCAL_CFLAGS=-DSOLARIS LOCAL_LDFLAGS='-z interpose' ;; + solaris2.9*) LOCAL_CFLAGS=-DSOLARIS LOCAL_LDFLAGS='-z interpose' ;; + solaris2.10*) LOCAL_CFLAGS=-DSOLARIS LOCAL_LDFLAGS='-z interpose' ;; solaris2*)LOCAL_CFLAGS=-DSOLARIS ;; lynxos*) LOCAL_CFLAGS=-DRECYCLES_PIDS ;; linux*) LOCAL_LDFLAGS=-rdynamic # allow dynamic loading > Also, do you or would you have a bug # for reference ? Sorry, I don't. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.case.edu/~chet/
[bash 3.2.39] File descriptor 10 is always duplicated from 0 and cannot be closed
Hi, all: When I was doing some testing I found the file descriptor 10 is always duplicate of fd 0 and it cannot be closed. See the following commands: # echo $BASH_VERSION 3.2.39(1)-release # read line <&10 hello<--- input from keyboard # echo $line hello # exec 10<&-<--- try to close fd 10 # read line <&10<--- no error reported, so fd 10 is still open? hello<--- input from keyboard # echo $line hello # read line <&11<--- test with fd 11 bash: 11: Bad file descriptor #
