1 |
The init file for apache 1.3 has a reload function that is exactly the same as |
2 |
apachectl graceful aka kill -USR1. So /etc/init.d/apache reload is the same |
3 |
as apachectl graceful |
4 |
|
5 |
Phil |
6 |
|
7 |
On Wednesday 17 August 2005 21:15, Jeroen Geilman wrote: |
8 |
|
9 |
> No, that's definitely NOT what he is after - since you are adding new |
10 |
> vhosts these will never be involved in any ongoing transfers. |
11 |
> Instead, reload will break off all current transfers - not a good idea |
12 |
> on a heavily loaded server. |
13 |
> Graceful is fine. |
14 |
|
15 |
> > Michael Crute wrote: |
16 |
> > |
17 |
> > The gaceful command will actually cause apache to restart but only |
18 |
> > after all pending transfers complete. I believe that this is the |
19 |
> > default behavior of /etc/init.d/apache2 restart the command you are |
20 |
> > looking for is reload. |
21 |
|
22 |
> Top-posting corrected. |
23 |
> |
24 |
> > On 8/17/05, *A. Khattri* <ajai@××××.net <mailto:ajai@××××.net>> wrote: |
25 |
> > |
26 |
> > On Tue, 16 Aug 2005, Ian P. Christian wrote: |
27 |
> > > On Tuesday 16 August 2005 13:01, Darko Luketic wrote: |
28 |
> > > > and imho thats not really the way it should be, apache should |
29 |
> > |
30 |
> > be restarted |
31 |
> > |
32 |
> > > > once a day not potentially every 15 minutes. |
33 |
> > > |
34 |
> > > I don't see why it should be restarted at all. If you're not |
35 |
> > |
36 |
> > binding to any |
37 |
> > |
38 |
> > > new ports, a reload should be fine rather then a restart. |
39 |
> > |
40 |
> > Just curious: would "apachectl graceful" load new vhosts added |
41 |
> > since the |
42 |
> > last restart? |
43 |
> > |
44 |
> > |
45 |
> > -- |
46 |
> > |
47 |
> > -- |
48 |
> > gentoo-server@g.o <mailto:gentoo-server@g.o> mailing |
49 |
> > list |
50 |
> > |
51 |
|
52 |
> |
53 |
|
54 |
-- |
55 |
gentoo-server@g.o mailing list |