Date:         Mon, 25 Feb 2002 17:07:41 -0000
Reply-To:     Nigel.Pain@SCOTLAND.GSI.GOV.UK
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Nigel Pain <Nigel.Pain@SCOTLAND.GSI.GOV.UK>
Subject:      Killing UNIX Processes
Content-Type: multipart/alternative;

*****************************************************************************
This email and any files transmitted with it are intended solely
 for the use of the individual or entity to whom they are addressed.
*****************************************************************************

Not strictly SAS, but SAS is at the root of the problem:

We are running 6.12 (soon to upgrade to 8.2) on Solaris and NT Workstation,
with users either working through SAS/Connect or directly on the server with
X-Server S/W (Exceed). On a regular basis, users close their SAS sessions
but somehow leave the UNIX process running (I suspect in many cases this is
due to omitting to signoff a remote session, no matter how often we implore
them to do so).

It's easy enough to go in periodically to check for redundant processes and
then kill them, but I'm sure there must be a way to identify these processes
in some kind of shell script. Unfortunately my shell script skills are not
up to it. Are there any clever, kind, generous ('scuse me while I get my
trowel to lay it on thicker!) UNIX gurus out there who could suggest
something so I can automate the procedure? At the moment I identify
processes with the ps command piped through a series of greps to narrow it
down to SAS sessions and then use the kill command.

Thanks

***************************************************
Nigel Pain
Scottish Executive Development Department
Business Support Unit
Victoria Quay
EDINBURGH
EH6 6QQ
UK
Tel +44 131 244 7237
Fax +44 7092 014235

Mailto:nigel.pain@scotland.gsi.gov.uk
Website: http:\\www.scotland.gov.uk


[text/html]