Great info! Thanks.
Perry Taylor
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Herve
Balestrieri
Sent: Wednesday, November 23, 2005 10:27 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] PORT.STATUS From Unix
Starting at release 10.1.15
Starting at release 10.1.15, the problem with "uvlictool" hanging UniVerse
when issuing to a "pipe" will be fixed (ECase 7640*USA).
When hung on the "Port status" semaphore, the "State" column would show = 1
as follow :
Port status State Netnode Owner Collisions Retries
Semaphore #
Yes, Herve, that helps!
Thanks. That one's a keeper.
Can you answer my question about how to read the port.status section of
the smat -s output?
(That's what you get for being helpful.)
cds
> From: Herve Balestrieri
>
> When there is no UNIX session logged into UniVerse, you can
> setup an in
> From: Perry Taylor
>
> Hrm. Good info.
>
> How would one go about finding a "hung" port.status semaphore?
Red Herring:
---
One would *expect* smat -s to indicate it, but no.
Toward the bottom of a smat -s it says:
Port status State Netnode Owner Collisions Retries
Sem
EMAIL PROTECTED] Behalf Of Perry Taylor
Sent: Wednesday, November 23, 2005 9:27 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] PORT.STATUS From Unix
Hrm. Good info.
How would one go about finding a "hung" port.status semphore?
-Original Message-
From: [EMAIL PROTECTED]
Subject
RE: [U2] [UV] PORT.STATUS From Unix
23/11/2005 15:27
Hrm. Good info.
How would one go about finding a "hung" port.status semphore?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stevenson,
Charles
Sent: Tuesday, November 22, 2005 9:46 PM
To: u2-users@listserver.u2ug.org
Subject: RE
> From: Perry Taylor
>
> What would be the indications/complications of this happening?
No one else can run port.status until the port.status semaphore is
cleared.
A more dangerous similar example is locking the login semaphore.
Logins to UV shell are singlethreaded via this semaphore.
uvlictoo
What would be the indications/complications of this happening?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stevenson,
Charles
Sent: Tuesday, November 22, 2005 3:12 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] PORT.STATUS From Unix
yeahbut, be careful not to leave the semaphore set via miss-typing:
For examplem if you did:
$port.status | asdfasf (where asdfasf is garbage.)
You'll need superuser (or uv administrator?) to do
>UNLOCK PSTATLOCK SEMAPHORE
from TCL.
> From: Rod Hills
>
> If you display the VOC entry fo
Thank you, Rod! That worked just right!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rod Hills
Sent: Tuesday, November 22, 2005 12:50 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] PORT.STATUS From Unix
If you display the VOC entry for
If you display the VOC entry for PORT.STATUS you'll see it calls
"list_readu". Just "cd /u1/uv/bin" then "ln list_readu port.status".
Then you can run port.status at the unix level.
HTH
Rod Hills
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Perry Tay
12 matches
Mail list logo
