Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stanford.edu!agate!mindseye!izumi
From: izumi@mindseye.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.next
Subject: Re: loginwindow LoginHook
Keywords: LoginHook loginwindow dwrite
Message-ID: <1991May10.143527.27890@agate.berkeley.edu>
Date: 10 May 91 14:35:27 GMT
References: <14824@ccncsu.ColoState.EDU> <7431@mace.cc.purdue.edu>
Sender: root@agate.berkeley.edu (Charlie Root)
Organization: /etc/organization
Lines: 22

In article <7431@mace.cc.purdue.edu> abe@mace.cc.purdue.edu (Vic Abell) writes:
>In article <14824@ccncsu.ColoState.EDU> kelley@kiwi (Kelley Wittmeyer) writes:
>>has anyone ever tried to run a script via
>>% dwrite loginwindow LoginHook scriptfile
>
>Yes, scripts can be run via both the loginwindow LoginHook and the
>LogoutHook.  What is slightly confusing is that the hook paths must
>be written to root's defaults file and loginwindow must be restarted
>after the defaults are updated.  You can do that by rebooting.  It
>has also been reported that logging in as "console" and then logging
>out will also cause loginwindow to see the new hooks, but I haven't
>verified that.

Or you can type "exit" to username, and no password.

By the way, LoginHook is broken on 2.0.  It is fixed in 2.1.


Izumi Ohzawa             [ $@Bg_78^=;(J ]
USMail: University of California, 360 Minor Hall, Berkeley, CA 94720
Telephone: (415) 642-6440             Fax:  (415) 642-3323
Internet: izumi@violet.berkeley.edu   NeXTmail: izumi@pinoko.berkeley.edu