File: dump_sockdfr.8

package info (click to toggle)
socks4-server 4.3.beta2-13
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 1,512 kB
  • ctags: 1,778
  • sloc: ansic: 19,305; makefile: 404; sh: 52
file content (34 lines) | stat: -rw-r--r-- 1,234 bytes parent folder | download | duplicates (9)
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
.TH DUMP_SOCKDFR 8 "May 6, 1996"
.SH NAME
dump_sockdfr \-  Display contents of frozen route file for SOCKS server
.SH SYNOPSIS
\fBdump_sockdfr [\fIinfile\fR]\fP
.SH DESCRIPTION
dump_sockdfr reads in a frozen route file for the
SOCKS server and produces
a listing of its contents on the standard output.

The argument is optional; if omitted, \fB/etc/sockd.fr\fP is assumed.

The frozen route file is produced by \fImake_sockdfr\fR and
is essentially the 
memory image of the parsed route 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.
.SH FILES
\fB/etc/sockd.fr\fP, \fB/etc/sockd.route\fP
.SH SEE ALSO
\fImake_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