FreeBSDwiki - User contributions [en]

Apache, Configuring

2005-10-20T13:13:55Z

Baraboom: /* Prefork */

If you've got a busy webserver, you'll soon find yourself looking at tweaking the Apache configuration to get more. As it is, most Apache installs are configured for testing / development vs production use.

==MPM==

By default, the httpd.conf has MPM specific settings for all possible MPM choices. However, since this choice is made at compile-time, all but one of these MPM specific can be safely removed. The default (and usually the recommended) MPM is prefork.

##
## Server-Pool Size Regulation (MPM specific)
##

===Prefork===

This is the default MPM and will work fine for most applications.

Default:
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule prefork.c>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0
</IfModule>

Tweaked:
StartServers 10
MinSpareServers 10
MaxSpareServers 20
MaxClients 256
MaxRequestsPerChild 15000

'''StartServers, MinSpareServers, MaxSpareServers'''
Creating a child process can be one of the most expensive in terms of CPU usage. Experiment with raising these values... as a start, you can probably safely double them and go from there. During traffic spikes, the server will have more available, idle child processes already created, which should help reduce load and keep the server busier serving content than spawning new servers when needed.

'''MaxClients'''
With a busy website you may start reaching the default MaxClients, in which case everyone else is locked out. This error will show up in your error logs. Please note that there is a hard limit of 256 for this directive. Raising it requires setting a compile-time option and reinstalling. Still, 256 is much heftier than 150, so this may work out fine.

'''MaxRequestsPerChild'''
Leaving this at 0 means a child never dies... once its created it will serve an unlimited number of requests until the main daemon kills it off during traffic lulls. Setting this to a high number has the benefit of periodically refreshing the pool of child processes and keeping memory leakage to a minimum.

===Worker===

In order to try out the worker MPM, you must re-install Apache2 with different MAKE_ARGS. For the brave, please see this page: [[Apache2 with the Worker MPM]].

==KeepAlives==

The KeepAlives directive is enabled by default; to quote from the Apache documentation:
The Keep-Alive extension to HTTP/1.0 and the persistent connection feature of
HTTP/1.1 provide long-lived HTTP sessions which allow multiple requests to be
sent over the same TCP connection. In some cases this has been shown to result
in an almost 50% speedup in latency times for HTML documents with many images.

Which is a good thing, if you want fast pages and have a strong server to handle it. If you're more concerned with availability than speed, or are running Apache on a less-than-stellar machine, you may get better performance (cpu/processor-wise, at least,) by turning KeepAlives off:

Default:
KeepAlives On

Tweaked:
KeepAlives Off

Apache, Configuring

2005-10-20T13:11:19Z

Baraboom: /* Apache 2 Configuration */

If you've got a busy webserver, you'll soon find yourself looking at tweaking the Apache configuration to get more. As it is, most Apache installs are configured for testing / development vs production use.

==MPM==

By default, the httpd.conf has MPM specific settings for all possible MPM choices. However, since this choice is made at compile-time, all but one of these MPM specific can be safely removed. The default (and usually the recommended) MPM is prefork.

##
## Server-Pool Size Regulation (MPM specific)
##

===Prefork===

This is the default MPM and will work fine for most applications.

Default:
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule prefork.c>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0
</IfModule>

Tweaked:
StartServers 10
MinSpareServers 10
MaxSpareServers 20
MaxClients 250
MaxRequestsPerChild 15000

'''StartServers, MinSpareServers, MaxSpareServers'''
Creating a child process can be one of the most expensive in terms of CPU usage. Experiment with raising these values... as a start, you can probably safely double them and go from there. During traffic spikes, the server will have more available, idle child processes already created, which should help reduce load and keep the server busier serving content than spawning new servers when needed.

'''MaxClients'''
With a busy website you may start reaching the default MaxClients, in which case everyone else is locked out. This error will show up in your error logs. Please note that there is a hard limit of 256 for this directive. Raising it requires setting a compile-time option and reinstalling. Still, 256 is much heftier than 150, so this may work out fine.

