I am setting up a new Apache server on Linux. I am wondering what
partition scheme I should go with. This will be just a webserver. I
read recently that you should give certain directories their own
partitions. What partitions are the most important ones for Apache?

Jerim79 wrote:
> I am setting up a new Apache server on Linux. I am wondering what
> partition scheme I should go with. This will be just a webserver. I
> read recently that you should give certain directories their own
> partitions. What partitions are the most important ones for Apache?
>

In my experience, you want to be careful where you put Apache's log
files. Someone hitting your server hard can cause rapid growth in the
log files. Better to fill a partition other than the root partition.

Jim

"Jerim79" <mylek@hotmail.com> wrote in message
news:1159973376.707327.94890@i3g2000cwc.googlegrou ps.com...
>I am setting up a new Apache server on Linux. I am wondering what
> partition scheme I should go with. This will be just a webserver. I
> read recently that you should give certain directories their own
> partitions. What partitions are the most important ones for Apache?
>
My first question would be - what is you experience with Linux?

If you are experienced, I would suggest that your web-root be on its own
partition, and that you make the size for your /var partition reasonable for
the logs, and that is a function of the traffic you expect. Generally apache
rotates the logs monthly, so they can get quite big.

If you are new to linux, then I suggest you try mandrake/mandriva, which is
what I use.
/ can be about 10 gigs
/home about 10
/etc about 10
/var 5 to 10
/web all the rest
I happened to have a 250 gig drive free for this application, so my web
server has 200 gig of free space right now.


This departs from the tradition of not adding to the 'root'. All 'growable'
things should be in /var along with all the logs, but I do not like that.

The logs go to /var/log/httpd If the logs run wild, as mine did once, you
get your warnings that the /var partition is full, but no data is lost. If
your web root were there too, you might loose things or you might not find
out about the problems until way too late. Runaway logs files often indicate
a configuration error - like accidentally having an open proxy.

Ask if you would like more detail.

Stuart

"Jerim79" <mylek@hotmail.com> wrote in message
news:1159973376.707327.94890@i3g2000cwc.googlegrou ps.com...
>I am setting up a new Apache server on Linux. I am wondering what
> partition scheme I should go with. This will be just a webserver. I
> read recently that you should give certain directories their own
> partitions. What partitions are the most important ones for Apache?
>
My first question would be - what is you experience with Linux?

If you are experienced, I would suggest that your web-root be on its own
partition, and that you make the size for your /var partition reasonable for
the logs, and that is a function of the traffic you expect. Generally apache
rotates the logs monthly, so they can get quite big.

If you are new to linux, then I suggest you try mandrake/mandriva, which is
what I use.
/ can be about 10 gigs
/home about 10
/etc about 10
/var 5 to 10
/web all the rest
I happened to have a 250 gig drive free for this application, so my web
server has 200 gig of free space right now.


This departs from the tradition of not adding to the 'root'. All 'growable'
things should be in /var along with all the logs, but I do not like that.

The logs go to /var/log/httpd If the logs run wild, as mine did once, you
get your warnings that the /var partition is full, but no data is lost. If
your web root were there too, you might loose things or you might not find
out about the problems until way too late. Runaway logs files often indicate
a configuration error - like accidentally having an open proxy.

Ask if you would like more detail.

Stuart