Re: Looking for 'ideal' web-server partitions
Kiffin Gish wrote: I want to create a web server for a few personal web sites (virtual named hosts) using Apache, Perl, PHP and MySQL. Maybe later using mod_perl and ssl. No mail servers or other complicated stuff, just a plain-vanilla web server for the general public and an average visitor traffic of below 1000 per day. I have 40G to use up on an AMD Sempron 1300+ with 512MB and was just wondering what would be a good way to divvy up the partitions. I was thinking something like this: SWAP 1024M / 1057M /db 6.3G /usr 24G /var 4.2G /www 42G I've heard arguments for and against a separate /db and/or /tmp partition as well as using a /home. Also I see that there is a /usr/local/www directory already so perhaps the /www partition is not required. Is a separate /db partition really needed? I'm pretty confused and would like to setup my web server the right way once and for all. Are there any standard recipes and/or guides to figuring this out or is it just a bunch of guess work? How does this look? If I could make one quick suggestion, I would urge you to attempt to mount you various partitions in more standard locations. For example, instead of mounting your db partition at /db, why not mount it at /var/db? And instead of mounting your www partition at /www, how about at /var/www, or the FreeBSD standard of /usr/local/www? Having these specific directories represent a separate filesystem is fine, and perhaps desirable, but having them all mounted on root makes for a less standard filesystem layout, which in general is not a good thing. Nathan pgp3XenDFW0A2.pgp Description: PGP signature
Looking for 'ideal' web-server partitions
I want to create a web server for a few personal web sites (virtual named hosts) using Apache, Perl, PHP and MySQL. Maybe later using mod_perl and ssl. No mail servers or other complicated stuff, just a plain-vanilla web server for the general public and an average visitor traffic of below 1000 per day. I have 40G to use up on an AMD Sempron 1300+ with 512MB and was just wondering what would be a good way to divvy up the partitions. I was thinking something like this: SWAP1024M / 1057M /db 6.3G /usr24G /var4.2G /www42G I've heard arguments for and against a separate /db and/or /tmp partition as well as using a /home. Also I see that there is a /usr/local/www directory already so perhaps the /www partition is not required. Is a separate /db partition really needed? I'm pretty confused and would like to setup my web server the right way once and for all. Are there any standard recipes and/or guides to figuring this out or is it just a bunch of guess work? How does this look? -- Kiffin Rex Gish Gouda, The Netherlands ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Looking for 'ideal' web-server partitions
Kiffin Gish wrote: I want to create a web server for a few personal web sites (virtual named hosts) using Apache, Perl, PHP and MySQL. Maybe later using mod_perl and ssl. No mail servers or other complicated stuff, just a plain-vanilla web server for the general public and an average visitor traffic of below 1000 per day. I have 40G to use up on an AMD Sempron 1300+ with 512MB and was just wondering what would be a good way to divvy up the partitions. I was thinking something like this: SWAP1024M / 1057M /db 6.3G /usr24G /var4.2G /www42G I've heard arguments for and against a separate /db and/or /tmp partition as well as using a /home. Also I see that there is a /usr/local/www directory already so perhaps the /www partition is not required. Is a separate /db partition really needed? I'm pretty confused and would like to setup my web server the right way once and for all. Are there any standard recipes and/or guides to figuring this out or is it just a bunch of guess work? How does this look? I'm not even sure what exactly you would put on a /db partition, would this be like /var/db? and /usr/local/www/data is the default DocumentRoot for apache. This can all be changed. Here is my take of your configuration. A) / is WAY too big. I generally allocate about 200M for /, if you are planning on not separating /tmp. Make it slightly larger, say 500M. B) again, im not sure what you are trying to accomplish with /db C) 4G for /var is pretty generous. I run a medium size webserver, and my /var is only 2G. D) separating /www isnt really nescessary, though theres really no downside to this. Here would be my partitioning sceme. 1024M - SWAP 300M - / 2G - /var the rest - /usr linking /tmp to /usr/tmp is generally a good idea in my book. Hope this helps. Regards, Frank Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Looking for 'ideal' web-server partitions
Kiffin Gish wrote: I want to create a web server for a few personal web sites (virtual named hosts) using Apache, Perl, PHP and MySQL. Maybe later using mod_perl and ssl. No mail servers or other complicated stuff, just a plain-vanilla web server for the general public and an average visitor traffic of below 1000 per day. I have 40G to use up on an AMD Sempron 1300+ with 512MB and was just wondering what would be a good way to divvy up the partitions. I was thinking something like this: SWAP 1024M /1057M /db 6.3G /usr 24G /var 4.2G /www 42G I've heard arguments for and against a separate /db and/or /tmp partition as well as using a /home. Also I see that there is a /usr/local/www directory already so perhaps the /www partition is not required. Is a separate /db partition really needed? I'm pretty confused and would like to setup my web server the right way once and for all. Are there any standard recipes and/or guides to figuring this out or is it just a bunch of guess work? How does this look? I'm not even sure what exactly you would put on a /db partition, would this be like /var/db? and /usr/local/www/data is the default DocumentRoot for apache. This can all be changed. Here is my take of your configuration. A) / is WAY too big. I generally allocate about 200M for /, if you are planning on not separating /tmp. Make it slightly larger, say 500M. B) again, im not sure what you are trying to accomplish with /db C) 4G for /var is pretty generous. I run a medium size webserver, and my /var is only 2G. D) separating /www isnt really nescessary, though theres really no downside to this. Unless something unusual is in /, then, yes it is too big, especially since /usr and /var is split out - though I don't see a /tmp. I would make that a separate partition also to reduce problems of filling it up and in the process overfilling wherever it is at. But, there is no problem with making a /db if you want to isolate your database stuff. If you do, then you can reduce /var to 2 gb, but if you leave all your database stuff in /var/db, then /var may need to be bigger - depends on how much you put there. Isolating /www is OK or not needed depending on what you put there and how much it changes - grows, it can be a good idea or just an extra bother. I generally make a large catchall partition and put all those things that change a lot and grow - database, spool, usr/local, etc in it with appropriate symbolic links. jerry Here would be my partitioning sceme. 1024M - SWAP 300M - / 2G - /var the rest - /usr linking /tmp to /usr/tmp is generally a good idea in my book. Hope this helps. Regards, Frank Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Looking for 'ideal' web-server partitions
On Tue, 28 Dec 2004 22:33:04 +0100, Kiffin Gish [EMAIL PROTECTED] wrote: I want to create a web server for a few personal web sites (virtual named hosts) using Apache, Perl, PHP and MySQL. Maybe later using mod_perl and ssl. No mail servers or other complicated stuff, just a plain-vanilla web server for the general public and an average visitor traffic of below 1000 per day. I have 40G to use up on an AMD Sempron 1300+ with 512MB and was just wondering what would be a good way to divvy up the partitions. I was thinking something like this: SWAP1024M / 1057M /db 6.3G /usr24G /var4.2G /www42G I've heard arguments for and against a separate /db and/or /tmp partition as well as using a /home. Also I see that there is a /usr/local/www directory already so perhaps the /www partition is not required. Is a separate /db partition really needed? I'm pretty confused and would like to setup my web server the right way once and for all. Are there any standard recipes and/or guides to figuring this out or is it just a bunch of guess work? How does this look? A root partition of 128M ought to be just fine, though you may want to put /tmp on a slice of its own. It looks like you plan to put databases and htdocs on slices of their own as well, so /var can be much smaller; I generally use a 256M /var slice, and have had no problems with space for logging. 24GB is a nice, fat /usr slice. You could easily trim that back, since again, it appears you plan to store db and www on unique slices. Maybe something like: SWAP 1024M / 128M /tmp 256M /var256M /usr10G (?) /dbwhatever size you like /www whatever size you like HTH, -- Joshua Lokken Open Source Advocate ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Looking for 'ideal' web-server partitions
Without passing on your numbers here are some reason to partition: var - A good idea, I think, especially with apache. It keeps a nimba style dOs from filling your disk. / - Without a var partition I believe var is in '/' and not user. /var/log, var/mail, var/spool/mqueue can grow. Your var size seems reasonable to me. /etc/named can grow if you run named. This is only an issue if you make / as small as possible. Note 5.x needs more space than 4.x which needed more than 3.x and we have 6.x as the new current. Its really hard to resize '/' without starting over. You can of course symlink out all of the stuff mentioned. I would make '/' 2 times the current recommendation. swap - Some people use mfs for /tmp. Remember to add the size to swap if you do that. data - Separating data from /usr makes upgrading easier. Requirements on /usr have probably grown, maybe as much as for '/'. I also assume you have a db partition for MySQL. A reason you may want that as a separate partition would be to use the 5.x file system snapshot which might make taking live backups possible. At least you could minimize the length of the down. You could backup the DB on a different cycle and frequency from www. I think good arguments can be made for combining the db and www partitions. For example, if you undersize the db partition you would lose all those advantages. I am not sure if innoDB allows for live backups. If it does and you needed that I would use innoDB and one partition. On my main work station I took the 4.x defaults of: /dev/ad0s2a 62M45M13M78%/ /dev/ad0s2f 14G 7.8G 5.0G61%/usr /dev/ad0s2e 62M17M40M29%/var procfs 4.0K 4.0K 0B 100%/proc and I wish I had made a data partition which would make going to 5.3 a whole bunch easier. All my servers have a data partition. On my laptop I take the autoconfig and just start fresh when going to FreeBSD [n+1].0. I hope this helps On Tue, 28 Dec 2004, Frank J. Laszlo wrote: Kiffin Gish wrote: I want to create a web server for a few personal web sites (virtual named hosts) using Apache, Perl, PHP and MySQL. Maybe later using mod_perl and ssl. No mail servers or other complicated stuff, just a plain-vanilla web server for the general public and an average visitor traffic of below 1000 per day. I have 40G to use up on an AMD Sempron 1300+ with 512MB and was just wondering what would be a good way to divvy up the partitions. I was thinking something like this: SWAP 1024M /1057M /db 6.3G /usr 24G /var 4.2G /www 42G I've heard arguments for and against a separate /db and/or /tmp partition as well as using a /home. Also I see that there is a /usr/local/www directory already so perhaps the /www partition is not required. Is a separate /db partition really needed? I'm pretty confused and would like to setup my web server the right way once and for all. Are there any standard recipes and/or guides to figuring this out or is it just a bunch of guess work? How does this look? I'm not even sure what exactly you would put on a /db partition, would this be like /var/db? and /usr/local/www/data is the default DocumentRoot for apache. This can all be changed. Here is my take of your configuration. A) / is WAY too big. I generally allocate about 200M for /, if you are planning on not separating /tmp. Make it slightly larger, say 500M. B) again, im not sure what you are trying to accomplish with /db C) 4G for /var is pretty generous. I run a medium size webserver, and my /var is only 2G. D) separating /www isnt really nescessary, though theres really no downside to this. Here would be my partitioning sceme. 1024M - SWAP 300M - / 2G - /var the rest - /usr linking /tmp to /usr/tmp is generally a good idea in my book. Hope this helps. Regards, Frank Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] _ Douglas Denault http://www.safeport.com [EMAIL PROTECTED] Voice: 301-469-8766 Fax: 301-469-0601 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