'''MaxRequestsPerChild'''
Leaving this at 0 means a child never dies... once its created it will serve an unlimited number of requests until the main daemon kills it off during traffic lulls. Setting this to a high number has the added benefit of periodically refreshing the pool of child processes and keep memory leakage to a minimum.

===Worker===

In order to try out the worker MPM, you must re-install Apache2 with different MAKE_ARGS. For the brave, please see this page: [[Apache2 with the Worker MPM]].

==KeepAlives==

The KeepAlives directive is enabled by default; to quote from the Apache documentation:
The Keep-Alive extension to HTTP/1.0 and the persistent connection feature of
HTTP/1.1 provide long-lived HTTP sessions which allow multiple requests to be
sent over the same TCP connection. In some cases this has been shown to result
in an almost 50% speedup in latency times for HTML documents with many images.

Which is a good thing, if you want fast pages and have a strong server to handle it. If you're more concerned with availability than speed, or are running Apache on a less-than-stellar machine, you may get better performance (cpu/processor-wise, at least,) by turning KeepAlives off:

Default:
KeepAlives On

Tweaked:
KeepAlives Off

Apache2, Installing

2005-10-20T13:10:34Z

Baraboom:

'''Apache 2.0'''

See also [[Apache]] - [[Apache Controlling]] - [[Configuring Apache]]

We'll walk through the installation for Apache2. It's very simple to install - in earlier versions of Apache, you had to install either mods or different versions depending on whether you wanted to enable certain features (ssl, etc). With Apache2, they are incorporated into the main package, and enabled or disabled when you configure Apache. There are a few exceptions, but most everything you'll need to run a modern feature-rich webserver is included with the Apache2 port.

'''Note:''' As always, before installing any ports, update your ports tree with [[cvsup]] if it has been a while.

Let's get started:

>'''su'''
Password: (enter root password)
oyabun# '''cd /usr/ports/www'''
oyabun# '''ls | grep apache'''
apache-contrib
apache-forrest
apache-jserv
apache13
apache13+ipv6
apache13-fp
apache13-modperl
apache13-modssl
apache13-modssl+ipv6
apache13-ssl
apache2
mod_jk-apache2
mod_jk2-apache2
oyabun# '''cd apache2'''
oyabun# '''make install clean'''

First, I changed to the [[superuser]], as we'll be installing software. I changed directory to the '''www''' section of the ports tree, and filtered a listing of that directories contents for all ports that contained the word 'apache' using [[grep]]. The one we want is '''apache2'''. I then changed to that directory, and issued the [[make]] command, with options '''install''' and '''clean''' specified, to install the software and clean up the makefiles when done.

Note that you'll want to check the file /usr/ports/www/apache2/Makefile.doc to see what modules you can build into apache2 -- e.g., [[LDAP]] or [[IPv6]] or threading. To include the one you want, you'd want to build apache like so:

samizdata# '''make -DWITH_LDAP_MODULE install clean

