Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!ncar!gatech!usenet.ins.cwru.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.172040.9333@agate.berkeley.edu>
Date: 10 May 91 17:20:40 GMT
References: <7431@mace.cc.purdue.edu> <1991May10.143527.27890@agate.berkeley.edu> <7432@mace.cc.purdue.edu>
Sender: root@agate.berkeley.edu (Charlie Root)
Organization: /etc/organization
Lines: 28

In article <7432@mace.cc.purdue.edu> abe@mace.cc.purdue.edu (Vic Abell) writes:
>In article <1991May10.143527.27890@agate.berkeley.edu> izumi@mindseye.berkeley.edu (Izumi Ohzawa) writes:
>>By the way, LoginHook is broken on 2.0.  It is fixed in 2.1.
>
>Please be more explicit.  I am currently using a script via LoginHook
>under 2.0 and it works correctly for me.  Exactly what is broken?

Hmm... If it works for you, that's great.
The problem I had was that specifying LoginHook broke something
in lowinwindow or Windowserver so that the next user who tries
to login get kicked out of login process and put immediately
back to loginwindow.
I had this problem using MOTD as LoginHook program.

This situation required restarting windowserver by typing
"exit" every time you login.

As I said, this is now fixed in 2.1.

NeXT's announcement for Software Release 2.1 also mentions
of fix to LoginHook, although it doesn't say specifically
what the broken behavior was.


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