Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!samsung!uunet!mcsun!ukc!icdoc!sot-ecs!tjc
From: tjc@ecs.soton.ac.uk (Tim Chown)
Newsgroups: comp.unix.admin
Subject: Re: Forcing actions at login
Message-ID: <6360@ecs.soton.ac.uk>
Date: 20 Jan 91 20:51:36 GMT
References: <6153@ecs.soton.ac.uk> <446@minya.UUCP> <1991Jan10.191546.268@am.sublink.org> <1991Jan13.231048.25341@NCoast.ORG> <2687@bimacs.BITNET> <3220@litchi.bbn.com>
Organization: University of Southampton, UK
Lines: 17

In <3220@litchi.bbn.com> rsalz@bbn.com (Rich Salz) writes:

>Cshell
>    cmp -s /etc/motd $HOME/.hushlogin
>    if ( $status ) tee $HOME/.hushlogin </etc/motd

I am very grateful for all the replies to my original question about
forcing actions.  We now have users "controlled" as desired on login
(setting paths, MANPATHs, global messages and some process renicing),
but I would like to ask what can be done for connections where a
login per se is not run.  The particular example I'm interested in
is an X-session under SunOS4.  In this context it appears that only
the user's .cshrc is inspected; Sun seem to have no global .cshrc
or .profile scheme.   Is there anything I can do here?

Cheers,
	Tim.