After a few seconds, minutes, or hours (depending on whether your hardware is going to waste, reasonable, or a throwback to the early 90's), Apache2's installation will be completed, and you'll be faced with this note:

Available variables you add/set to /etc/rc.conf.
- apache2_enable (bool): Set to "NO" by default.
Set it to "YES" to enable apache2.
- apache2ssl_enable (bool): Set to "NO" by default.
Set it to "YES" to start apache with SSL
(if <IfDefined SSL> exists in httpd.conf).
- apache2limits_enable (bool):Set to "NO" by default.
Set it to yes to run `limits $limits_args`
just before apache starts.
- apache2_flags (str): Set to "" by default.
Extra flags passed to start command.
- apache2limits_args (str): Default to "-e -C daemon"
Arguments of pre-start limits run.

As you can see from this, ssl suport is included in Apache2, as opposed to Apache 1.3. I included this output because I have a bad habit of scrolling important stuff like this out of the buffer after installations, and it's nice to have it saved here. You don't need to worry about any of this until you configure Apache.

So, Apache2 is now installed, you just need to actually set it up.

Please visit [[Apache Controlling]] to learn how to actually start your webserver.
[[Category:Common Tasks]]

[[Category:FreeBSD for Servers]]

Apache, Configuring

2005-10-20T13:04:56Z

Baraboom: /* Prefork */

==Apache 2 Configuration==

If you've got a busy webserver, you'll soon find yourself looking at tweaking the Apache configuration to get more. As it is, most Apache installs are configured for testing / development vs production use.

==MPM==

By default, the httpd.conf has MPM specific settings for all possible MPM choices. However, since this choice is made at compile-time, all but one of these MPM specific can be safely removed. The default (and usually the recommended) MPM is prefork.

##
## Server-Pool Size Regulation (MPM specific)
##

===Prefork===

This is the default MPM and will work fine for most applications.

Default:
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule prefork.c>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0
</IfModule>

Tweaked:
StartServers 10
MinSpareServers 10
MaxSpareServers 20
MaxClients 250
MaxRequestsPerChild 15000

'''StartServers, MinSpareServers, MaxSpareServers'''
Creating a child process can be one of the most expensive in terms of CPU usage. Experiment with raising these values... as a start, you can probably safely double them and go from there. During traffic spikes, the server will have more available, idle child processes already created, which should help reduce load and keep the server busier serving content than spawning new servers when needed.

'''MaxClients'''
With a busy website you may start reaching the default MaxClients, in which case everyone else is locked out. This error will show up in your error logs. Please note that there is a hard limit of 256 for this directive. Raising it requires setting a compile-time option and reinstalling. Still, 256 is much heftier than 150, so this may work out fine.

'''MaxRequestsPerChild'''
Leaving this at 0 means a child never dies... once its created it will serve an unlimited number of requests until the main daemon kills it off during traffic lulls. Setting this to a high number has the added benefit of periodically refreshing the pool of child processes and keep memory leakage to a minimum.

===Worker===

In order to try out the worker MPM, you must re-install Apache2 with different MAKE_ARGS. For the brave, please see this page: [[Apache2 with the Worker MPM]].

==KeepAlives==

The KeepAlives directive is enabled by default; to quote from the Apache documentation:
The Keep-Alive extension to HTTP/1.0 and the persistent connection feature of
HTTP/1.1 provide long-lived HTTP sessions which allow multiple requests to be
sent over the same TCP connection. In some cases this has been shown to result
in an almost 50% speedup in latency times for HTML documents with many images.

Which is a good thing, if you want fast pages and have a strong server to handle it. If you're more concerned with availability than speed, or are running Apache on a less-than-stellar machine, you may get better performance (cpu/processor-wise, at least,) by turning KeepAlives off:

Default:
KeepAlives On

Tweaked:
KeepAlives Off

Apache, Configuring

2005-10-20T12:54:45Z

Baraboom: /* MPM */

==Apache 2 Configuration==

If you've got a busy webserver, you'll soon find yourself looking at tweaking the Apache configuration to get more. As it is, most Apache installs are configured for testing / development vs production use.

==MPM==

By default, the httpd.conf has MPM specific settings for all possible MPM choices. However, since this choice is made at compile-time, all but one of these MPM specific can be safely removed. The default (and usually the recommended) MPM is prefork.

##
## Server-Pool Size Regulation (MPM specific)
##

===Prefork===

This is the default MPM and will work fine for most applications.

Default:
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule prefork.c>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0
</IfModule>

Tweaked:
StartServers 10
MinSpareServers 10
MaxSpareServers 20
MaxClients 250
MaxRequestsPerChild 15000

StartServers,
Creating a child process can be one of the most expensive in terms of CPU usage. With a busy website you may start reaching the default MaxClients, in which case everyone else is locked out. This error will show up in your error logs.

===Worker===

In order to try out the worker MPM, you must re-install Apache2 with different MAKE_ARGS. For the brave, please see this page: [[Apache2 with the Worker MPM]].

==KeepAlives==

The KeepAlives directive is enabled by default; to quote from the Apache documentation:
The Keep-Alive extension to HTTP/1.0 and the persistent connection feature of
HTTP/1.1 provide long-lived HTTP sessions which allow multiple requests to be
sent over the same TCP connection. In some cases this has been shown to result
in an almost 50% speedup in latency times for HTML documents with many images.

Which is a good thing, if you want fast pages and have a strong server to handle it. If you're more concerned with availability than speed, or are running Apache on a less-than-stellar machine, you may get better performance (cpu/processor-wise, at least,) by turning KeepAlives off:

Default:
KeepAlives On

Tweaked:
KeepAlives Off

Apache, Configuring

2005-10-20T12:49:57Z

Baraboom:

Talk:Apache, Configuring

2005-10-16T11:56:02Z

Baraboom:

Seeing as how this page was blank before, I can't say you did wrong to it but this entry is pretty useless, Barroom. Thanks for the newsyslog.conf entry though.

--[[User:Dave|Dave]] 20:11, 15 Oct 2005 (EDT)

hehe yea i typed that and ran out of steam for the day... but I have added a bit more text to the page, maybe get some other people adding / improving upon it. apache configuration covers quite a range of stuff... what i'd like to do is get some information goin about worker mpm, mod_fastcgi, php - any suggestions on how to organize it in here?

Apache, Configuring

2005-10-16T11:52:02Z

Baraboom:

Sudo, configuring

2005-10-16T11:47:22Z

Baraboom:

First, install [[sudo]]. [[su]] to root and go to /usr/ports and then find out where the port is:

[dave]@deus ~ % sudo
-bash: sudo: command not found
[dave]@deus ~ % su -
Password:
[root]@deus ~ # cd /usr/ports && make search name=sudo
Port: sudo-1.6.7.5
Path: /usr/ports/security/sudo
Info: Allow others to run commands as root
Maint: mharo@FreeBSD.org
B-deps:
R-deps:

[root]@deus /usr/ports # cd security/sudo
[root]@deus /usr/ports/security/sudo # make install clean

Once it's installed, you'll need to run [[visudo]] since there's no other way to edit /etc/sudoers (well, you can use another editor, but it just won't work.)

