The root
. If
you start the server as a non-root user, it will fail to change to the
specified group, and will instead continue to run as the group of the
original user. Unix-group is one of:
#
followed by a group number.It is recommended that you set up a new group specifically for
running the server. If the configured
Don't set root
unless
you know exactly what you are doing, and what the dangers are.
It is not recommended to use the group nobody
,
which is not intended for use by long-running daemons.
The root
.
If you start the server as a non-root user, it will fail to change
to the lesser privileged user, and will instead continue to run as
that original user. If you do start the server as root
,
then it is normal for the parent process to remain running as root.
Unix-userid is one of:
The user should have no privileges that result in it being able to access files that are not intended to be visible to the outside world, and similarly, the user should not be able to execute code that is not meant for HTTP requests. It is recommended that you set up a new user and group specifically for running the server.
Don't set root
unless
you know exactly what you are doing, and what the dangers are.
It is not recommended to use the user nobody
,
which is not intended for use by long-running daemons.
This directive tells the server to chroot(8) to the specified directory after startup, but before accepting requests over the 'net.
Note that running the server under chroot is not simple, and requires additional setup, particularly if you are running scripts such as CGI or PHP. Please make sure you are properly familiar with the operation of chroot before attempting to use this feature.
When On, startup will fail if the suexec binary doesn't exist or has an invalid owner or file mode.
When Off, suEXEC will be disabled even if the suexec binary exists and has a valid owner and file mode.