Btw, at the point where there's quite a few udt.exe's that exist at o/s but are already released from unidata (as I see through listuser, anyway)...those udt.exe's are consuming zero cpu.
-----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Symeon Breen Sent: Thursday, June 24, 2010 8:47 AM To: 'U2 Users List' Subject: Re: [U2] UniData 'QUIT' The QUIT command just exits the udt process. Of course udt itself will do some tidying up at that point - releasing locks etc, then the OS will do some tidying up with regard memory space etc. I have seen quit take a long time when the udt process has got hold of a lot of ram, so check out the process and see how much ram/cpu it is using, also check the lock table to see if it is having to release a lot of locks. -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Amy Cook Sent: 24 June 2010 16:31 To: U2 Users List Subject: [U2] UniData 'QUIT' Can anyone tell me exactly what the QUIT verb does? Does it issue a stopudt? Does it also do a 'kill' or windows equivalent of o/s process id? I'm asking because we have a situation where: 1) When I issue the quit command (using demo account for testing purposes), it takes a minimum of 3 seconds now to logout. It's never been anything but immediate up until a week and a half ago. 2) if we have numerous phantoms running, they seems to be hitting this same delay in logging out, and within a couple minutes, that 3 seconds grows to 20 seconds...up to 20 minutes or more...waiting on the other sessions to logout. 3) At the point where it's taking a long time to logout...the database has already released the session. Listuser no longer shows that phantom session. But the Task Manager shows it's still active to the O/S. At first we were focused on the phantoms, but these are the only sessions that really log in, do something, then immediately log out...creating the perfect environment for building up the 'queue' for logout. Since we've been through a ton of troubleshooting already, I'm trying to start over at ground zero and figure out why a simple unidata session to the demo account doesn't immediately log out when I issue the quit command. Any ideas?? TIA, Amy _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
