SUMMARY: Serial Terminal Changing Parity?

The following fixed my problem,

Richard Lacroix wrote:

> Hi,
> 
> in your pmadm command line try using '-l console' instead of '-l conttyH'

Here are the two entries from ttydefs(4),

   console:9600 hupcl opost onlcr:9600::console

   conttyH:9600 opost onlcr:9600 hupcl sane::contty1H

The crucial difference is the 'sane' in the conttyH entry. Apparently,
enabling parity is the "sane" thing to do. Forgot about that. Thanks,
Richard.

But I'm still not sure why conttyH works on another machine. :/

> Crist Clark wrote:
> 
>> Oops. My mail composer was kind enough to clean up those nasty 8-bit
>> characters I had cut in there in the "Password:" string. Notice that
>> when it cleared the bit, the proper answer came out. I'll write it
>> again as hexadecimal in the format vi(1) would display it,
>>
>> Crist Clark wrote:
>>
>>> Having a weird problem with a serial terminal server connected to a
>>> Sun running Solaris 8. It looks like there is a parity problem, but as
>>> far as I can tell, there shouldn't be. I cannot find where the 
>>> configuration
>>> on a system that works differs from one that does not.
>>>
>>> The banner gets printed out fine. So does the login prompt and the echo
>>> of the username. But then things go downhill,
>>>
>>>   [blah, blah, the disclaimer prints fine.]
>>>   | Anyone using this system expressly consents to such monitoring  |
>>>   | and is advised that if such monitoring reveals possible         |
>>>   | evidence of criminal activity, system personnel may provide the |
>>>   | evidence of such monitoring to law enforcement officials.       |
>>>   |-----------------------------------------------------------------|
>>>
>>>   ttya login: cclark
>>>   Password:
>>
>>
>>
>>   ttya login: cclark
>>   P\xe1\xf3\xf3wor\xe4\:\xa0
>>
>>> Those whacky characters in the password string look like parity checks
>>> kicked in. The next time the banner pops up, it is corrupted too.
>>> Everything is messed up until I stop the monitoring on the port, kill
>>> anything still running on it, and then start up monitoring again.
>>> Something like,
>>>
>>>     # pmadm -r -p zsmon -s ttya
>>>     <kill lingering processes>
>>>     # pmadm -a -p zsmon -s ttya -i root -f u -v `ttyadm -V` -m 
>>> "`ttyadm -d /dev/term/a -i 'terminal disabled' -l conttyH -p 'ttya 
>>> login: ' -s /usr/bin/login -T vt100 -S y`"
>>>
>>> The banner pops up just fine... until I try to log in again.
>>>
>>> My best guess is when the ttymon hands off the control of the terminal
>>> to login or whaterver, the tty settings are getting changed. Anyone
>>> know what I need to do to fix this? The terminal is set to no parity,
>>> and I'd much rather keep it that way.
>>>
>>> (Could you make the process of configuring serial ports any more
>>> convoluted? Sacadm, pmadm, ttymon, ttydefs, ttyadm, etc., etc.
>>> just to get a freakin' serial console up.)
>>
>>
>>
>>
> 
> 


-- 
Crist J. Clark                               crist.clark@globalstar.com
Globalstar Communications                                (408) 933-4387

The information contained in this e-mail message is confidential,
intended only for the use of the individual or entity named above.
If the reader of this e-mail is not the intended recipient, or the
employee or agent responsible to deliver it to the intended recipient,
you are hereby notified that any review, dissemination, distribution or
copying of this communication is strictly prohibited.  If you have
received this e-mail in error, please contact postmaster@globalstar.com
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers