Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Broken backquote behavior in bash?



 I forgot to include the version details: 

The server with the broken behavior is running CentOS release 5.2, 
and bash is bash-3.2-21.el5. 



On Thu, Jul 24, 2008 at 10:50 AM, John Abreau <[hidden email]> wrote: 
> I've got a server that's been giving strange errors lately. Most 
> noticeably, when I login, 
> I get several errors of the form 
> 
>    -bash: [: =: unary operator expected 
> 
> I've traced these to files under /etc/profile.d, and on further 
> testing I find that the 
> offending lines are using backquotes, e.g. 
> 
>        if [ `/usr/bin/id -u` = 0 ] ; then 
> 
> When I try to use backquotes on the command line on this server, I get 
> no output. 
> Even stranger, if I have a suspended vi job, then running something in 
> backquotes 
> terminates the vi process: 
> 
>    $ vi foo 
>    ^Z 
>    [1]+  Stopped                 nvi foo 
>    $ echo `echo bar` 
> 
>    [1]+  Terminated              nvi foo 
> 
> If I do this on my other systems, I get 
> 
>    $ echo `echo bar` 
>    bar 
> 
> and the vi job does not terminate. 
> 
> I've tried googling for these symptoms, but so far I haven't found a match. 
> Has anyone else run across this odd behavior? What could be causing it? 
> 
> 
> 
> -- 
> John Abreau / Executive Director, Boston Linux &amp; Unix 
> GnuPG KeyID: 0xD5C7B5D9 / Email: [hidden email] 
> GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 
> 


BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org