Re: apache log files
Instead of setting ulimit in an init script, you can set it in the file /etc/security/limits.conf like this: www-data hardnofile 4096 www-data softnofile 8192 I'm not sure what hard and soft really mean, they're discribed as: #type can have the two values: #- soft for enforcing the soft limits #- hard for enforcing hard limits but I don't know what kind of a difference they make. /proc/sys/fs/file-max is 26214 on that system, I'm not sure if it's influenced by the contents of limits.conf ... On another system it's even higher though I've not changed anything. Anybody knows what changes this value? Sönke Am Mittwoch, 3. November 2004 23:42 schrieb Craig Sanders: On Wed, Nov 03, 2004 at 11:11:13PM +0100, Marek Podmaka wrote: I have apache 1.3 webserver hosting about 150 domains (more than 400 virtual hosts). Now I have separate error log for each domain (something.sk) and separate combined log for each virtual host (for example www.abcq.sk and new.abcq.sk). This has many positives for me: easy to find some data related to each virtual host and that I can make seaparate statistics for each virtual host. I use awstats. And now the bad side - the number of open files in each apache process is more than 500 just for these log files. It's no problem for now, but with more domains in future it will hit the 1024 per process limit of open files. And now the questions :) 1) Where does that 1024 open files limit come from? Is it somewhere configurable? edit /etc/init.d/apache and add a line like ulimit -n 4096 -n is the maximum number of open file descriptors per process. use a value that's about twice as much as you think you'll need. you also need to set /proc/sys/fs/file-max to some suitably high value (again, calculate how many you think you'll need and double it). this can be set in /etc/sysctl.conf Or do you think it's totally bad idea to have such number of log files? until recently, i ran a web server with about 600 virtual hosts on it, each with its own access.log and error.log files. with 200 max apache children, that worked out as up to about 240,000 (600 x 200 x 2) file handles opened by apache processes for logging at any given time. this was on a dual p3-866 with 512MB RAM. it worked. it bothered me a little that it wasn't really scalable and that eventually i'd have to do something about logging. i had some ideas on what to do, but was limited by the fact that i wanted to have separate error.log files for each virtual host. overall, though, my attitude was it aint broke, so don't fix it. this wouldn't be a problem if apache could be configured to prefix each error.log line with the virtual host's domain name..then you could have a single pipe to an error logging script which wrote the error lines to the right file, same as you can do for the access.log. but apache can't be configured to do that, and i never bothered looking at the source to see how easy it would be to hack it in, so that means you either have a shared error.log for all vhosts or you put up with having lots of open file handles. i chose the latter, and occasionally increased both ulimit -n and /proc/sys/fs/file-max as requiredi never did run into any limit. craig -- craig sanders [EMAIL PROTECTED] (part time cyborg) -- Sönke von Stamm System Administration [EMAIL PROTECTED] Tel.: +49 511 - 35 77 19 - 29 Fax.: +49 511 - 35 77 19 - 19 Imedia Gesellschaft für neue Medien mbH Limmerstr. 46 | 30451 Hannover
Re: PHP4-gd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 just try php4-gd2 =:) yours, Sönke Am Mittwoch, 24. April 2002 10:04 schrieb Craig: Hi Could someone please tell me how to enable jpeg support using the php4-gd package. Kind regards Craig :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjzGi4gACgkQtWXOsFK9NM5lVgCdEDH6xU4DlUICsuc8E6Q8zTtx SgEAniga7TuocswtBvsxj2nQiSNjSaED =2EQU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: where has htpasswd gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 oops found it. I had previously installed thttpd-util just to get that thtpasswd which does nearly the same of course. Had to uninstall that in dselect-upgrade yesterday (dependencypulled in unwanted thttpd) and since then I indeed have /usr/bin/htpasswd. Must have come with the updated apache-common. Strange. thanks anyway Sönke Am Donnerstag, 14. März 2002 18:13 schrieb Eric LeBlanc: On Thu, 14 Mar 2002, Soenke von Stamm wrote: can't find it in woody anymore =8( anyone knows if it's installable somwhere in a woody deb? Found Nothing with apt-cache and thelike. thanks in advance, rick@ikaluk:~$ zgrep htpasswd Contents-i386.gz usr/bin/htpasswd web/apache-common in package apache-common. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyRsnYACgkQtWXOsFK9NM5bxQCgoxEjgwaJyqQuiyyBkzBihuFh T34AoIya3zd7xpflVkjKDenrvYZPPQ2j =ILex -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
where has htpasswd gone?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 can't find it in woody anymore =8( anyone knows if it's installable somwhere in a woody deb? Found Nothing with apt-cache and thelike. thanks in advance, Sönke -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyQvMQACgkQtWXOsFK9NM5ILgCggmgelCcKm7VFAtNZzskQzHdt UkcAoL05iG4guuqaZHesTu8rqb+r7gyL =mZ3S -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem with the installation of imp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Werner, 1) - a. Apache c. Apache-SSL b. Both o. Other What type of Web Server are you running? [a] - wrong: you chose apache-ssl 2) - # LoadModule php3_module /usr/lib/apache/1.3/libphp3.so - remove the comment (#) in /etc/apache-ssl/httpd.conf 3) - Restart Apache-SSL now? [Y/n] Y apache-ssl: cannot determine local host name. Use the ServerName directive to set it manually. /usr/sbin/apache-sslctl start: httpd could not be started - set the ServerName and restart apache-ssl 4) re-run apt-get install imp or use dpkg --configure --pending maybe you'll have to reconfigure (see 1)) horde/imp, safest (to me) is apt-get --purge remove horde imp; apt-get install horde imp good luck, Sönke Am Freitag, 1. März 2002 17:34 schrieb Werner De Kuyffer: Hi, Attached you find a copy of the output of the installation process of imp. Can someone help me with the error that occurred? Thanks, Werner -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjyDizoACgkQUHsyYAmAYTWiXACfVBXtoIw8J/Lo82ZUyOh86ZTp eJEAn3AgVHMxaygx3U+2NcyAfQ3nhDbG =GWv4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with Duron Procesor
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 if i get it straight there is/was an issue with durons/athlons running on via kt chipsets and k7 optimized kernels: the optimization uses some 3dnow+ code for faster memory access which leads to - well - unwanted effets. I read this somewhere in german c't, can't find it now. maybe try a k6 or pII/III optimezed kernel yours Sönke Am Sonntag, 16. Dezember 2001 00:37 schrieb [EMAIL PROTECTED]: Hello! We bought a Clone with a 950k, AMD-Duron Processor, Motherboard by Biostar to build an Intranet Server out of it. When installing a new Kernel (2.4.7), compiled for this processortype the machine stopped to work, because of severe Memory fault problems, reducing the access speed from 133 Mhz to 100 Mhz reduces the problem significatively Using a plain Pentium kernel we got no memory faults anymore. Is this a Motherboard/Memory problem, or is there any known problem with the AMD-Duron optimization? gcc-version: 2.95.4 20010902 (Debian prerelease) Thanks, Jorge-León -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwgoAoACgkQUHsyYAmAYTUQjQCfZ4jthTJ9nYVSTL1CeOAxhk/E qz4An0ZgVXo8nkfyz6aCvX8m0w072b4I =+xbn -END PGP SIGNATURE-
