LogoutHook question

Thread View: comp.sys.next.sysadmin

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by David Lemson Sat, 22 Aug 1992 22:39

#1039

Author: David Lemson
Date: Sat, 22 Aug 1992 22:39

16 lines
1241 bytes

I know that if a LoginHook exits with a 0, the login proceeds
normally.  If it exits with a 1, then the login kicks back out to
the prompt.
I want to do the same sort of thing with LogoutHook.  If I exit the
LogoutHook program with a 1, I want it to dump the user back into
the workspace, not letting them log out.  I tried it, and it doesn't
work.  Anyone have any idea how I might do this? (something
undocumented?)
BTW, in case you're wondering why I don't want to let the user log
out, it's because I want to force them to go back and reduce their
disk usage before they log out. 
-- 
David Lemson                                                 (217) 244-1205
University of Illinois NeXT Campus Consultant  / CCSO NeXT Lab System Admin
Internet : lemson@uiuc.edu                 UUCP :...!uiucuxc!uiucux1!lemson 
NeXTMail accepted                                   BITNET : LEMSON@UIUCVMD

Re: LogoutHook question

#671

Author: bruce
Date: Tue, 25 Aug 1992 14:48

38 lines
2505 bytes

lemson@ux1.cso.uiuc.edu (David Lemson) writes:
: I know that if a LoginHook exits with a 0, the login proceeds
: normally.  If it exits with a 1, then the login kicks back out to
: the prompt.
: I want to do the same sort of thing with LogoutHook.  If I exit the
: LogoutHook program with a 1, I want it to dump the user back into
: the workspace, not letting them log out.  I tried it, and it doesn't
: work.  Anyone have any idea how I might do this? (something
: undocumented?)
: BTW, in case you're wondering why I don't want to let the user log
: out, it's because I want to force them to go back and reduce their
: disk usage before they log out. 
: -- 

  Sounds like a good usage for the logout hook, however perhaps not the
right action.  Perhaps applying a compression utility to their entire
home directory tree, leaving only enough actually IN the directory for
the next login.  It would likely be necessary to arc-off also their
normal .cshrc and .profile, replacing it with new-user defaults, ESPECIALLY
if they must utilize a terminal shell or even remote login shell to
restore their home directory.    Not allowing a logout, especially in
a busy campus environment is apt to merely leave a lot of damage in its
wake, as users DON'T logout, and the next user comes along and merely
grabs a fan and stuffs it into the recycler, pops the empty option, in
order to gain access to the hardware for their own use.  Automated
E-Mail is classic on the NeXT, and could function from the same logout
hook, explaining just what has happened to their directory(s), and
how to go about fixing the problem.

  It would certainly be nice to place a ``dock-able'' test-only which
would TEST to see if they're in trouble if they logout...

Bruce
-- 
Bruce Gingery          bruce@TotSysSoft.com        (Total System Software)
InterNet:  Bruce.Gingery@p1.f5.n310.z1.fidonet.org (  Cheyenne, Wyoming )
       or  bruce@brucext.TotSysSoft.com
NeXT-Mail: bruce@tssnext.rmNUG.org  < -or- > bruce@TotSysSoft.com

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads