mchinni@ARDEC.arpa (Michael J. Chinni, SMCAR-CCS-E) (09/25/86)
Geoff, All I can help with is a suggestion for item 1. [ 1. Modify CSH so that it checks for the existence of a system wide [ .cshrc and .login (obviously they could have different names) before [ reading the users .cshrc and .login. This would allow the system [ manager (me) to create a standard environment without having to write [ each user a .login and .cshrc and still allow the user to modify his [ or her environment if they choose. What I am now doing is to have each users rc file, first execute a system wide rc file. This lets me do as you mention, which is to create as standard environment, while still allowing users to change their environment if they so choose. I am doing this with the Bourne shell. Do to lack of working knowledge on C shell, I can't say for sure if this will work for it. Mike Chinni USA AMCCOM ARDEC
rgenter@LABS-B.BBN.COM (Rick Genter) (09/26/86)
I thought the Bourne shell already did this? I seem to recall that
the Bourne shell read a .profile from a well-known place (either /etc/.profile
or /usr/lib/.profile - I can't remember), then read the user's .profile.
Of course, this is from Venix 2.0, so probably it's all wrong :-).
--------
Rick Genter BBN Laboratories Inc.
(617) 497-3848 10 Moulton St. 6/512
rgenter@labs-b.bbn.COM (Internet new) Cambridge, MA 02238
rgenter@bbn-labs-b.ARPA (Internet old) linus!rgenter%BBN-LABS-B.ARPA (UUCP)rab@smu (10/01/86)
what i did was place this line at the beginning of everyone's .login: source /usr/local/.login the rule is that if you remove that line, then there are no guarantees. it works quite well for setting up a system-wide login 'image'. rick barrett smu!rab