Ubuntu+eBox status

[Javier Uruen Val]

Hi again.

[...]
> That's a rather big change, as apache 1.3 is no longer shipped since
> Gutsy. Did you invest some time to figure out what was wrong with the
> apache2 setup ?

After tweaking a little bit the thread configuration in apache2, the memory 
footprint has decreased and it's closer to apache 1.3.

I had to fix an issue related to the process signal mask. As we start/stop 
services within apache2 doing /etc/init.d/foo or start bar, the new spawned 
process  inherits the apache2 process singal mask which blocks some signals 
like SIGTERM. Most of the services clear their signal mask properly, but 
others  don't. The result was that we couldn't stop some services because 
they were ignoring some signals. This is fixed too by clearing the signal 
mask before starting a process.

So we are using apache2 again.

>
> > There are a couple more of perl modules we have packaged:
> > libnet-cups-perl-0.55 and libtree-perl-1.0.
>
> You should submit them for inclusion in universe ASAP.

I've already uploaded them to REVU


[..]
> > Another approach is detecting if the file which is going to be
> > overwritten has been modified by the user, in that case the user would be
> > informed and prompted to confirm changes or cancel. I guess that should
> > be the way to go with every single configuration file overwritten by eBox
> > from other packages.
>
> I think this is the right approach. Including a merging tool is not the
> most important thing and can be added later. At least local
> modifications should be detected, the user warned and asked about what
> should be done (overwrite or cancel).

I'm already working on this.