File: socks.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 (31 lines) | stat: -rw-r--r-- 1,105 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
.TH SOCKS.FC 5 "May 6, 1996"
.SH NAME
.nf
socks.fc \- Frozen configuration file for SOCKS clients
.fi
.SH SYNOPSIS
/etc/socks.fc
.SH DESCRIPTION
The frozen configuration file is produced by \fImake_socksfc\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 client programs since
they no longer have to parse the file contents.

When the SOCKS client starts, it always looks for the frozen
configuration file \fB/etc/socks.fc\fP first . If that file
is not found, it then tries to use the plain-text configuration file
\fB/etc/socks.conf\fP. If you use frozen configuration,
you must remember to run \fImake_socksfc\fR every time after you
modify the plain-text file or the SOCKS clients will continue to use
the frozen file of a previous configuration.

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