jeffjordan
MIS
Whenever an end-user logs on to a Windows Server it creates a session id. As it is redirected to the Unix Host server, Unix creates a PID. If the session on the Windows times out or hangs, the windows session is "blown away"; but the PID on the Unix remains.
The kicker is that access to the Unix server is done using a common logon, so the PIDs are all the same.
Is there a way for the Unix server to kill a process when the Windows session id dies?
The kicker is that access to the Unix server is done using a common logon, so the PIDs are all the same.
Is there a way for the Unix server to kill a process when the Windows session id dies?