Haskett
Sent: 29 December 2010 23:15
To: U2 Users List
Subject: Re: [U2] [UD] Killing a UO connection
Kevin:
Thanks. I don't shutdown UniData (the -f is unnecessary (used only
for stopud) and stopudt pid [pidM... pidN] will stop one or more
unidata processes). When I use UniAdmin to Logoff a user
Two things come immediately to mind... First, to force people off you're
shutting down Unidata altogether? Seems a bit harsh, that's all I'm
saying. Second, what about deleteuser instead of udtkill? I'm not a fan of
deleteuser (because even the documentation says it can cause corruption) but
Kevin:
Thanks. I don't shutdown UniData (the -f is unnecessary (used only
for stopud) and stopudt pid [pidM... pidN] will stop one or more
unidata processes). When I use UniAdmin to Logoff a user there's
approximately a 30 second pause between logging off the user/pid and the
user
I'm running UO for most of the connectivity to our application.
Occasionally, a UO connection from DesignBais gets locked and I can only
get rid of it via UniAdmin. I have a BASIC program I run to delete
these connections and it mostly works. However, occasionally it
doesn't. Here's the
