Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!dali.cs.montana.edu!milton!wiml
From: wiml@milton.u.washington.edu (William Lewis)
Newsgroups: comp.sys.next
Subject: Re: .login file
Keywords: .login, NeXT, /dev/console, scripts
Message-ID: <9215@milton.u.washington.edu>
Date: 15 Oct 90 03:42:04 GMT
References: <1990Oct13.023904.6927@Neon.Stanford.EDU>
Organization: University of Washington, Seattle
Lines: 20


   .cshrc and .login are only executed when you start a shell, for instance
by launching Terminal, Shell or Stuart. (Actually I don't know if 
.login is executed in these cases, maybe only .cshrc is). I think the
preferred way to have arbitrary things happen when you log in is
to use the defaults database:

dwrite loginwindow LoginHook /some/program/name
dwrite loginwindow LogoutHook /some/other/program

  "loginwindow" is the program that handles the login window (appropriately
enough); it's the NextStep equivalent of /bin/login. On the other
hand, I think these are global defaults (everyone who logs in on the
console has these programs run). The hook would have to do whatever
differentiation is neccessary.
-- 
 wiml@milton.acs.washington.edu       Seattle, Washington   
     (William Lewis)   |  47 41' 15" N   122 42' 58" W  
"These 2 cents will cost the net thousands upon thousands of 
dollars to send everywhere. Are you sure you want to do this?"