Date: Sun, 16 Jan 2000 20:50:34 +1100 From: aunty <aunty@comcen.com.au> To: freebsd-questions@freebsd.org Subject: login class and bash clash? Message-ID: <20000116205034.C14280@comcen.com.au>
next in thread | raw e-mail | index | archive | help
On a -STABLE system I'm trying to set up a staff class with, among
other things, a different default path. (Easy to maintain, and not so
likely to be edited away by novice wheel members.)
After logging in, the environment seems to be that in /etc/profile
instead of the one set for the class. Everyone uses the bash shell.
The staff users' home directories contain neither .profile nor .bash*
When the user's shell is set to csh they do get the environment that is
set up for the class, as intended. But they must have bash.
This line from login(1) might be hinting at an explanation for my
puzzle, but if so I'd need it filled out a bit:
The standard shells, csh(1) and sh(1), do not fork before
executing the login utility.
I suppose it'd be possible to maintain a .bash_profile in their home
directories to ovveride /etc/profile, but using login.class is neater.
Am I reading the situation correctly? Maybe I should remove /etc/profile
(is it necessary?) and use the other class definitions to replace some
of what /etc/profile sets up. Or read something. Or something.
Suggestions?
--
Regards,
-*Sue*-
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000116205034.C14280>