File: make_socksfc.8

package info (click to toggle)
socks4-server 4.3.beta2-14
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 1,504 kB
  • ctags: 1,779
  • sloc: ansic: 19,305; makefile: 394; sh: 52
file content (39 lines) | stat: -rw-r--r-- 1,556 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
35
36
37
38
39
.TH MAKE_SOCKSFC 8 "May 6, 1996"
.SH NAME
make_socksfc \-  Generates frozen configuratyion file for SOCKS clients
.SH SYNOPSIS
\fBmake_socksfc [\fIinfile\fR [\fIoutfile\fR] ]\fP
.SH DESCRIPTION
make_socksfc reads in a plain-text configuration file for the
SOCKS clients and produces
a frozen configuration file as the output.

Both arguments are optional. The default for \fIinfile\fR is
\fB/etc/socks.conf\fP; the default for \fIoutfile\fP is
\fB/etc/socks.fc\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 configuration file is essentially the 
memory image of the parsed input 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 FILES
\fB/etc/socks.fc\fP, \fB/etc/socks.conf\fP
.SH SEE ALSO
\fIdump_socksfc\fR(8),
\fIsocks.conf\fR(5), \fIsocks.fc\fR(5)
.SH AUTHOR
.nf
Ying-Da Lee, yingda@esd.sgi.com or yingda@best.com