[svlug] Re: Heads Up: bash 2.0 gives me headaches.

[Jeremy Brinkley]

On 17 Mar 1998, Stig HackVän wrote:

> The error message is definitely generated by bash '2.01.0(1)-release'
> because none of the other programs know the whole pipeline.
> 
> The point is that bash 1.x and apparently the version of bash that Jeremy
> Brinkley's running don't generate this error...
> 
> Jeremy, is there anything in your setup that might account for this
> difference? 

Well, I'm running bash '2.00.0(1)-release'; could this be a change
between 2.00.0(1) and 2.01.0(1)?  I looked at the environment in
which I ran your pipeline, and there's nothing weird like $BASH_OPTIONS
or anything like that set.  bash differs in its startup behavior
depending on if it's invoked as 'sh' or 'bash'; I invoked it as
bash.  I have no set options (like set -o monitor) in any of
my startup scripts.

Hope this helps.

  Jeremy Brinkley                  jeremy at wishbone.stanford.edu
  System Administrator             finger for PGP key (2.6.2) or
  Stanford Blood Center            http://wishbone.stanford.edu/~jeremy


--
echo "unsubscribe svlug" | mail majordomo at svlug.org
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ to unsubscribe