pseudo-port problem

[Alain St-Laurent]

Itâ s a bit hard to explain, but we have pseudo-ports (usually one, sometimes two) that acts
As if the keyboard return key was stuck.

If a user tries to log in our applications and gets one of these ports
he wonâ t be able to enter the applications and he will have to close
is session.

That problem has been with us for some time now.
I tought the problem was due to a bug with an application (Double-Vision) that we use to take control of
Userâ s terminal for support.

And after a reboot the problem went away for weeks
Even months.

About a month ago a reboot no longer solved the problem
And we have a persistant problem with the
Pseudo-port /pty/ttypc

is there a way to remove that port
or make

[Darren Prior]

Hi,

rmsf and insf could be used to remove and readd the port. Check the man pages for the full syntax.

regards,

Darren.

[A. Clay Stephenson]

Before removing any device nodes, the first thing that I would do is an ls -l /dev/pty and closely look at the major/minor device number tuples. Do they appear logically consistant and ordered.

This really sounds like a problem with the ptys driver itself rather than a particular device node. I would look for any patches related to the pseudo terminal driver for your OS release. Of course, your DoubleVision application could be doing some terrible ioctl()'s on a port and that is really what is your problem.

[Alain St-Laurent]

I will look out the syntax to remove
and/or re-create the port.

ls -l

gives me no special indication

crw--w---- 2 root tty 17 0x00000b ...ttypb
crw--w---- 2 root tty 17 0x00000c ...ttypc
crw--w---- 2 root tty 17 0x00000c ...ttypd

[A. Clay Stephenson]

Well ls -l gives me one:
crw--w---- 2 root tty 17 0x00000b ...ttypb
crw--w---- 2 root tty 17 0x00000c ...ttypc
crw--w---- 2 root tty 17 0x00000c ...ttypd


Note that ttypc and ttypd share a common minor device number. That could cause exactly the symptoms you are seeing.

[Alain St-Laurent]

sorry about the misunderstanding...

I made a typo you shoud have seen

crw--w---- 2 tty 17 0x00000d May 14 15:14 ttypd

[A. Clay Stephenson · Accepted solution]

Well, in that case, if you see no discrepancies removing and recreating the device nodes will do no good. All these do is create the hooks between the names we humans use for a device and the major/minor device number tuples that the kernel uses.

I would first focus on finding patches related to the driver.

[Alain St-Laurent]

since for now it's the only
port with that problem
I'll remove it, and plan on some patches.

Thank You !!!