Note that [[visudo]] doesn't actually call the [[vi]] editor, just your default editor; if that ''happens'' to be [[vi]] then it will come up. Otherwise, your regular editor will come up.

/etc/sudoers has one entry in it:
root ALL=ALL(ALL) ALL
which doesn't really explain what those ALLs mean in context; so often a lot of folks will set the sudoers to give ALL=ALL(ALL) ALL to every user they add. That's nice, but you're giving all of root's power away. You might as well give users the root password and save them the hassle of using [[sudo]] at all.

The explanation:
sudo-user machine=(effective user rights) command

So, if I want to give Jimbo [[root]] access on my server, Pete root on my laptop and Light only to have access to [[shutdown]] on all my machines, my sudoers would look like:
root ALL=ALL(ALL) ALL
jimbo ALL=samizdata.mydomain.tld(ALL) ALL
peet ALL=deus(ALL) ALL
light ALL=ALL(ALL) /sbin/shutdown

Finally, if you just want to give yourself [[root]] access on your server via sudo with no password, your sudoers might look like:
root ALL=ALL(ALL) ALL
yourself ALL=(ALL) NOPASSWD: ALL

'''NOTE:''' remember that setting sudo rights for multiple machines in a single '''sudoers''' file is only meaningful if that file is actually shared or distributed across those multiple machines. Simply writing permissions for the machine samizdata ''on'' the machine deus isn't going to do anything useful by itself. You would need to copy the file contents over to all the machines that are listed (and then [[kill]] -HUP the sudo process, if it's running,) in order to make the changes meaningful.

==Using Aliases to make life easier==

You can make groups within the sudoers file so that you don't have to type more than you need to. Follow this format:

'''User_Alias''' allows you to define a group of users
'''Runas_Alias''' allows you to define the daemon or user the command can run as
'''Host_Alias''' allows you to define a group of hosts
'''Cmnd_Alias''' allows you to define which commands (full path '''must''' be given) are in a group

