> Of course! I would therefore argue that complete specification is
> necessary if you have a requirement to meet changing requirements
> retrospectively. If your requirements are less formal (or less
Actually, not always. In the case of something like syslog, you
can actually assume that whatever your vendor gave you is reasonable,
and then when the time to care comes, you just replace the
configuration wholesale with your generated configuration (cp
generated-file /etc/syslog.conf && /etc/rc.d/syslog restart or
whatever). Your domain may vary.
Stoping the caring is a little more annoying, as you'll suddenly
have two sets of machines: those that had their syslog side effected
from vendor default, and newer machines that still have vendor
default. This may be undesirable.
> paranoid), you can probably do without it. What other problems am I
> missing?
Well, I'd like it if you could help me find my marbles, but I'll
admit that it's not terribly likely at this point.
Follow-Ups:
References:
|
|
