Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!zaphod.mps.ohio-state.edu!know!ladcgw.ladc.bull.com!melb.bull.oz.au!sjg From: sjg@melb.bull.oz.au (Simon J Gerraty) Newsgroups: comp.unix.admin Subject: Re: Forcing actions at login Message-ID: <1991Jan22.023543.934@melb.bull.oz.au> Date: 22 Jan 91 02:35:43 GMT References: <6153@ecs.soton.ac.uk> <446@minya.UUCP> <1991Jan10.191546.268@am.sublink.org> <449@minya.UUCP> <1991Jan16.000012.26467@lokkur.dexter.mi.us> Organization: Bull HN Information Systems Australia. Lines: 27 In <1991Jan16.000012.26467@lokkur.dexter.mi.us> scs@lokkur.dexter.mi.us (Steve Simmons) writes: >Different sites have different needs. There's many a time I've >*desperately* needed to set something for *all* users *all* the time >(Hi Bill!). Without a global setup file the only solution is to modify I agree. Of course you don't have to slash your wrists if your vendor did not build global init file support into your c-shell. I just create global files /etc/csh.{login,cshrc} and source these in the default .login,.cshrc files that users are provided with. Eg. # .cshrc 1.1 # pick up the standard environment source /etc/csh.cshrc # place personal commands here Of course this approach does not _force_ the use of /etc/csh.cshrc since users can always remove the source line. In practice however they do not - after all, I only put useful things in the global files anyway :-) -- Simon J. Gerraty #include