[Server-devel] Warning: breakage updating xs-config

[Martin Langhoff]

On Tue, Aug 12, 2008 at 1:49 AM, Jerry Vonau <jvonau at shaw.ca> wrote:
> Martin Langhoff wrote:
>>
>> A few weeks ago Bryan and David reported breakage with xs-config, and
>> over the last week over various tests we've had xs-config updates
>> making a mess of already-configured XS setups. I haven't had a chance
>> to look at it but yes, it is a high priority bug, and I'll be working
>> on it asap.
>>
> Sorry, coming up to speed, Ticket number? Got some info on the method used,
> and what failed?

#7708 - If you just install an XS, do the basic config (domain_config,
etc) and then install a new xs-config, the install mechanism makes a
mess. One tell-tale sign is that the files edited by domain_config are
overwritten. Diagnosing more later...

> Based on my F9 testing, while you have xs-config open, can you remove
> syslogd from the requires? Syslogd will still be installed based on the
> comp.xml file anyway. Without removing this requires from xs-config,
> updating past F7 becomes impossible as syslogd was later renamed/replaced.

What is the new name? The depends is there because we do override
/etc/syslogd.conf

> The same goes for newt-perl in xs-pkgs. The package radvd also gave me
> problems, although I don't recall why.

I'll look into removing those.

> I ended up re-rolling xs-config and
> xs-pkgs to exclude these above packages. F9 now installs the xs-config
> package, with one problem, the symlinks in /etc/rc.d/rc1.d/ 23456... don't
> get created, looks like those need to be copied over also with F9.

Ok.

> Some
> other links were installed as "file".olpcnew. also. I'll put together a list
> later if you want it.

Interesting. Short term plan is to fix it promptly. Long term plan --
discussed with Wad this morn -- is to break xs-config into various
parts:

 - For daemons that accept a parameter pointing to the config file
(named for example) we should disable the daemon permanently via
chkconfig and install an alternative init script (named-olpc) which
points to a different config file (/etc/named-olpc.conf).

 - For files where we want to search/replace values (as we do with
domain_config_ we should ship a template file
(/etc/named-olpc.conf.in) with placeholders (@@BASEDOMAIN@@). So
domain_config gets simplified a lot and becomes more reliable too.

 - We prefer conf.d arrangements where possible - and in those cases,
avoid the symlink mess.

 - For actually hardcoded-name files we need to override (ie:
/etc/rssh.conf) we can use a version-control scheme (git based
probably).

 - And dismantle the symlink mess we have...

cheers,


m
-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff