We quite often get UO processes hanging on out udt box, deleteuser or kill
-9 is what i usually do and they always hang around in listuser for atleast
5 mins - it is a real pain!

 

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Bill 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 there's
approximately a 30 second pause between logging off the user/pid and the
user disappearing from the "LISTUSER" command.  I didn't realize doing
this through UniAdmin could potentially corrupt files or interrupt writes!

I'm not sure where I got the "udtkill.exe" information from but I
substituted "deleteuser" for that executable.  Only He knows if this
will work properly!

Thanks again,

Bill

------------------------------------------------------------------------
Kevin King said the following on 12/29/2010 2:18 PM:
> 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
> that's the command that I understand is supposed to be used in place of
> UniAdmin to force a user down.
>
>
> ------------------------------------------------------------------------
> Subject:      [UD] Killing a UO connection
> Date:         Tue, 28 Dec 2010 13:48:48 -0800
> From:         Bill Haskett <[email protected]>
> To:   U2 Mail List <[email protected]>
>
>
> 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 code in use in BASIC:
>
> IF OptionNos NE "FORCE" THEN
>    PerformVerb = "stopudt -f "
> END ELSE
>    PerformVerb = "udtkill.exe "
> END
>
> Supposedly this was supposed to do the trick, but it doesn't. Does
> anyone know what is used by UniAdmin to clear the connection so I can
> program it into BASIC?
>
> Thanks,
>
> Bill Haskett
> Advantos Systems, Inc.
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users 

  _____  

No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1191 / Virus Database: 1435/3347 - Release Date: 12/29/10

_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to