Unix and Linux Discussions Tagged with issues |
|
Thread / Thread Starter |
Last Post |
Replies |
Views |
Forum |
|
|
|
1 |
6,186 |
Shell Programming and Scripting |
|
|
|
2 |
14,817 |
AIX |
|
|
|
48 |
21,207 |
What is on Your Mind? |
|
|
|
3 |
7,839 |
Web Development |
|
|
|
1 |
12,069 |
Red Hat |
|
|
|
4 |
7,040 |
What is on Your Mind? |
|
|
|
4 |
4,828 |
UNIX for Dummies Questions & Answers |
|
|
|
0 |
1,708 |
Solaris |
|
|
|
0 |
3,954 |
OS X Support RSS |
|
|
|
0 |
2,518 |
OS X Support RSS |
|
|
|
4 |
2,232 |
Shell Programming and Scripting |
|
|
|
0 |
2,200 |
AIX |
|
|
|
1 |
30,401 |
Linux |
|
|
|
0 |
1,818 |
UNIX for Dummies Questions & Answers |
|
|
|
12 |
5,377 |
Solaris |
|
|
|
3 |
3,306 |
UNIX for Dummies Questions & Answers |
|
|
|
8 |
5,084 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
4,165 |
UNIX for Advanced & Expert Users |
|
|
|
3 |
2,720 |
UNIX for Dummies Questions & Answers |
|
|
|
5 |
3,518 |
UNIX for Advanced & Expert Users |
|
|
|
2 |
2,575 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
17,109 |
UNIX for Advanced & Expert Users |
|
|
|
3 |
3,278 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
13,725 |
UNIX for Dummies Questions & Answers |
|
|
|
7 |
5,426 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
5,334 |
Programming |
|
|
|
7 |
5,364 |
UNIX for Dummies Questions & Answers |
|
|
|
3 |
163,883 |
UNIX for Dummies Questions & Answers |
|
|
|
6 |
6,741 |
UNIX for Dummies Questions & Answers |
|
|
|
7 |
4,130 |
UNIX for Dummies Questions & Answers |
|
|
|
4 |
32,918 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
7,381 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
4,171 |
UNIX for Dummies Questions & Answers |
|
|
|
2 |
3,067 |
UNIX for Dummies Questions & Answers |
|
|
|
1 |
7,169 |
Cybersecurity |
|
|
|
1 |
3,590 |
Cybersecurity |
timod(7) Miscellaneous Information Manual timod(7)
NAME
timod - STREAMS module for converting ioctl() calls into Transport Interface messages
DESCRIPTION
The module is a STREAMS module that converts calls from a transport user supporting the Transport Interface (TI) into messages that a
transport protocol provider supporting TI can consume. This allows the user to initiate certain TI functions as atomic operations. This
release of HP-UX no longer automatically pushes whenever a t_open(3) is performed. The TLI and XTI libraries have been modified to no
longer require this module to perform the atomic operations described within this man page. Binary compatibility is not a problem since
the module will still exist within the kernel. But, any application which is recompiled and expects the module to be automatically pushed,
may not work without code modification.
The user places and removes the module on a device stream by calling the STREAMS and functions. (The TLI function pushes onto the device
stream for the user.) The module should only be pushed onto streams which are terminated by transport providers which conform to the
Transport Interface. tirdwr(7) is an alternative interface to which supports the and system calls. If has been pushed onto the stream,
the user should use the to remove the module from the stream before pushing
The module transparently passes any STREAMS messages that are not generated by the commands described below to the neighboring module or
driver. will act on an whose field is one of the values below. (See streamio(7) for a description of the and the structure.)
This TI command binds an address to the transport protocol provider.
The STREAMS message that the module issues to the call is equivalent to the TI message type The STREAMS message that the
module returns in response to the successful completion of the call is equivalent to the TI message type
This TI command unbinds an address from the transport protocol provider.
The STREAMS message that the module issues to the call is equivalent to the TI message type The STREAMS message that the
module returns in response to the successful completion of the call is equivalent to the TI message type
This TI command gets the TI protocol-specific information from
the transport protocol provider. The STREAMS message that the module issues to the call is equivalent to the TI message
type The STREAMS message that the module returns in response to the successful completion of the call is equivalent to the
TI message type
This TI command gets, sets, or negotiates TI protocol-specific options with
the transport protocol provider. The STREAMS message that the module issues to the call is equivalent to the TI message
type The STREAMS message that the module returns in response to the successful completion of the call is equivalent to the
TI message type
RETURN VALUES
If the module returns an error for an call, the lower 8 bits of the return value will be one of the TI error codes defined in the header
file. If the TI error is of the type TSYERR, then the second 8 bits of the return value will contain an error as defined in the header
file. The STREAMS message that the module issues when an call results in an error is equivalent to the TI message type
FILES
defines the error codes for XTI functions.
defines the error codes for TI functions.
defines the message types for TI functions.
defines the error codes for system errors.
SEE ALSO
ioctl(2), t_open(3), streamio(7), tirdwr(7).
timod(7)