eBox - the story continues :)

[Soren Hansen]

I need a bit of advice.

I've found a good solution for adding schemas and ACL's to the ldap
configuration as discussed last week, but now I'm faced with a slightly
different problem.

While adding schemas to the LDAP server is likely to be useful for many
different packages, setting up ntpd or a dhcp server isn't.
Traditionally, this has been of interest only to the package itself (and
the admin, of course), but now when dealing with a framework like eBox
which is supposed to be used to manage different services (e.g.  ntpd
and dhcp), how would you recommend going about this?

The most straight-forward solution would be if there existed a special
no-conf version of the ntp package.  It wouldn't have any configuration
files installed by maintainer scripts and no rc?.d links. That would
make it completely ok for the admin's configuration tool of choice to
add a configuration file to it and mess about with rc?.d links and
whatnot. The problems would of course arise if several such tools were
to mangle configuration files like that, but that's a different can of
worms.

Second, if e.g. ntp.conf wasn't a conffile, I could try to parse its
contents and use it to only tweak the tiny bits I actually need to, so
that I didn't add any unexpected changes to the admin's config file. The
problem is, though, that having ntp.conf marked as a conffile is what
most non-eBox-users will want it to.

I can't come up with any really good solutions at this hour, I'm afraid.
Any pointers?

-- 
Soren Hansen
Ubuntu Server Team
http://www.ubuntu.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20070801/a2dd5bd1/attachment.pgp