File: sockd.fc.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,091 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.FC 5 "May 6, 1996"
.SH NAME
sockd.fc \- Frozen configuration file for SOCKS server
.SH SYNOPSIS
\fB/etc/sockd.fc\fP
.SH DESCRIPTION
The frozen configuration file is produced by \fImake_sockdfc\fR and
is essentially the
memory image of the parsed configuration file. Using the frozen configuration
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
configuration file \fB/etc/sockd.fc\fP first. If that file
is not found, it then tries to use the plain-text configuration file
\fB/etc/sockd.conf\fP. If you use frozen configuration,
you must remember to run \fImake_sockdfc\fR every time after you
modify the plain-text file or the SOCKS server will continue to use
the frozen file of a previous configuration.

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