Re: orphan sessions in ODS 7.2
}>From ilist@rmy.emory.edu Sat Jun 14 02:14:47 1997
}>Received: from rmy.rmy.emory.edu by hobbes.dbintellect.com via ESMTP (950413.SGI.8.6.12/930416.SGI.AUTO)
}> for <settler@dbintellect.com> id CAA02641; Sat, 14 Jun 1997 02:14:35 -0600
}>Received: (from ilist@localhost) by rmy.rmy.emory.edu (8.7.1/8.7.1) id DAA16608 for informix-list-out; Sat, 14 Jun 1997 03:00:01 -0400 (EDT)
}>From: Andy Chang <ktchang@earthlink.net>
}>Message-Id: <33A22E0D.639A@earthlink.net>
}>Subject: orphan sessions in ODS 7.2
}>Date: Fri, 13 Jun 1997 23:37:17 -0600
}>Reply-To: ktchang@earthlink.net
}>Organization: EarthLink Network, Inc.
}>Sender: informix-list-owner@rmy.emory.edu
}>To: informix-list@rmy.emory.edu
}>X-Informix-List-Id: <news.39161>
}>
}>Greetings...
}>Does anybody out there know a way to identify orphan sessions in a 7.2
}>engine?
}>
}>Andy
}>
Use 'onstat -g ses' to get the UNIX process Id, fourth column labeled pid.
Use the pid to check for orphan - 'ps -ef|grep pid', where pid is the number
displayed in the onstat command. If the PPID (Parent Process ID) value in
the ps display is 1 and the TIME value is increasing rapidly, then it's
probably an orphan. Note that a 'nohup dbaccess dbname <sqlfile.sql &' will
also appear as an orphan, so your kill script should try to discern background
dbaccess sessions from true orphans.
-------------------------------------------------------------------
Jeff Craig | dbINTELLECT Technologies, Inc.
Senior Consultant | Golden, CO
| (303) 275-6954 ext. 8008
| email: settler@dbintellect.com
| fax: (303) 275-2134
-------------------------------------------------------------------