Pages : 1
#1 27-06-2012 15:36:31
- hdahmani
- Membre
- Inscription : 31-05-2012
- Messages : 81
Problème avec le mod userdir
Bonjour,
Je viens de formater mon system et de le réinstaller, je voudrais installer un serveur apache en mode multiutilisateur et installer le mod userdir !!
J’ai bien la page test, INDEX OF / ~test
Mes je ne parviens pas à afficher INDEX OF/~utilisateurs
je n'ai pas mes dossiers
J’ai la page suivante qui s’affiche
Forbidden: You don’t have permission to access /~ utilisateurs on this server
Si quelqu’un peut me dire quoi faire merci d’avance
Hors ligne
#2 28-06-2012 12:32:27
- hdahmani
- Membre
- Inscription : 31-05-2012
- Messages : 81
Re : Problème avec le mod userdir
Je pense que ses une question de droit, mes je ne sais pas ou chercher s’il vous plais j’ai besoin d’aide, Merci
Hors ligne
#4 29-06-2012 16:24:11
- hdahmani
- Membre
- Inscription : 31-05-2012
- Messages : 81
Re : Problème avec le mod userdir
Merci pour ton aide voila mon fichier /etc/apache2.conf
ased upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "foo.log"
# with ServerRoot set to "/etc/apache2" will be interpreted by the
# server as "/etc/apache2/foo.log".
#
### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
LockFile ${APACHE_LOCK_DIR}/accept.lock
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15
##
## Server-Pool Size Regulation (MPM specific)
##
# 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 mpm_prefork_module>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0
</IfModule>
# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadLimit: ThreadsPerChild can be changed to this maximum value during a
# graceful restart. ThreadLimit can only be changed by stopping
# and starting Apache.
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 64
ThreadsPerChild 25
MaxClients 150
MaxRequestsPerChild 0
</IfModule>
# event MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_event_module>
StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 64
ThreadsPerChild 25
MaxRequestsPerChild 0
</IfModule>
# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}
#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#
AccessFileName .htaccess
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ~ "^\.ht">
Order allow,deny
Deny from all
Satisfy all
</Files>
#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain
#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log
#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn
# Include module configuration:
Include mods-enabled/*.load
Include mods-enabled/*.conf
# Include all the user configurations:
Include httpd.conf
# Include ports listing
Include ports.conf
#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.
# Include generic snippets of statements
Include conf.d/
# Include the virtual host configurations:
Include sites-enabled/
Hors ligne
#6 30-06-2012 11:11:34
- hdahmani
- Membre
- Inscription : 31-05-2012
- Messages : 81
Re : Problème avec le mod userdir
bonjour,
oui bien sur le mod userdir et activé!!
J’ai bien la page test, INDEX OF / ~test
Mes je ne parviens pas à afficher INDEX OF/~utilisateurs
je n'ai pas mes dossiers
J’ai la page suivante qui s’affiche
Forbidden: You don’t have permission to access /~ utilisateurs on this server
Hors ligne
#8 30-06-2012 14:55:46
- hdahmani
- Membre
- Inscription : 31-05-2012
- Messages : 81
Re : Problème avec le mod userdir
oui j'ai crée le repertoire public_html , dans home le chemin que j'ai donner et :
home/utilisateurs/public_html/dahmani!
Cela te parait t'il correct ??
Hors ligne
#9 01-07-2012 16:37:28
Re : Problème avec le mod userdir
En fait , userdir permet aux utilisateurs système d'avoir un espace web accessible sans devoir toucher à la conf d'apache , par contre il faut que 1 l'utilisateur systém existe et posséde un "home" exemple , utilisateur cdsl et hdahmani
Si les utilisateurs n’existent pas encore
useradd cdsl
useradd hdahmaniNous avons donc normalement ( sauf si tu as modifié le fichier skel ) les chemins suivants
/home/cdsl
/home/hdahmanimaintenant si cdsl veut accéder à certains fichiers via le web en utilisant l'url
http://<serveur>/~cdsl
Il lui faut créer le répertoire public_html dans son home, soit
/home/cdsl/public_htmlSi hdahmani veut aussi acceder à ses fichiers il devra lui aussi créer le répertoire public_html das son home
Voilà comment fonctionne le module par defaut.
Maintenant tu peux modifier le fonctionnement en éditant et adaptant les chemins par défaut du fichier /etc/apache2/mods-enabled/userdir.conf
dont la conf par défaut est :
<IfModule mod_userdir.c>
UserDir public_html
UserDir disabled root
<Directory /home/*/public_html>
AllowOverride FileInfo AuthConfig Limit Indexes
Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
<Limit GET POST OPTIONS>
Order allow,deny
Allow from all
</Limit>
<LimitExcept GET POST OPTIONS>
Order deny,allow
Deny from all
</LimitExcept>
</Directory>
</IfModule>Hors ligne
#10 22-07-2012 15:10:25
- hdahmani
- Membre
- Inscription : 31-05-2012
- Messages : 81
Re : Problème avec le mod userdir
merci de ton aide! ouf ca marche
Hors ligne
Pages : 1