| 1 |
Le Wed, 7 Jun 2006 17:26:44 +0200, |
| 2 |
Maik Musall <lists@××××××.de> a =C3=A9crit : |
| 3 |
|
| 4 |
> Hello, |
| 5 |
>=20 |
| 6 |
> I find it difficult to minimize service downtime for things like apache |
| 7 |
> when the package is to be updated. If I stop the service before |
| 8 |
> emerging, downtime is longer than necessary since during the compile |
| 9 |
> stage it could stay running. On the other hand, when I don't stop the |
| 10 |
> service before emerge exchanges the binaries, things can become unstable |
| 11 |
> (initscripts reporting service running but it isn't, or vice versa, |
| 12 |
> segfaulting running binaries...). |
| 13 |
|
| 14 |
I have never seen such problems :\ |
| 15 |
|
| 16 |
|
| 17 |
>=20 |
| 18 |
> Ideal would be an emerge option that asks back for confirmation just |
| 19 |
> before exchanging files. But that doesn't seem to exist. |
| 20 |
>=20 |
| 21 |
> How do you handle this problem? |
| 22 |
|
| 23 |
I don't have this problem, so I don't have to handle it. But I have an idea |
| 24 |
for you.. You may want to do a=20 |
| 25 |
|
| 26 |
man emerge |
| 27 |
|
| 28 |
and have a look at the options : |
| 29 |
|
| 30 |
--buildpkgonly (-B) |
| 31 |
--usepkg (-k) |
| 32 |
|
| 33 |
The first one allow you to create a package which won't be installed, |
| 34 |
the second one will install using a package (and if none exist, |
| 35 |
it will compile). Using the first command, you will compile it, and when |
| 36 |
you're ready to update apache, you just have to stop it, emerge your |
| 37 |
package and then you may start the service again. |
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
>=20 |
| 42 |
> Thanks |
| 43 |
|
| 44 |
no problem ;) |
| 45 |
-- |
| 46 |
gentoo-server@g.o mailing list |
Archives