Provided by: socks4-server_4.3.beta2-19build1_amd64 bug


       make_sockdfr -  Generates frozen route file for SOCKS server


       make_sockdfr [infile [outfile] ]


       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/  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/
       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.


       /etc/, /etc/sockd.route


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


       Ying-Da Lee, or

                                           May 6, 1996                            MAKE_SOCKDFR(8)