[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

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

1119.0. "PCM 1.6, DUNIX - garbage output on monitor window" by 29067::B_GRUBBS () Fri Dec 08 1995 15:21

    PCM 1.6 on DUNIX.
    
    My customer uses telnet connections to a decserver with an ALPHA
    console plugged into the serial port.
    
    He can connect and do most things but he has two problems with the
    'monitor' window.
    
    1) if they reboot the system that they are monitoring, they get a lot
       of garbage in the monitor window, CTRL G's and such and it's almost
       impossible to reuse.  The have to close it down and start another
       one.
    
    2) ctrl P doesn't seem to work to halt the system they are connected
    to.
    
    
    The strange part is if they telnet directly to the terminal server and
    the telnet listner number they can read all the consoel reboot info
    without any trouble, and ctrl P is able to halt the system.
    
    Seems like a problem with the decterm that gets spawned when you
    monitor a remote console.  Anyone seen something like this before?
    
    thanks,
    
    --Bert Grubbs
      Colorado CSC
T.RTitleUserPersonal
Name
DateLines
1119.1control-P sending break?51666::KORKKOVeli K�rkk� @FNO, 879-5512, GPS FNOSun Dec 10 1995 07:518
        By default control P will send break signal (asking for
        confirmation first). You will have change the default break
        setting to something else in order to be able to send control-P,
        i.e.
        
            Console command:	set break ctrl-h
        
        _veli
1119.2??29067::B_GRUBBSSun Dec 10 1995 18:2611
    
    thanks for the resonse, but I'm not sure what you mean.
    
    If they telnet directly to the terminal server telnet listener
    that serves that physical port ctrl P works fine.  It just can't
    seem to get through from the 'monitor' window that PCM brings up.
    
    I don't think it's a console setting that needs to be changed....
    
    --bert
    
1119.351666::KORKKOVeli K�rkk� @FNO, 879-5512, GPS FNOMon Dec 11 1995 10:4414
If you telnet directly, then pressing control-P will indeed send control-P to 
Alpha console. Therefore it works.

If you $CONSOLE CONNECT ALPAHA, then by default control-P will cause PCM
to send break signal, not control-P to the monitored system. And therefore
it will not work.

You will have to instruct PCM to send control-P when you press control-P. And
this takes place when you redefine break character to be e.q. control-H 
(instead of control-P!).

Does this glarify the situation?

_veli
1119.4got it.29067::B_GRUBBSMon Dec 11 1995 13:284
    
    very clearly....sorry for the misunderstanding!  8^}
    
    --Bert
1119.5one outstanding.29067::B_GRUBBSMon Dec 11 1995 13:345
    
    Still one question left.  On the garbage they see in the monitor window
    when the 'monitored' system is rebooted? 
    
    --Bert
1119.629067::BUTTERWORTHGun Control is a steady hand.Wed Dec 13 1995 16:079
    bert,
      Monitor does not interpret escape sequences, so all non-printing
    characters appear as a reverse question mark. If they use the CONNECT
    interface, all esc sequences and non-printing characters are passed to
    the users terminal, i.e., the bell witll ring, esc sequences will be
    executed by the terminal etc - it will look "normal".
    
    Regards,
       Dan
1119.7no go29067::B_GRUBBSThu Dec 14 1995 16:109
    
    
    They see the garbage characters under monitor and connect.  It doesn't
    have to be a reboot, they just connect to what would be an active
    console.
    
    I'm getting the terminal server port characteristics faxed to me.
    
    --Bert