| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 78.1 | No, haven't seen it before | ALPHAZ::HARNEY | John A Harney | Thu Jan 23 1997 08:34 | 30 |
| 78.2 | I've asked the customer... | MUNICH::WWERNER | When in doubt, do as the INTs do | Thu Jan 23 1997 10:40 | 20 |
| 78.3 | | ALPHAZ::HARNEY | John A Harney | Thu Jan 23 1997 13:10 | 12 |
| 78.4 | | EPS::VANDENHEUVEL | Hein | Thu Jan 23 1997 14:59 | 16 |
| 78.5 | from SHOW SYSTEM | MUNICH::WWERNER | When in doubt, do as the INTs do | Fri Jan 24 1997 06:50 | 11 |
| Hmmm, not thousands of i/os from security_server...
Pid Process Name State Pri I/O CPU Page flts Ph.Mem
(start of hang)
27C000D5 SECURITY_SERVER HIB 8 991 0 00:02:02.47 19026 1184
(15 sec. later)
27C000D5 SECURITY_SERVER HIB 8 1043 0 00:02:09.06 19026 1184
(after error message)
27C000D5 SECURITY_SERVER HIB 8 1091 0 00:02:15.09 19056 1214
Wolfgang
|
| 78.6 | | ALPHAZ::HARNEY | John A Harney | Fri Jan 24 1997 09:57 | 16 |
|
The NET$PROXY.DAT file seems fine. It is the largest proxy file
I've ever seen.
My system (Alpha 3000 Model 400) does "UAF> sh/proxy *::PFRSL"
in about 6 seconds and yields 4 records.
My only guess is that their satellite traffic is so heavy the
remote security server can't get to the NET$PROXY.DAT file in
a timely manner.
Resolution likely means changing a timeout value in SECURESHRP.EXE
or making it user-adjustable.
Please file a problem report. Don't expect a quick fix, though.
\john
|