[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

881.0. "PCM v1.6 and Psuedo_Terminal Type Connections" by SNOOTY::DAWSONJ (Evening Squire...) Fri Jul 21 1995 12:05

Hi there,

	 A customer recently asked me how to set PCM up to monitor the
	node it was running on.  He explained that he was intending to 
	install a Watchdog-type product.

	 The Psuedo-Terminal connection seemed to be the best idea, so
	using one of our v1.6 systems I looked how this would need to
	be set up.  After some time, we came to the conclusion that
	PCM wasn't quite doing what it should.

	 When it tries to start the command procedure that PCM creates
	(in console$tmp), it doesn't seem to get the filename, since
	when you monitor the node you can see the '@' being displayed
	but no filename.  Also the actual terminal is not setup correctly
	since any REPLYs do not get broadcasted.

	 The COMMAND we gave when we set up the system was "@TEST.COM",
	and here is the file:

$ set term/broadcast
$ reply/enable
$ wait 2:00

	... I also checked that there were no SET TERM/INQUIREs in
	either SYLOGIN or LOGIN.

	 I told the customer the theory of setting this up, and on his
	v1.5 system it worked perfectly.  Is this a problem with v1.6,
	or am I missing something?

Thanks in advance,


James.
UK CSC.
T.RTitleUserPersonal
Name
DateLines
881.1SYLOGIN output ?ULYSSE::STRATMANPeter Stratman @VBOFri Jul 21 1995 12:397
    I found that the command file never executed when anything was sent to
    the FTA during execution of SYLOGIN. The only workaround I found was to
    send all output to a temporary file which I type out with the command
    file..

    The other solution is to modify SYLOGIN to stay quiet, but that was not
    an option at this customer's site.
881.2CSC32::BUTTERWORTHGun Control is a steady hand.Fri Jul 21 1995 23:207
    You will find that doing just about any SET TERM commands will screw
    it up. Youcould also modify SYLOGIN.COM to check if the terminal device
    is an FTA device. If it is, just skip any SET TERM commands. They
    really aren;t needed as all decterms are setup as a VT3xx anyway.
    
    Regs,
      Dan
881.3COMICS::DAWSONJEvening Squire...Tue Jul 25 1995 12:2613
	 When we were trying to set this up we modified our SYLOGIN.COM
	to contain the following:

$ dev_name = f$trnlnm("tt")
$ if f$locate("FTA", dev_name) .eqs. f$length(dev_name)
$ then
$  set term/inquire
$ endif

	... and yet things still were not working.

James.
881.4CSC32::BUTTERWORTHGun Control is a steady hand.Wed Jul 26 1995 18:115
    Do you have any SET CONTROL=T or SET CONTROL=Y commands being executed?
    These will also make it break.
    
    Regs,
      Dan