Provided by: socks4-server_4.3.beta2-18_i386
sockd.fc - Frozen configuration file for SOCKS server
The frozen configuration file is produced by make_sockdfc 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 /etc/sockd.fc first. If that file is not found, it
then tries to use the plain-text configuration file /etc/sockd.conf. If
you use frozen configuration, you must remember to run make_sockdfc
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
dump_sockdfc(8), make_sockdfc(8), sockd.conf(5), sockd.fc(5)
Ying-Da Lee, email@example.com or firstname.lastname@example.org
May 6, 1996 SOCKD.FC(5)