| Title: | POLYCENTER Console Manager |
| Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
| Moderator: | CSC32::BUTTERWORTH |
| Created: | Thu Aug 06 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1541 |
| Total number of notes: | 6564 |
One thing I noticed with console that I didn't notice with VCS is that if one person that connected to a console line types CTRL/S then the entire console system hangs and noone can type anything on all the other console lines. (acts like everyone types CTRL/S). VCS use to have this problem abut 3 years ago and resolved it then. Don'tr ask me how.... Is there a way around this.. Users are both C3 and set host terminal lines.... Thanks Bill
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 971.1 | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Tue Sep 12 1995 12:44 | 6 | |
Bill,
This is the first I've heard of this problem. I'll put it on our
list for the support team to verify. Thanks for the update.
Dave
| |||||
| 971.2 | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Wed Sep 13 1995 12:27 | 13 | |
I just tested this and I can't make it break. I connected to two nodes
ctrl-s'd one of them and then entered commands into the other one.
Are you running V1.6 of PCM? Apologies if I missed that.
>VCS used
Not to start an argument, but I've been doing most fo the VCS engr.
support for the last 3 years and VCS never had a problem like that.
It's internal interporcess communication mechanisms precluded this kind
of thing happening. Now we had a couple locking problems that could
effect our ability to connect but they were not tied to ctrl-s.
| |||||
| 971.3 | My mistake.... not a problem | 30188::CLEMENCE | Mon Sep 18 1995 11:31 | 35 | |
> I just tested this and I can't make it break. I connected to two nodes
> ctrl-s'd one of them and then entered commands into the other one.
> Are you running V1.6 of PCM? Apologies if I missed that.
I re-tried a similar senerio on our system here and now it works..
I'm still using V1.5, I know it 'acted' like all the systems hung, but in
thinking about it the other systems were running 'DEC unix' and the ctrl/s
was on a debug massease section of code trunning on them. Since those systems
are interconnected together, via other cluster software, my guess is that
they all hung when the first debug message couldn't complete..
I.E. It was falsely indicating a Polycenter problem. I should have
re-teseted again under a more controled condition before reporting
it here... My apologies....
> >VCS used
>
>
> Not to start an argument, but I've been doing most fo the VCS engr.
> support for the last 3 years and VCS never had a problem like that.
> It's internal interporcess communication mechanisms precluded this kind
> of thing happening. Now we had a couple locking problems that could
> effect our ability to connect but they were not tied to ctrl-s.
Not to start an argument either, prior to 1993 we use to have to look for
terminal lines in a RSTWAIT state. When one was it would hang VCS. This
went away sometime after 1993, I never got back to the person who supported it
to understand how this problem was resolved or what caused it. I was,
incorrectly, assumining it was a VCS problem; whereas it could have been a
VMS software bug.
My apologies..
Bill
| |||||
| 971.4 | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Mon Sep 18 1995 13:52 | 7 | |
Bill,
Thanks for the update and saving us time by not having to look into
this problem.
Dave
| |||||