File: sockd.fr.5

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 (28 lines) | stat: -rw-r--r-- 1,049 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
.TH SOCKD.FR 5 "May 6, 1996"
.SH NAME
sockd.fr \- Frozen route file for multi-homed SOCKS proxy server
.SH SYNOPSIS
\fB/etc/sockd.fr\fP
.SH DESCRIPTION
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.

To find out the contents of a frozen route file, use
\fIdump_sockdfr\fR.
.SH SEE ALSO
\fIdump_sockdfr\fR(8), \fImake_sockdfr\fR(8),
\fIsockd\fR(8), \fIsockd.route\fR(5)
.SH AUTHOR
.nf
Ying-Da Lee, yingda@esd.sgi.com or yingda@best.com