<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>* About the enPlugin disPlugin, i do not think the user will have a lot of benefit here.</div><div><br></div><div>It's great if there are a bunch of plugins which do not really need configuration, </div><div>if a (very) few packages need them it's ok, but if you *need* to configure every plugin</div><div>it would be a little configuration nightmare.</div><div><br></div><div>I rather prefer editing one file than go through a mess of dirs/files (i *HATE* the</div><div>exim4 new configuration, it's (IMO) a breaindead nightmare solution which</div><div>i can not overcome to only try it, i really do prefer the postfix configuration.</div><div><br></div><div>btw. how exactly handles postfix the configuration files? I like the way you can </div><div>select with debconf No config, Local only, Internet Mail, etc. ... </div><div>How does postfix writes this changes, as well with sed? I guess so because the</div><div>config file is clean and a reconfigure seems to just ad the missing parts, could be </div><div>wrong thought, never give it that much attention because it basically just works (tm).</div><div><br></div><div>Other solutions might be:</div><div><br></div><div><div>* I do not know if collectd can include other configuration files, but is it feasible to </div><div>make the main configuration (server/client/proxy/writelocally) in collect.conf and </div><div>make an include to collect.(local | additional).conf?</div><div><br></div><div>* what i do NOT like are constructs like in grub and other packages with lines: </div><div>"Do not change this line, it's managed by package X", "Make your changes below this line but do not delete it"</div><div>If possible this should be avoided</div><div><br></div><div><br></div></div><div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font><blockquote type="cite">In following with the apache example, maybe deliver<br></blockquote><blockquote type="cite">/etc/collectd/collect.conf.example, and have a debconf question to<br></blockquote><blockquote type="cite">copy it into place?<br></blockquote><br>Are you talking about "collectd-core"? I'd rather like to avoid<br>introducing debconf in that package as well. Imho, copying a sample<br>config from /usr/share/doc/ is about the same amount of work as<br>answering a debconf questions (which, in turn, would, presumably, avoid<br>quite a few people in that case).<br></div></blockquote>I second that collectd-core should be as simple as could be, do not see it</div><div>necessary to have debconf in here too.</div><div><br></div><div><br></div>the more i think of it the more i like the way postfix handles this, i would appreciate<div>the same approach for collectd!<br><div><br></div><div><div>best</div><div>Raimund</div><div><br></div><div><br></div></div></div></body></html>