Re: Locking user accounts

Killing an Informix user process will NOT kill or shutdown the Informix engine. That used to happen in OL5 and earlier versions because each client had its own engine process which was a child of the client and which would die when its parent was killed without cleaning up. When this happened the engine's supervisor task (tbinit) would shut itself and all remaining clients down to prevent corruption. However, IDS 7/8/9 is more robust and the engine's processes are independent of the clients so it detects the forced disconnect and cleans up the connection and session including rolling back any open transactions. Alternatively, and better anyway, you can use onmode -z <sid> to kill the session (onstat -g ses to see the session belonging to a pid) in the database first then kill the user's task since it may not itself detect the disconnect from the engine until the user requests data again. Either way this is safe. Art S. Kagel ----- Original Message ----- From: David Taylor <dtaylor@rpionline.com> At: 3/ 4 11:31 > I have a little problem here. I need to be able to lock user accounts if they > are logged in over night. I don't have anyone that logins in from offsite so I > don't have a worry there. I am running AIX 4.3 on a RS6000 with Informix 7.3.1 > It would be easy to just find all of the user's processes and kill those and > then disable their login, so that they would have to come to me to get it back, > but I can't do this because I've been told that if they are running an informix > process that killing that process will kill informix itself and shut that down. > I've figured out how to use 'chuser' to lock the account, but this does not lock > the user's windows. All user's use a windows application to connect to the > RS6000. > > Thanks in advance, > > ___________________________ > David Taylor > Database Specialist > Rapidparts Inc. > 616.647.3108 > dtaylor@rpionline.com