Chase Research IOLAN+, Руководство пользователя и администратора

Страница: 80 / 150

74
IO LAN +
- User and Administration Guide
8.3 Tips
Unix Notes
On Unix variants based on System V Release 3, clients that
are interactive shell processes may not be able to handle the
interrupt, quit and break keys properly. This is a deficiency
in the pseudo-tty drivers and not the daemon.
On some System V Release 4 variants, if the daemon writes
to a non-existent client, the pseudo-tty may irretrievably
hang up. In general, make sure there is always a client
process running if there is the possibility of data being
received for it.
On some systems such as SunOS, XENIX and AIX a break
received from the peripheral is not passed to the client
properly. If the client wishes to make the break act like an
interrupt key (i.e. when the stty options -
ignbrk and brkintr
are set) then this can be achieved by setting the Break field
on the IOLAN+ Port Setup Menu to ‘Brkintr’.
On SunOS, if a getty is the client process running to a
terminal then the login prompt may be corrupted on the
screen but this goes when the user name is typed in. The
UUCP command
uucico may not work with ioland on
Solaris 2.1 (Intel).
Some systems may not properly propagate the SIGHUP
signal associated with the
-h option.