Bert Grubbs from Digital UNIX Net Support (DSNlink) best answered the question:
>>It is OK to run both types of devices, right?
yes, it is ok to run both SVR4 and BSD type terminals. For OSF 3.2 the
only difference is the device name. They are both 'streams' devices.
>>tty09 through tty0C give IO errors when trying to cat to the LAT port, these
>>are all Xyplex servers(coincidence??).
This problem is associated with NOT having group 0 enabled on the Xyplex
terminal servers. It's something that has changed from OSF 2.0 to 3.2
where OSF has group 0 enabled by default and requires that group of the
terminal servers match.
We are in the process of escalating this to engineering, but in the
meantime you'll have to enable group 0.
Let me know how this works out.
--Bert Grubbs
Digital UNIX Net Support
------------------------original post--------------------------------------
I'm in the process of setting up LAT printers and I'm running some LAT port
problems. When first setting up the system (OSF v3.2A), I created 200 SVR4
LAT devices, 130 of which have gettys running. All the LAT/printer
documentation refers to using BSD devices, so using latsetup I created 50
BSD LAT devices, no gettys. It is OK to run both types of devices, right?
Now to the problem.
tty02 through tty08 work just fine, these are all connected to DECservers.
tty09 through tty0C give IO errors when trying to cat to the LAT port, these
are all Xyplex servers(coincidence??). Command syntax used...
# latcp -A -p tty02 -H SERVER_NAME_IN_CAPS -R PORT_NAME_IN_CAPS
I even tried the server and port name in lowercase and it seems to be converted
to uppercase anyways.
While messing with this, I ran into what could be a hint. While giving up on
LAT, I figured I'll recreate the tty09 through tty0C devices and try solving
from a different angle. When doing this, one port gave this error..
# latcp -A -p tty0B -H SIRIUS -R PORT_11
Port tty0B is in use.
so I tried to delete the port....
# latcp -D -p tty0B
Port tty0B is not an application port
Using lsof I couldn't find any refernce to tty0B. When doing an ls, it looks
just like others..
crw-rw-rw- 1 root system 5, 35 Jul 20 11:24 tty0B
crw-rw-rw- 1 root system 5, 36 Jul 20 11:25 tty0C
Anyone have an good clues?
The "Authorized Groups" setting on the server ports is set to the right group
for this system. In fact, when on these servers I can see the system as being
available with SHOW SERVICES.
-Bill Sadvary
Dickinson College
------------------------end of original post--------------------------------
A thanks to Rudolf Gabler (RUG_at_USM.Uni-Muenchen.DE) for his reply..
>This is a little bit surprising. In my case, The command (..is in use)
>said what it said. It was in use!
>I created the application port and then used it. When I wanted to reset
>it, I had first to stop all lpd and references in /etc/printcap before I
>could reset the application port. And of course lprm the queued jobs.
>Regards,
>Rudi Gabler
Received on Fri Jul 21 1995 - 17:12:49 NZST