🚀 go-pugleaf

Hi there,

I don't know if "bug" is the right word, but I think that
the "bash-wizards" are most likely to be in this group and
i found now group like "gnu.bash.discuss".

on our Systems, we'd like to have systemwide aliases (like
"alias passwd=yppasswd"), because there is a need for some of
our aliases (like "soft='source /usr/local/scripts/soft'") to 
be not just command, but an alias or function.

We could define them in /etc/profile for a login shell, but
unfortunately most of our Sun-Openwin Shells are interactive,
but not login shells (our profile is quite long, so starting
bash -login on all new xterms would be time consuming).

We could set "ENV" to something like /etc/bashrc, but this
is only obeyed by noninteractive shells. 

We could recommend our users to have the aliases in their
.bashrc, but accidently some of our users (>300) delete
their files and then they say "why can't I set the passwd" or
"whereis that soft command gone".

Currently we use functions, which we declare in "/etc/profile",
and export them. But this breaks our "env"-command. I wonder if
this bash-thing has nothing like a systemwide "bashrc" for 
interaction, nologin shells.

Thanks in advance

Reiner Huober
---------------
email: reiner.huober@rz.uni-ulm.de