1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
.TH MAKE_SOCKDFR 8 "May 6, 1996"
.SH NAME
make_sockdfr \- Generates frozen route file for SOCKS server
.SH SYNOPSIS
\fBmake_sockdfr [\fIinfile\fR [\fIoutfile\fR] ]\fP
.SH DESCRIPTION
make_sockdfr reads in a plain-text route file for the
SOCKS server and produces
a frozen route file as the output.
Both arguments are optional. The default for \fIinfile\fR is
\fB/etc/sockd.route\fP; the default for \fIoutfile\fP is
\fB/etc/sockd.fr\fP. You may specify \fIinfile\fR while omitting
\fIoutfile\fR, but you cannot specify \fIoutfile\fR without also
speficying \fIinfile\fR.
The contents of the frozen route file is essentially the
memory image of the parsed input file. Using the frozen route
file can reduce the start-up delay of the SOCKS server program since
it no longer has to parse the file contents.
When the SOCKS server starts, it always looks for the frozen
route file \fB/etc/sockd.fr\fP first. If that file
is not found, it then tries to use the plain-text route file
\fB/etc/sockd.route\fP. If you use frozen route file,
you must remember to run \fImake_sockdfr\fR every time after you
modify the plain-text file or the SOCKS server will continue to use
the frozen version of a previous route file.
To find out the contents of a frozen route file, use
\fIdump_sockdfr\fR.
.SH FILES
\fB/etc/sockd.fr\fP, \fB/etc/sockd.route\fP
.SH SEE ALSO
\fIdump_sockdfr\fR(8),
\fIsockd.fr\fR(5), \fIsockd.route\fR(5)
.SH AUTHOR
.nf
Ying-Da Lee, yingda@esd.sgi.com or yingda@best.com
|
