tty port settings

[Rick Garland]

Hi all:

Got a K class box running 10.20 and an application called VSIFAX. Part of what VSIFAX looks for to send readable faxes is the tty port setting of 'stop' being ^S.

For the longest time this setting never changed and the faxes ran fine - this was good for over a year. All of the sudden, the tty port setting for 'stop' goes to and the faxes are wasted. I have manually set this tty setting and also done the the stty < /dev/ttyd0p6 believing this would set the port as default. Will go for a few days and then it will become undefined again resulting in wasted faxes.

What is causing the port to lose the stty setting and is there a way to set the stty on the port so it doesn't go away anymore?

Many thanks

[Sanjay_6]

Hi Rick,

I believe there was a posting on his foum about another user having the same problem of the setting reset after running ignite "make_recovery".

Is it different in your case.

thanks

[Sanjay_6 · Accepted solution]

Hi Rick,

Here is the thread to the question i was talking about.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,11866,0xb6f3c6af36b7d5118ff10090279cd0f9,00.html

Hope this helps.

thanks

[A. Clay Stephenson]

Hi Rick:

That typically happens when the port is being closed and re-opened. On all of my vsifax boxes, I've made a little routine called holdport which does just what its name implies. It all K&R c so it will compile using the bundled compiler. This thread has the source + the rc stuff.
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x6c7dabe92dabd5118ff10090279cd0f9,00.html

[Uday_S_Ankolekar]

Hello,

I'm sure running make_recovery is changing this parameter.
In my environment I had same problem (visifax on HP 11X) ,After checking all possible reasons I came to conclusion that make_recovery does changes stty stop parameter.
I did not run make_recovery for a week ( I run it once a week) and stty stop paramaeter was unchanged

Something HP should look into.

-USA

[Rushank]

Hello,

I'm discussing this matter with forum...

It's a problem with make_recovery for sure.


http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xb6f3c6af36b7d5118ff10090279cd0f9,00.html

-Rush..