Idle Users

[Fairlight]

On Thu, Jun 17, 2004 at 03:17:34PM -0700, after drawing runes in goat's blood,
Bob Rasmussen cast forth these immortal, mystical words:
> 
> Handling the WM event is exactly what I am doing. And closing the telnet
> or SSH session gracefully is ALSO what I am doing. The problem comes when
> the host's application does not shut down in response. I *think* this is
> due to the "hangup" signal (SIGHUP), which is generated by the telnetd or
> sshd, is trapped or ignored at some level. Then what? Because of this
> possibility, I give users and administrators the option of disabling quit.

Ahhhhhh.  Okay, that wasn't clear from your first post.  Sorry, Bob.  I
assumed you were doing one or the other, not that there was this particular
chain of events--which your solution actually makes sense for.  Out of
curiosity, how does it handle Alt-F4?  Is that the same as 'X', another
event, or worse--an untrappable event?  Although, I seem to recall that you
can take over the binding for that, can't you?

> I have brainstormed on how I might improve on this situation. Both telnet
> and ssh allow the sending of several arbitrary signals to the server.
> Maybe I could offer an option where, on WM_QUIT, Anzio would send a hangup
> signal to the server. If the server trapped out the hangup, everything
> would stay running. If the hangup was handled normally, the server would
> close its end of the connection, and Anzio would exit gracefully.
> 
> Reactions?

At the risk of sounding ignorant, I'll bite.  Why would telnetd or sshd
themselves ever trap a HUP and not pass it along to the child process
group?

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html