You ''can'' use already existing system groups, but you have to add the prefix % (e.g., %wheel)

As an example, if my /etc/sudoers showed:

User_Alias ADMINS=jimbo
User_Alias DNSADMINS=peet
User_Alias DHCPADMINS=light

Runas_Alias DAEMONS=bind,dhcpd,sshd

Host_Alias NAMESERVERS=ns1.samizdata.mydomain.tld,ns2.samizdata.mydomain.tld
Host_Alias DHCPSERVERS=dhcp.mydomain.tld,dhcp2.mydomain.tld

Cmnd_Alias DNS=/usr/local/sbin/rndc,/usr/local/sbin/bind
Cmnd_Alias DHCP=/usr/local/sbin/dhcpd

at the top, then I could add these lines to the bottom:

ADMINS ALL=(ALL) DNS,DHCP
DNSADMINS NAMESERVERS=(DAEMONS) DNS
DHCPADMINS DHCPSERVERS=(DAEMONS) DHCP

Note that there are no spaces between the users and commas, likewise, servers and commands only have a comma seperating them -- '''no spaces'''. This would essentially give jimbo rights to do root-priviledge stuff with any server, as any daemon, but only using the commands that '''DNS''' and '''DHCP''' specify; peet would only get root access to NAMESERVERS, only run as the DAEMONS, and only use the commands in DNS. Light would only get root access to DHCPSERVERS, run as DAEMONS and only be able to run /usr/local/sbin/dhcpd.

This is ideal if you have a) a lot of servers and/or b) a lot of admins with specific functions, that don't need complete access to the machine, but do need some sort of administrative rights on it.

[[Category:System Commands]] [[Category:Ports and Packages]] [[Category:Configuring FreeBSD]]

Sudo, configuring

2005-10-16T11:46:45Z

Baraboom:

First, install [[sudo]]. [[su]] to root and go to /usr/ports and then find out where the port is:

[dave]@deus ~ % sudo
-bash: sudo: command not found
[dave]@deus ~ % su -
Password:
[root]@deus ~ # cd /usr/ports && make search name=sudo
Port: sudo-1.6.7.5
Path: /usr/ports/security/sudo
Info: Allow others to run commands as root
Maint: mharo@FreeBSD.org
B-deps:
R-deps:

[root]@deus /usr/ports # cd security/sudo
[root]@deus /usr/ports/security/sudo # make install clean

Once it's installed, you'll need to run [[visudo]] since there's no other way to edit /etc/sudoers (well, you can use another editor, but it just won't work.)

Note that [[visudo]] doesn't actually call the [[vi]] editor, just your default editor; if that ''happens'' to be [[vi]] then it will come up. Otherwise, your regular editor will come up.

/etc/sudoers has one entry in it:
root ALL=ALL(ALL) ALL
which doesn't really explain what those ALLs mean in context; so often a lot of folks will set the sudoers to give ALL=ALL(ALL) ALL to every user they add. That's nice, but you're giving all of root's power away. You might as well give users the root password and save them the hassle of using [[sudo]] at all.

The explanation:
sudo-user machine=(effective user rights) command

So, if I want to give Jimbo [[root]] access on my server, Pete root on my laptop and Light only to have access to [[shutdown]] on all my machines, my sudoers would look like:
root ALL=ALL(ALL) ALL
jimbo ALL=samizdata.mydomain.tld(ALL) ALL
peet ALL=deus(ALL) ALL
light ALL=ALL(ALL) /sbin/shutdown

Finally, if you just want to give yourself [[root]] access on your server via sudo with no password, your sudoers might look like:
root ALL=ALL(ALL) ALL
convoy ALL=(ALL) NOPASSWD: ALL

'''NOTE:''' remember that setting sudo rights for multiple machines in a single '''sudoers''' file is only meaningful if that file is actually shared or distributed across those multiple machines. Simply writing permissions for the machine samizdata ''on'' the machine deus isn't going to do anything useful by itself. You would need to copy the file contents over to all the machines that are listed (and then [[kill]] -HUP the sudo process, if it's running,) in order to make the changes meaningful.

