PortSever TS 16 ( PN 50000854 , SN W15170245 )
Solaris 10 on X86 ( HP DL 160 ).
This is a question not an issue.
Our software use the port as a normal serial comm. port, that is we open, set up env. Ioctl() like bits/baud/flow control…then read and write to the port like /dev/dty/xxxx .
My question if i set up a a port as “TCP Sockets” can i still use my same code as above that is open/env setup (bit/baud/…read/write to /dev/dty/xxxx
Or what needs to be done on my application code different. Is that port “/dev/dty/xxxx” not seen as a normal unix comm. port anymore.
My customer wishes to pass "TCP data down " that line. I understand it would be point-to-point and eat up a digi port, versus normal network interface. but that is not an issue