Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!samsung!ernie.viewlogic.com!madmax!kenc
From: kenc@madmax.Viewlogic.COM (Kenstir)
Newsgroups: comp.unix.shell
Subject: Re: What should be in .cshrc vs .login
Message-ID: <1990Oct29.113434@madmax.Viewlogic.COM>
Date: 29 Oct 90 16:34:34 GMT
References: <1294@tardis.Tymnet.COM> <FPB.90Oct21120952@ittc.ittc.wec.com> <1300@tardis.Tymnet.COM> <1990Oct23.011502.21167@mp.cs.niu.edu> <1990Oct23.045911.472@athena.mit.edu>
Sender: news@viewlogic.com (News Administrator)
Reply-To: kenc@madmax.Viewlogic.COM (Kenstir)
Organization: Viewlogic Systems, Inc., Marlboro, MA
Lines: 36

In article <1990Oct23.045911.472@athena.mit.edu>, jik@athena.mit.edu
(Jonathan I. Kamens) writes:
|>   Our users log into X displays the vast majority of the time, and
our X login
|> setup doesn't even *look at* .login, so putting the initialization
stuff there
|> isn't an option.  Putting it in .cshrc, however, makes it work both
for X
|> logins and for dialup logins (which do use .login, obviously :-).

It certainly is an option.  Check out this in the .xsession file:
	#!/bin/csh
	#         ^^^ don't use -f option
	#
	#	.xsession	xdm display manager startup file
	#
	# $Id: .xsession,v 1.3 90/03/27 11:10:14 kenc Exp $

	# want to read .cshrc AND .login when starting a session
	source .login
	
	sh ~/.xinitrc

This is bordering on the religious, but there is a place for the .login
file.  For instance:
	if (-e /usr/games/fortune) /usr/games/fortune

doesn't want to be in the .cshrc, and resetting environment variables
in the .cshrc which may have been purposefully altered is not a great
idea.

--
Kenneth H. Cox
Viewlogic Systems, Inc.
kenstir@viewlogic.com
...!harvard!cg-atla!viewlog!kenstir