On Tue, May 15, 2007 at 05:13:43PM -0800, Fielder George Dowding wrote:
> Kevin Miller wrote:
> > Fielder George Dowding wrote:
> >> I have run into a strange situation (my workstation at the Mabel T.
> >> Caverly Senior Center) where bash does not act like, well, bash. Here
> >> are the symptoms:
> >>
> >> Type "set" to see all the environmental variables.
> >>   1. Regular user: a bash script scrolls ???
> >>   2. Root: the environmental variables are printed to screen.
> >>   3. Regular user after typing "sh" to get the old Borne Shell, normal
> >> results a number 2, above.
> >>
> >> I suspect there is a mis-configured something somewhere. Can anyone help?
> > 
> > SUSE's always done that (well, at least as long as I've used it.)  I 
> > just tried on a Debian box and their script is even longer.  But if you 
> > do a:
> > 	set | more
> > you'll see the normal variables at the beginning.  Not sure what the 
> > script is doing but it's 'normal', i.e., part of the stock install I 
> > believe...
> > 
> > ...Kevin
> 
> Wow! Yet another reason not to use SuSE! =:-)}}} Be that as it may, here
> is the background to my query:
> 
< snip interesting history >
     I’m not sure I fully understand.  I use SuSE and have no
     problem setting environment variables.  "Set" isn’t the
     command to use, however, and indeed, dumps way to much info
     to the screen when invoked.  But var=value certainly works
     (or export var=value).
     I have on occasion had scripts that somehow dump the entire
     environment as a by product of some action.  Very annoying,
     and a by product of using "set" incorrectly, I seem to
     remember.
Rgds,
-- Mike Bishop Willow, Alaska --------- To unsubscribe, send email to <aklug-request@aklug.org> with 'unsubscribe' in the message body.Received on Wed May 16 10:12:22 2007
This archive was generated by hypermail 2.1.8 : Wed May 16 2007 - 10:12:23 AKDT