Re: tcpsvd vs. tcpserver

On Tue, Oct 05, 2004 at 10:30:27AM -0400, Charlie Brady wrote:
> What I've found useful is to generate one config file for each policy I 
> wish to implement (in my case, only "local" and "default"), and generate 
> a set of symlinks for each network specification, viz: 0 -> default, 
> 192.168.1 -> local, 127.0.0.1 -> local, 10.39.155 -> local. [This approach 
> is perfect for me, since I generate all my config from a db of service 
> policies and network lists; it may be less useful if you expect a human to 
> construct the files and symlinks.]

I suggest to have the policy files start with a dot.  If ipsvd is run
with the -h option, a dns query could return "local" or "default", and
so possibly bypass the instructions.  dot-files are included into the
cdb, so you can also safely use them as "forward" in a check hostname
instruction.

Regards, Gerrit.