Le Wed, 7 Jun 2006 17:26:44 +0200, Maik Musall <[EMAIL PROTECTED]> a =C3=A9crit :
> Hello, >=20 > I find it difficult to minimize service downtime for things like apache > when the package is to be updated. If I stop the service before > emerging, downtime is longer than necessary since during the compile > stage it could stay running. On the other hand, when I don't stop the > service before emerge exchanges the binaries, things can become unstable > (initscripts reporting service running but it isn't, or vice versa, > segfaulting running binaries...). I have never seen such problems :\ >=20 > Ideal would be an emerge option that asks back for confirmation just > before exchanging files. But that doesn't seem to exist. >=20 > How do you handle this problem? I don't have this problem, so I don't have to handle it. But I have an idea for you.. You may want to do a=20 man emerge and have a look at the options : --buildpkgonly (-B) --usepkg (-k) The first one allow you to create a package which won't be installed, the second one will install using a package (and if none exist, it will compile). Using the first command, you will compile it, and when you're ready to update apache, you just have to stop it, emerge your package and then you may start the service again. >=20 > Thanks no problem ;) -- [email protected] mailing list
