Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!mips!news.cs.indiana.edu!news.nd.edu!mentor.cc.purdue.edu!mace.cc.purdue.edu!abe
From: abe@mace.cc.purdue.edu (Vic Abell)
Newsgroups: comp.sys.next
Subject: Re: loginwindow LoginHook
Keywords: LoginHook loginwindow dwrite
Message-ID: <7431@mace.cc.purdue.edu>
Date: 10 May 91 13:44:58 GMT
References: <14824@ccncsu.ColoState.EDU>
Organization: Purdue University Computing Center
Lines: 14

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.

I use loginwindow hooks to completely darken my screen when I log out
and rebrighten it when I log in.