sockd.fr(5) [minix man page]

SOCKD.FR(5)							File Formats Manual						       SOCKD.FR(5)

NAME

       sockd.fr - Frozen route file for multi-homed SOCKS proxy server

SYNOPSIS

       /etc/sockd.fr

DESCRIPTION

       The frozen route file is produced by make_sockdfr 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 /etc/sockd.fr first. If that file is not found, it  then  tries	to
       use  the  plain-text  route file /etc/sockd.route. If you use frozen route file, you must remember to run make_sockdfr 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 dump_sockdfr.

SEE ALSO

       dump_sockdfr(8), make_sockdfr(8), sockd(8), sockd.route(5)

AUTHOR

       Ying-Da Lee, yingda@esd.sgi.com or yingda@best.com

								    May 6, 1996 						       SOCKD.FR(5)

MAKE_SOCKDFR(8) 					      System Manager's Manual						   MAKE_SOCKDFR(8)

NAME

       make_sockdfr -  Generates frozen route file for SOCKS server

SYNOPSIS

       make_sockdfr [infile [outfile] ]

DESCRIPTION

       make_sockdfr reads in a plain-text route file for the SOCKS server and produces a frozen route file as the output.

       Both  arguments	are optional. The default for infile is /etc/sockd.route; the default for outfile is /etc/sockd.fr. You may specify infile
       while omitting outfile, but you cannot specify outfile without also speficying infile.

       The contents of the frozen route file is essentially the memory image of the parsed input 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 /etc/sockd.fr first. If that file is not found, it then tries to
       use the plain-text route file /etc/sockd.route. If you use frozen route file, you must remember to run make_sockdfr 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 dump_sockdfr.

FILES

       /etc/sockd.fr, /etc/sockd.route

SEE ALSO

       dump_sockdfr(8), sockd.fr(5), sockd.route(5)

AUTHOR

       Ying-Da Lee, yingda@esd.sgi.com or yingda@best.com

								    May 6, 1996 						   MAKE_SOCKDFR(8)