[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

593.0. "Pseudo device and generic" by CSC32::PITT () Wed Feb 01 1995 20:44

    
    
    ok...help me out here. 
    
    Customer has PCM installed on an OSF node. 
    Their immediate goal (until they buy a terminal server) is to just
    monitor their own system.
    
    TO do this, they put in "pseudo terminal" for transport type, and
    for device, they put in "generic".  They put in nothing for server name
    and nothing for port name. .
    
    This seems to have gone well, but when they click on the icon for this
    system, they get the "clock" and nothing ever comes back.
    
    I had them try to look at the log files (we looked at
    console_manager.log) and saw "connection to <system> lost. IO error".
    
    THe PCM manual I have only lists direct, telnet, and lat as transport
    types. (I don't have the most recent manual). 
    
    Is this a correct configuration? Any ideas why this doesn't work
    (assuming it's even supposed to).?
    
    thanks.
    
    Cathy

T.R	Title	User	Personal Name	Date	Lines
593.1	Command needed	ZENDIA::DBIGELOW	Innovate, Integrate, Evaporate	`Wed Feb 01 1995 21:47`	18
	Cathy, The pseudo terminal is designed to run an application and most likely, they didn't enter a command when they configured the system. Have them go back into the editor and enter a command to run in the pseudo terminal. If they want to monitor their own system, they could enter the following command: tail -f /var/adm/messages This will constantly monitor the tail end of the messages log file for the system. Don't forget to remind your cusotmer that they will have to issue a reconfigure command after they've made the changes. Hope this helps, Dave
593.2		CSC32::PITT		`Wed Feb 01 1995 21:52`	11
	by a "command to run in the pseudo terminal" do you mean like an editor? The 1.0 ultrix manual says that a valid "command" would be vi... what exactly are they going to get by doing this? Does the new doc talk about this "pseudo terminal" and "generic" setup?? thanks LOTS!
593.3		ZENDIA::DBIGELOW	Innovate, Integrate, Evaporate	`Wed Feb 01 1995 22:11`	10
	Yes, you could very well run an editor just to test it out. As a matter of fact, that's how I test out event definitions. If they are going to use vi, they'll have to type 'i' for insert, otherwise, the terminal will just beep. Another command would be 'eurf -n' which would capture error messages. The psuedo terminal was designed primarily for applications which print out error messages or conditions. Dave
593.4		CSC32::PITT		`Thu Feb 02 1995 02:42`	3
	got it. thanks.!
593.5	Throw away that Manual.	OPG::SIMON		`Thu Feb 02 1995 08:55`	9
	Cathy, throw away the V1.0 manual, it bears little relation to V1.5 functionality, in fact there was no Psuedo transport in V1.0. Even if you don't have a hard copy of the manual it is online in ALL the kits in Bookreader format. You will be able to give more accurate info that way. Cheers Simon....
593.6		CSC32::PITT		`Fri Feb 03 1995 05:00`	8
	I did throw it away after I made copies of the 1.5 doc!! Thanks. by the way, after I figured out how to set it up and get it going, it was pretty straight forward! thanks!