TERM and Digi MIO??

[ppalanca]

Trying to invoke [term -ilttyr1A] at command line with /dev/ttyr1A set to 666. TERM will timeout and fail.

Then will disable port and [term -ilttyr1A] will be then able to connect to port. Will then back out and enable ttyr1A...and will then be able to connect to port fine through TERM.

This is a Digi/Acceleport [2 serial] PCI on SCO 5.0.6. Could this be an issue with interrupt channel? In that TERM can't complete a lockout of port [/usr/spool/uucp/LCK..**] when the Digiport is enabled.
But if we help it along by first disabling port, allowing a connection...somehow TERM learns something about that same port and is then able to control it when it's enabled. Grrrrrrrr.

Suspect incompatibility between Century TERM and Digi MPI. Neither company is willing to help.

Anyone run into this situation before?

 

[patw]

Dump TERM. Century takes YEARS to fix bugs and is expensive to boot.

Try CRT instead:

http://www.vandyke.com

get a 30 day demo - $34.95 if you want to license it.

At least if CRT has problems you have more ammo to hit Digi with since that would seem to indicate a bad port. (have you tried other ports?) Pat Welch, UBB Computer Services
Caldera Authorized Partner
Unix/Linux/Windows/Hardware Sales/Support
(209) 745-1401 Fax: (413) 714-2833

 

[edfair]

tty1A or tty1a? Don't know if it matters , but other stuff thinks 1A has modem controls. And don't know if the normal delay in bringing 1A back to init state would affect it. Ed Fair
unixstuff@juno.com
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[Megabitman]

I'd be highly suspicious that Term is causing your issue or Digi. The fact that you have a LCK file indicates that the serial port is in use for a dialup connection via UUCP. Remove the entry in uucp and that should cure your problem since it is probably initializing the serial port.

 

[Guest_imported]

How TERM interacts with Digi through [port monitoring] is the real issue. Set for strictly dialin and Digi works great on the modem control port; throws a LCK on terminal port (ttyr1a) and releases upon exiting as it should. But try to get to port through callout as TERM does...it's not consistant....unless you help/push it along.

Stuck with TERM Patw, but I'll try out CRT just the same, thanx.
Mega? Not sure what you meant...but yes, whatever TERM does to LCK the port from other users accessing...it's not able to complete in time due to some unknown conflict "timeout/unknown transport". Move it out of the way [port disabled from start] and it's accessible.

Went to an Equinox solution [SST brd] and it works fine. Darnit...I hate "cookbook" knowledge.

 

[Megabitman]

This is a snippet from a post I made this am which may apply to your situation here. I had forgotten about this issue with Digi until this am. See if this helps.

There is one other thing that I had forgotten about until this am. Check your files under /etc/conf/init.d to ensure that the settings in the files there match what you have set up in /etc/inittab. I had forgotten that when you manually edit inittab, the files that call the initialization processes here do not get updated. For example, you may set tty1A to 38400 in inittab eg # o but the "sio" file under /etc/conf/init.d is not altered. When the port is reset after a logout ( and I've never bothered to find out why this happens ), the port will fall back to the speed specified in this directory. The default for tty1A is 3 so the login will be offered at 2400. Each serial manufacturer ( I believe...) delivers a different file into this directory. I use primarily Computone so the ports are delivered in a file called ncxa. When you disable and then re-enable your ports, a second line will be listed as being updated. That will be the file in this directory. See if this helps your serial communications (this is true for ANY serial logins being offered!)

HTH,

Ken

 

[ppalanca]

The [ncxa] file would be for RealPort access on a Digiport ServerII. This situation was for Acceleport/MPI access. The actual inittab reference file for this is /etc/conf/init.d/epca...but can also be accessed through [MPI] utility running on server.

Again..believe issue is with Century/TERM and Digi. Though you're pointing at the problem...in that the mechanism that Digi uses seems too archaic for TERM to handle.

thanx,
-paul