![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to isotailor.5 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / support|
Return to isotailor.5 CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / support |
1.1 root 1: .TH ISOTAILOR 5 "5 July 1988"
2: .\" $Header: /f/osi/support/RCS/isotailor.5,v 7.5 90/07/09 14:50:51 mrose Exp $
3: .\"
4: .\"
5: .\" $Log: isotailor.5,v $
6: .\" Revision 7.5 90/07/09 14:50:51 mrose
7: .\" sync
8: .\"
9: .\" Revision 7.4 90/01/11 18:38:00 mrose
10: .\" real-sync
11: .\"
12: .\" Revision 7.3 89/12/12 16:14:33 mrose
13: .\" localHost
14: .\"
15: .\" Revision 7.2 89/11/30 23:51:52 mrose
16: .\" typo
17: .\"
18: .\" Revision 7.1 89/11/27 10:30:48 mrose
19: .\" sync
20: .\"
21: .\" Revision 7.0 89/11/23 22:27:37 mrose
22: .\" Release 6.0
23: .\"
24: .SH NAME
25: .B isotailor
26: \- ISODE tailoring file
27: .SH DESCRIPTION
28: The \fIisotailor\fR file contains information used to run-time
29: configure the ISODE distribution.
30: Entries are separated by end\-of\-line (or the end\-of\-file).
31: The character `#' at the beginning of a line indicates a comment line.
32: The syntax is:
33: .sp
34: .in +.5i
35: .nf
36: variable: value
37: .fi
38: .in -.5i
39: .sp
40: as in
41: .sp
42: .in +.5i
43: .nf
44: sbindir: /usr/etc/
45: .fi
46: .in -.5i
47: .PP
48: The entries come in several types. There are general ISODE
49: configuration parameters, operating system specific tailoring and
50: interface specific tailoring parameters.
51: .SH "LOCAL ENVIRONMENT TAILORING"
52: There are some variables that are used to make up for deficiencies in
53: operating systems, or to override the operating system. These are
54: described as follows.
55: .IP localname
56: This takes a string as a parameter and is used as
57: the name of the local host if the \fIgethostname\fR call
58: (or equivalent, e.g., \fIuname\fR)
59: is not used. This will also override any other run-time determination
60: of the local hostname.
61: .IP binpath
62: This takes a string as a parameter and indicates the directory where
63: the ISODE user programs are kept (be sure to use a trailing slash).
64: .IP sbinpath
65: This takes a string as a parameter and indicates the directory where
66: the ISODE system programs are kept (be sure to use a trailing slash).
67: .IP etcpath
68: This takes a string as a parameter and indicates the directory where
69: the ISODE configuration files are kept (be sure to use a trailing slash).
70: .SH "LOGGING TAILORING"
71: There are a number of options that can be set for each layer of ISODE.
72: The first variable indicates the default logging directory,
73: the other variables give information about each log file.
74: .IP logpath
75: This variable takes a string as a parameter and indicates the
76: directory where the ISODE log files are kept (be sure to use a
77: trailing slash).
78: .PP
79: The remaining variables are all configured in the same way and are in
80: the general format:
81: .sp
82: .in +.5i
83: .nf
84: xyzlevel: [none] [exceptions] [notice] [pdus] [trace] [debug] [all]
85: xyzfile: filename
86: .fi
87: .in -.5i
88: .sp
89: The filename can be either the name of a file of a `\-' in which case
90: the standard error is used. If the filename contains the string `%d'
91: then this is replaced by the current process id.
92: .PP
93: The normal level for this style of tailoring is to set exceptions. The
94: other two values can be added in when debugging, if so desired.
95: The current variables in this format are as follows.
96: .sp
97: .in +.5i
98: .nf
99: .ta \w'compatlevel 'u
100: compatlevel native services subsystem
101: compatfile
102: addrlevel addressing subsystem
103: addrfile
104: tsaplevel transport level
105: tsapfile
106: ssaplevel session level
107: ssapfile
108: psaplevel presentation elements
109: psapfile
110: psap2level presentation level
111: psap2file
112: acsaplevel association control level
113: acsapfile
114: rtsaplevel reliable transfer level
115: rtsapfile
116: rosaplevel remote operations level
117: rosapfile
118: .sp
119: .in -.5i
120: .fi
121: .SH "TRANSPORT STACK TAILORING"
122: There are several variables which can be used to en/disable configured
123: TS-stacks and to define OSI communities and their relationship
124: to this system.
125: .SS "TS-STACKS"
126: .IP ts_stacks
127: which takes one or more of the following values:
128: .sp
129: .in +.5i
130: .nf
131: [tcp] [x25] [bridge] [tp4] [all]
132: .fi
133: .in -.5i
134: .sp
135: indicates which TS-stacks should be enabled.
136: This is useful when multiple machines (with different interfaces)
137: share the same executables.
138: For example,
139: the \fB\*(EDisotailor\fR file is a normally symbolic link to
140: \fB/private\*(EDisotailor\fR.
141: .SS "OSI COMMUNITIES"
142: .IP ts_interim
143: which takes one or more OSI community names as a value.
144: Each community name must be defined as a macro in the
145: \fIisomacros\fR\0(5) file.
146: .IP ts_communities
147: which takes one or more of the following values:
148: .sp
149: .in +.5i
150: .nf
151: [int-x25] [janet] [internet] [realns] [localTCP] [all]
152: .fi
153: .in -.5i
154: .sp
155: This variable is used to distinguish membership in various OSI communities.
156: For example,
157: a site with an X.25 connection might be attached to the International X.25
158: network, but not the JANET.
159: Thus \fIts_stacks\fR would include \*(lqx25\*(rq,
160: and \fIts_communities\fR would include \*(lqint-x25\*(rq but not
161: \*(lqjanet\*(rq.
162: Note that the ordering of communities is important:
163: network addresses will be tried in the order that their respective
164: communities are listed with this variable.
165: .IP default_nsap_community
166: which takes an integer value,
167: declaring the default community to be used for NSAP addresses.
168: .IP default_x25_community
169: declaring the default community to be used for X.25 (DTE) addresses.
170: .IP default_tcp_community
171: declaring the default community to be used for TCP (RFC1006) addresses.
172: .SS "TS-BRIDGE"
173: These are the parameters that are used in the Transport-Service Bridge
174: implementation.
175: .IP tsb_communities
176: A list of pairs of values.
177: The first of each value should be a community as defined in the
178: \fIts_communities\fP variable
179: (obviously the values \*(lqnone\*(rq and \*(lqall\*(rq are not permissible).
180: The second value of the pair should be a presentation address using
181: the ISODE \*(lqstring\*(rq format.
182: When a call is to be placed and the network corresponds to one
183: of the communities given here, then a call through the bridge given in
184: the second variable will be made automatically.
185: .IP tsb_default_address
186: This variable contains a string encoded presentation address which the
187: bridge will listen on by default.
188: This should normally consist of a set of network addresses with no selectors
189: present.
190: .PP
191: Consider the case of a host with access to both the Internet and the
192: International X.25 network.
193: This host might have this entry in its \fIisotailor\fR file:
194: .sp
195: .in +.5i
196: .nf
197: tsb_default_address: Internet=sheriff+17004\\|Int-X25(80)=23426020017299+PID+03018000
198: .fi
199: .in -.5i
200: .sp
201: This tells the bridge to listen on two network endpoints.
202: Hosts in the Internet community wishing to reach the International
203: X.25 community would have this entry in their \fIisotailor\fR file:
204: .sp
205: .in +.5i
206: .nf
207: tsb_communities: int-x25 Internet=sheriff+17004
208: .fi
209: .in -.5i
210: .sp
211: Similarly,
212: hosts in the International X.25 community wishing to reach the
213: Internet community, would have the entry:
214: .sp
215: .in +.5i
216: .nf
217: tsb_communities: internet Int-X25(80)=23426020017299+PID+03018000
218: .fi
219: .in -.5i
220: .SH "INTERFACE SPECIFIC TAILORING"
221: Most interfaces that ISODE runs over have some form of tailoring.
222: These are usually very dependent on the interface. Each interface
223: which supports tailoring will now be described.
224: .SS "General X.25 Tailoring"
225: There are two specific variables that can be used with any X.25
226: interface.
227: .IP x25_local_dte
228: This is the X.121 address that ISODE processes will listen on
229: by default.
230: It may be a full X.121 address or a sub-address.
231: .IP x25_local_pid
232: This is the X.25 protocol ID that ISODE processes will listen on by default.
233: Traditionally, this is the first four octets of the CUDF in hex-notation,
234: e.g., 03010100.
235: .PP
236: There are also three variables for performing address
237: manipulation as required by some network vendors.
238: .IP x25_intl_zero
239: If this has the value `on' then any international DTEs (i.e.
240: having non\-local DNICs) will have a leading zero introduced
241: before being passed to the network.
242: .IP x25_strip_dnic
243: If this has the value `on' then any local DTEs (i.e. having the
244: local DNIC) will have this DNIC removed before being passed to
245: the network.
246: .IP x25_dnic_prefix
247: This should be set to the local DNIC (the first four digits of the
248: DTE) of the host machine.
249: It should only be set if one or both of the previous two
250: variables has the value `on'.
251: .PP
252: There are also two variables for logging X.25 statistics.
253: .IP x25level
254: Defines the level of logging to be used for X.25 statistics logging.
255: (At present, only \*(lqnotice\*(rq level messages are generated.)
256: .IP x25file
257: Defines the filename to be used for X.25 statistics logging.
258: .SS "SUNLINK X.25"
259: These setting are only useful when SUN_X25 is defined along with X25.
260: The effect of these parameters is more fully documented in the Sun manuals.
261: .IP reverse_charge
262: Set to 1 or 0 to enable/disable reverse charging.
263: .IP recvpktsize
264: .IP sendpktsize
265: This should be set to one of 0 (default), 16, 32, 64, 128, 256, 512 or
266: 1024 to set the send/receive packet size.
267: .IP recvwndsize
268: .IP sendwndsize
269: This sets the send/receive window sizes. Legal values are 0 (default),
270: 7 and 127.
271: .IP recvthruput
272: .IP sendthruput
273: This sets the sending/receiving throughput values. Legal values are 0
274: (default) 75, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, 48000.
275: .IP cug_req
276: Closed user group request. Set to either 0 or 1.
277: .IP cug_index
278: Sets the closed user group index number.
279: .IP fast_select_type
280: Sets the fast select parameters. Either 0, 1 or 2.
281: .IP rpoa_req
282: .IP rpoa
283: Recognised private operating agency parameters.
284: .SS "CAMTEC CCL"
285: These are used
286: when the Camtec X.25 is accessed via the
287: CCL (sockets) mechanism.
288: .IP x25_outgoing_port
289: This selects which port on the Camtec card will be used
290: for outgoing calls, and takes the value A, B or #.
291: A and B are the two X.21 WAN interfaces and # is the
292: Ethernet.
293: Listening is automatically done on all three ports.
294: .SS "BRIDGE X.25"
295: These are parameters that are used in the tp0bridge implementation.
296: .IP x25_bridge_host
297: The host machine that is running the tp0bridge.
298: .IP x25_bridge_port
299: This is the TCP port that is to be used
300: for bridging.
301: The default is 146, which should be in defined in /etc/services.
302: .IP x25_bridge_addr
303: The X.121 address of the remote host.
304: .IP x25_bridge_listen
305: The X.121 address to listen on for incoming calls, on the remote host.
306: .IP x25_bridge_pid
307: The protocol ID used for listening along with the previous address.
308: This is encoded as a string of eight hex digits.
309: .IP x25_bridge_discrim
310: A string used to discriminate the network. When attempting to place an
311: X.25 call with BRIDGE_X25 and real X25 configured in, this string is
312: used to decide which interface to use. If the string is empty, the
313: bridge will be used. If it is set to `\-' the bridge will not be used.
314: If the string is anything else, it is compared against the called
315: X.121 address. If there is a match, then the bridge is used, otherwise
316: the real interface is used.
317: .SH "DIRECTORY SERVICES TAILORING"
318: There are two variables that can be tailored:
319: .IP ns_enable
320: This takes either the string \*(lqon\*(rq or \*(lqoff\*(rq as a parameter.
321: If \*(lqon\*(rq,
322: then the \*(lquser-friendly namservice" will be used to perform
323: name/address resolution.
324: If the nameservice lookup fails,
325: the stub-directory will be used as a fallback.
326: .IP ns_address
327: This is the transport address of the nameservice.
328: It is specified using the ISODE \*(lqstring\*(rq format,
329: e.g.,
330: .in +.5i
331: Internet=wp.psi.com+17006
332: .in -.5i
333: which indicates that the nameservice lives in the TCP/IP communications domain
334: on TCP port \*(lq17006\*(rq at host \*(lqwp.psi.com\*(rq.
335: The nameservice is accessed via the OSI CO-mode transport service,
336: so other kinds of addresses (e.g., X.25 addresses can be used as well).
337: .SH "PROGRAM-SPECIFIC TAILORING"
338: By default
339: a program-specific tailoring file is consulted before the system\-wide
340: tailoring file.
341: The program-specific file is called \fB\&.myname_tailor\fR in the user's
342: home directory,
343: where \*(lqmyname\*(rq is the name that the program was invoked with.
344: .SH FILES
345: .nf
346: .ta \w'$HOME/.myname_tailor 'u
347: \*(EDisotailor ISODE tailoring file
348: $HOME/.myname_tailor program-specific tailoring file
349: .re
350: .fi
351: .SH "SEE ALSO"
352: \fIThe ISO Development Environment: User's Manual, Volume 2:
353: Underlying Services\fR, \*(lqThe ISODE Tailoring File\*(rq.
354: .SH AUTHORS
355: Marshall T. Rose
356: .br
357: Simon Walton,
358: University College London
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.