[bind] bind in multi eth (virtual) situations

[Joseph S D Yao]

On Thu, Sep 21, 2000 at 03:40:15AM -0400, amh wrote:
> options { listen-on { xxx.xxx.xxx.xxx; }; query-source address
> xxx.xxx.xxx.xxx port *; transfer-source xxx.xxx.xxx.xxx; };
> 
> (side note: am i the only one that compresses named.conf entries to one
> line? sure makes it easier scripting.)

I maintain long configuration documents.  I change a few things at a
time.  Were I to keep free-form configurations in one long line, then
every time I check something in with SCCS, RCS, CVS, or the like, it
would register one line changed - the huge one.  When I have a problem
and use the configuration management tool to check what has changed ...
I get one big huge long line, very unhelpful - I have to scan visually
to see what the changes are.

Besides, I don't see how one big long ugly ;ine makes for "easier"
scripting.  I can group, understand, and make changes more quickly when
things are laid out in more than one dimension.  Two helps some:

options {
	listen-on {
		xxx.xxx.xxx.xxx;
	};
	query-source address xxx.xxx.xxx.xxx port *;
	transfer-source xxx.xxx.xxx.xxx;
};

And now any changes are isolated.  And the hugelongline doesn't break
in the middle of a statement, as yours did.

If you only have one thing between {}s, then I wouldn't mind:
	listen-on { xxx.xxx.xxx.xxx; };
except for the fact that, the minute you want to change it, you have to
expand it again.  Or, rather, I would.

This is all, of course, a matter of perception.  If your perceptions
are young and sharp and will ALWAYS BE SO, go ahead and write things
unreadably.  It will certainly make it difficult for you to ever be
replaced.  ;-}

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.