==Using Aliases to make life easier==

You can make groups within the sudoers file so that you don't have to type more than you need to. Follow this format:

'''User_Alias''' allows you to define a group of users
'''Runas_Alias''' allows you to define the daemon or user the command can run as
'''Host_Alias''' allows you to define a group of hosts
'''Cmnd_Alias''' allows you to define which commands (full path '''must''' be given) are in a group

You ''can'' use already existing system groups, but you have to add the prefix % (e.g., %wheel)

As an example, if my /etc/sudoers showed:

User_Alias ADMINS=jimbo
User_Alias DNSADMINS=peet
User_Alias DHCPADMINS=light

Runas_Alias DAEMONS=bind,dhcpd,sshd

Host_Alias NAMESERVERS=ns1.samizdata.mydomain.tld,ns2.samizdata.mydomain.tld
Host_Alias DHCPSERVERS=dhcp.mydomain.tld,dhcp2.mydomain.tld

Cmnd_Alias DNS=/usr/local/sbin/rndc,/usr/local/sbin/bind
Cmnd_Alias DHCP=/usr/local/sbin/dhcpd

at the top, then I could add these lines to the bottom:

ADMINS ALL=(ALL) DNS,DHCP
DNSADMINS NAMESERVERS=(DAEMONS) DNS
DHCPADMINS DHCPSERVERS=(DAEMONS) DHCP

Note that there are no spaces between the users and commas, likewise, servers and commands only have a comma seperating them -- '''no spaces'''. This would essentially give jimbo rights to do root-priviledge stuff with any server, as any daemon, but only using the commands that '''DNS''' and '''DHCP''' specify; peet would only get root access to NAMESERVERS, only run as the DAEMONS, and only use the commands in DNS. Light would only get root access to DHCPSERVERS, run as DAEMONS and only be able to run /usr/local/sbin/dhcpd.

This is ideal if you have a) a lot of servers and/or b) a lot of admins with specific functions, that don't need complete access to the machine, but do need some sort of administrative rights on it.

[[Category:System Commands]] [[Category:Ports and Packages]] [[Category:Configuring FreeBSD]]

User:Baraboom

2005-10-15T23:47:45Z

Baraboom:

i hate red links

Apache, Configuring

2005-10-15T23:46:43Z

Baraboom:

KeepAlives Off

Newsyslog.conf

2005-10-15T23:45:29Z

Baraboom:

(Usually located at '''/etc/newsyslog.conf''')

Controls behavior of [[newsyslog]], the utility which periodically (in most systems, once per hour) reviews all logs mentioned in this file and archives / rotates / trims those logs in accordance with specifications contained within. See '''man newsyslog''' for lots of detailed info on setting this up.

==Rotating Apache Logs==
/path/to/some.log root:wheel 600 3 * $D0 JB /var/run/httpd.pid 30

This line will rotate the log, maintain the privileges, keep 3 old rotations, rotate daily at midnight, treat the log as a binary file, compress it with bzip2 and restart apache with signal 30. There are obviously a lot of options you can change to suit your needs but the 'B' flag and the '30' signal are recommended for apache logs.

[[Category:Important Config Files]]

Newsyslog.conf

2005-10-15T23:45:09Z

Baraboom:

(Usually located at '''/etc/newsyslog.conf''')

Controls behavior of [[newsyslog]], the utility which periodically (in most systems, once per hour) reviews all logs mentioned in this file and archives / rotates / trims those logs in accordance with specifications contained within. See '''man newsyslog''' for lots of detailed info on setting this up.

==Rotating Apache Logs==
/path/to/some.log root:wheel 600 3 * $D0 JB /var/run/httpd.pid 30

This line will rotate the log, maintain the privileges, keep 3 old rotations, rotate daily at midnight, treat the log as a binary file, compress it with bzip2 and restart apache with signal 30.

There are obviously a lot of options you can change to suit your needs but the 'B' flag and the '30' signal are recommended for apache logs.

[[Category:Important Config Files]]