Installation d un serveur cartographique sur GNU/Linux: Red Hat Enterprise Linux v.4

Transcription

1 1 / 48 Installation d un serveur cartographique sur GNU/Linux: Red

2 2 / 48 INDEXATION DU DOCUMENT TITRE : REFERENCE : Installation d un serveur cartographique sur GNU/Linux: Red ACTION NOM DATE SIGNATURE RÉDIGÉ PAR Jean David TECHER SUIVI DU DOCUMENT INDICE DATE MODIFICATIONS NOM

3 3 / 48 Table des matières 1 Pré-requis : Installer Red 1 2 Installation de l application cartographique Les outils utilisés Automatisation et installation complète A Explication détaillée de l installation des différents éléments 9 A.1 Création du répertoire des sources et téléchargement des sources A.2 Geos A.3 Proj A.4 PostgreSQL A.5 PostGIS A.6 PostgreSQL : Création du super-utilisateur postgres et initilisation du groupe de bases de données par défaut A.7 PDFLIB A.8 LibJpeg,LibPng, FreeType2 et GD A.9 Php A.10 Gdal A.11 MapServer A.12 Installation de l application cartographique de démonstration A.12.1 Pour Apache A.12.2 Pour PostgreSQL A.12.3 Installer l application de démonstration B Fichiers de configuration 18 B.1 Script d installation général B.2 Apache B.3 PostgreSQL B.3.1 Fichier de configuration du serveur B.3.2 Fichier pour le service C Bibliographie 48 C.1 [1] C.2 [2]

4 4 / 48 Table des figures 1.1 Copie d écran conforme à la désactivation du pare-feu sur Red Hat Copie d écran conforme à la désactivation de SELinux sur Red Hat Installation des paquetages de la rubrique "Outils de développement" Formulaire d accès à l application L application de démonstration A.1 Première copie d écran pour PHPINFO A.2 Seconde copie d écran pour PHPINFO : les extensions de MapServer(MapScript), PDFLIB (pdf) et PostgreSQL (pgsql) ont bien été prises en compte lors de la compilation de PHP

5 5 / 48 Liste des tableaux 1.2 Les options choisies lors de l installation Ensemble des outils à installer

6 Résumé Ce guide fournit les diverses phases d installation d un serveur cartographique sous GNU/Linux pour Red Hat Enterprise Linux v.4. Le premier chapitre fournit l installation adéquate et minimale requise afin de pouvoir compiler et installer nos divers outils sur de cette distribution. L objectif du premier chapitre est de proposer un environnement de compilation GNU/Linux minimal conforme à l implémentation de solutions cartographiques. Les divers outils nécessaires pour nos solutions cartographiques sont abordés dans le second chapitre ainsi que le déploiement automatique des applications cartographqiues.les compilations et installations respectives des différents outils sont fournis en annexe de ce document.

7 1 / 48 Chapitre 1 Pré-requis : Installer Red Hat Enterprise Linux v.4 Red est fourni avec 4 CD principaux. Ici nous n aurons besoin que des 3 premiers CD. Au niveau de l installation de la Red Hat, nous avons ôpté pour une installation minimale. A titre indicatif, sont fournis dans le tableau suivant divers paramètres choisis lors de l installation du système Red Hat Langue Clavier Méthode d installation Partitionnement Chargeur de boot Pare-feu SELinux Mode d installation Paquetages à installer Français Latin9 CD Local Automatique GRUB Désactivé Désactivé personnalisé Développement / Outils de développement TAB. 1.2 Les options choisies lors de l installation Si par la suite, on souhaite partir d une installation d une Red Hat déjà existante, il est nécessaire que les divers points suivants soient impérativement respectés : 1. Le gestionnaire de pare-feu de Red Hat et de SELinux doivent être désactivés. 2. Au niveau des paquetages à installer : certains paquetages relatifs à la rubrique "Outils de développements" du gestionnaire de paquetages doivent être installés. Pour désactiver le pare-feu et SELinux, allez dans "Applications" --> "Paramètres de système" --> "Niveau de sécurité"

8 2 / 48 FIG. 1.1 Copie d écran conforme à la désactivation du pare-feu sur Red Hat

9 3 / 48 FIG. 1.2 Copie d écran conforme à la désactivation de SELinux sur Red Hat Toujours dans le cas d une installation déjà existante, pour installer le paquetage "Développement / Outils de développement" allez dans "Applications" --> "Paramètres de système" --> "Ajouter/Supprimer des applications" et cochez la case "Outils de Développement" dans la section développement. Cliquez sur "Mettre à jour". Pour procéder à l installation de l ensemble des paquetages concernés vous aurez besoin des CD n 2 et n 3 de la Red Hat. Celà permettra de fournir les outils tel que configure, make, perl etc...

10 4 / 48 FIG. 1.3 Installation des paquetages de la rubrique "Outils de développement"

11 5 / 48 Chapitre 2 Installation de l application cartographique Nous allons procéder ici aux diverses compilations et installations. Les diverses étapes doivent avoir lieu dans l ordre chronologique des sections successives de ce chapitre. Nous commencerons ce chapitre pour fournir un petit descriptif des divers outils à installer. Nous terminerons par la mise en place automatique de l application cartographique. NOTE Nous avons rédigé un script install.sh contenu dans les sources à télécharger qui effectue lles diverses commandes à effectuer. 2.1 Les outils utilisés L ensemble des outils utilisés est récapitulé dans le tableau suivant Outil Version Installation à partir de GEOS sources PROJ sources POSTGRESQL sources POSTGIS sources PDFLIB 5.0.4p1 sources LIBJPEG 6b RPM LIBPNG RPM FREETYPE RPM GD sources PHP sources GDAL sources MAPSERVER sources TAB. 2.2 Ensemble des outils à installer Certaines installations auront lieu à partir des sources, d autres à partir de RPM. Pour la suite du chapitre, il est nécessaire de se connecter soit en SSH sur la machine-cible si on n est pas connecté sur la machine ou d ouvrir un terminal localement sur la machine depuis la session graphique courante. Pour ce dernier choix, rendez-vous à "Applications" --> "Outils de système" --> "Terminal". Selon votre choix,

12 6 / 48 Connexion par SSH : Depuis un terminal, tapez ssh root@ < hote_distant > où <hote_distant> est l IP de la machine distante. Répondez par yes si une question vous est posée, saisissez le mot de passe de root si celà vous est aussi demandé Connexion depuis la sessions graphique courante Pour ce dernier choix, rendez-vous à "Applications" --> "Outils de système" --> "Terminal". Saisissez whoami si cette commande vous renvoit une réponse différente de root alors saisissez su et comme demandé, saisissez le mot de passe de root 2.2 Automatisation et installation complète Pour procéder à l installation complète, il vous suffira de faire cd wget http :// mapserver.com/applis/download / serveur_carto_v1.zip unzip serveur_carto_v1. zip chmod 700 install. sh./ install.sh L installation commence. Veuillez alors patienter le temps de voir s afficher le message suivant dans le terminal... %%%%%%%%%%%%%%%%%%%%%%%%% % INSTALLATION TERMINEE % %%%%%%%%%%%%%%%%%%%%%%%%% A l apparition de ce message, l installation des différents élements est donc terminée! Par la suite, pour accéder à l application, saisissez simplement http ://nom_de_la_machine ou http ://IP_de_la_machine. Vous accéderez au formulaire d accès suivant. Saisissez comme Login ddass26 et comme mot de passe ddass26

13 7 / 48 FIG. 2.1 Formulaire d accès à l application Vous accéderez alors à l application de démonstration

14 8 / 48 FIG. 2.2 L application de démonstration Bonne navigation!

15 9 / 48 Annexe A Explication détaillée de l installation des différents éléments Remarque : Cet annexe détaille l ensemble des commandes qui ont été utilisées dans le second chapitre. Puisque l installation a été automatisée par l emploi d un script shell install.sh (voir section "Automatisation et installation complète" du second chapitre), nous proposons ici une mise en oeuvre manuelle détaillant les divers points abordés lors de l installation. Nous procéderons ainsi ici aux diverses compilations et installations. Les diverses étapes doivent avoir lieu dans l ordre chronologique des sections successives de ce chapitre. Le dossier de téléchargement pour les sources est le répertoire-racine /mnt/src. Quand un outil est abordé, celui-ci fait l objet d une section. Pour chaque outil, nous commencerons par un descriptif succinct puis par son installation au sens GNU/Linux du terme : configuration (./configure...),compilation (make) et installation (make install) A.1 Création du répertoire des sources et téléchargement des sources Tapez la commande suivante pour créer le répertoire /mnt/src mkdir /mnt/src Rendez-vous ensuite dans ce répertoire cd /mnt/src On téléchargera l ensemble des sources à l adresse suivante http :// grâce à l utilitaire wget wget http :// mapserver.com/applis/download / serveur_carto_v1.zip On décompresse ce fichier zippé en faisant unzip serveur_carto_v1. zip A.2 Geos GEOS est un paquetage qui permet d ajouter des fonctionnalités spatiales supplémentaires ou relationnelles ou topologiques à PostGIS telles que Within(), Intersects(). Le site de référence est http ://geos.refractions.net. Pour installer Geos, faisons

16 10 / 48 cd /mnt/src/ tar xvjf geos tar. bz2 cd geos &&./ configure && make && make install On s assure que Geos est installé en faisant par exemple geos - config -- version qui devrait nous renvoyer A.3 Proj Proj est la librairie qui référence l ensemble des divers systèmes de projection géographique comme le Lambert II Etendu. Cette librairie offre aussi des fonctionnalités de reprojection entre divers systèmes de projection à PostGIS telle que la fonctionnalité transform(). Il est par exemple possible de passer d un système de projection comme le Lambert II Etendu au Lambert III Carto. Le site de ce projet est http :// Pour installer Proj, faisons cd /mnt/src tar xvzf proj tar. gz cd proj &&./ configure && make && make install Les librairies concernant GEOS (libgeos, libgeos.so.2,libproj.so...) sont installées dans le répertoire /usr/local/lib. Il faut inclure ce chemin dans le fichier /etc/ld.so.conf en fin de fichier en faisant echo /usr/local/lib >> /etc/ld.so.conf ldconfig A.4 PostgreSQL PostgreSQL est le système de gestion de bases de données relationnelles (SGDBR) open source le plus évolué actuellement. Bien que MySQL est le plus populaire, PostgreSQL a toujours su devancé cette dernière en bien des points. A titre d exemple, PostgreSQL a toujours veillé a respecté les diverses révisions des normes SQL actuelles (plus de 50 % pour les révisions actuelles de 2003). Il offre aussi de nombreux avantages aussi bien au niveau des spécificités des transactions que son extensibilité avec divers langages de programmation comme Php, perl, tcl,c/c++... Le site de référence est http :// Le site francophone est http :// On s assure dans un premier temps qu aucune RPM nécessitant PostgreSQL est installé. Pour s en rassurer on désintalle tout ce qui fait référence à PostgreSQL rpm -e postgresql rpm -e -- nodeps postgresql Pour installer PostgreSQL, il est nécessaire de faire les commandes suivantes cd /mnt/src tar xvjf postgresql tar. bz2 cd postgresql &&./ configure -- enable - nls && make && make install Au niveau des options d installation, nous avons opté pour l option --enable-nls de manière à avoir l aide des utilitaires de cette distribution en français.

17 11 / 48 A.5 PostGIS PostGIS est une extension pour PostgreSQL. PostGIS, en tant que extension, fournit de nouvelles fonctionnalités à PostgreSQL. Il s agira de fonctionnalités d ordre spatiales (topologie spatiale, opérateurs spatiaux et relationnelles). Cet ajout confère a PostgreSQL le statut de bases de données spatiales. Le site du projet est http ://postgis.refractions.net Pour installer PostGIS, il est nécessaire de renseigner le répertoire bin de PostgreSQL /usr/local/pgsql/bin temporairement dans le PATH de la machine et de rendre les libraires accessibles - elles sont localisées dans le répertoire /usr/local/pgsql/lib de PostgreSQL export PATH =/ usr/local/pgsql/bin:$path echo /usr/local/pgsql/lib >> /etc/ld.so.conf ldconfig Il ne reste plus qu à installer PostGIS cd /mnt/src tar xvzf postgis tar. gz cd postgis &&./ configure && make && make install A.6 PostgreSQL : Création du super-utilisateur postgres et initilisation du groupe de bases de données par défaut Pour installer PostgreSQL, il est nécessaire de créer un super-utilisateur nommé postgres ayant comme mot de passe 01map (par exemple). Cette utilisateur n est qu un simple utilisateur au sens UNIX du terme sur la machine - il n a donc pas les mêmes droits que root. Le répertoire qui accueillera notre groupement de bases de données par défaut sera /mnt/pgdata dont postgres sera le propriétaire. Le groupement de bases de données par défaut sera encodé en LATIN9. Sur la machine en local, les connexions au serveur de PostgreSQL ne nécessiteront aucun mot de passe. Tout ce qui est attendu ci-dessus est obtenu en faisant useradd -p 01 map postgres ; mkdir / mnt/ pgdata /; chown -R postgres : postgres / mnt/ pgdata; su postgres -c "export PATH =/ usr/local/pgsql/bin:$path;export PGDATA =/ mnt/pgdata;initdb -E LATIN9 -A trust; mkdir $PGDATA/ pg_log" A.7 PDFLIB PDFLIB est une librairie qui propose notamment une API pour divers langages de programmation (java,c++,php...) pour pouvoir générer à la volée des documents au format pdf. Nous proposerons son API au langage PHP. Le site du projet est http :// Pour installer PDFLIB, nous ferons cd /mnt/src tar xvzf PDFlib -Lite p1 -Unix -src.tar.gz cd PDFlib - Lite p1 - Unix - src &&./ configure && make && make ldconfig install A.8 LibJpeg,LibPng, FreeType2 et GD Libjpeg et libpng sont des paquetages qui contiennent respectivement des bibliothèques graphiques pour jpeg et png. Ces dernières servent notamment pour la manipulation de fichier au format respectifs.jpeg ou.png. On les utilise notamment avec

18 12 / 48 divers langages de programmation. Ce sera ici le cas avec PHP. Libjpeg et Libpng sont nécessaires pour la compilation/installation de GD. Ils permettront ainsi à ce dernier de manipuler des fichiers dans les formats attendus. Libjpeg est disponible ici http :// Libpng est disponible ici http ://sourceforge.net/projects/libpng/ Freetype2 est utilsé dans le support des fontes comme par exemple pour le rendu de texte affiché sur une image (exemple : rendu de texte anti-crénelé sur une image). Par l intermédiaire de GD, FreeType fournit à MapServer le support pour le TrueType. Un des sites possibles pour ce projet est http :// GD est une librairie pour la création dynamique d image dans divers formats connus. Nous l utiliserons ici avec PHP. Map- Server nécessite que GD soit installé pour pouvoir générer des images au format GIF, PNG et JPEG. Le site du projet est http :// Toutes ces paquetages sont nécessaires pour que MapServer puisse générer des images dans divers formats au niveau de la carte. Pour installer toutes ces paquetages et sources, nous ferons cd /mnt/src rpm -Uivh libjpeg -devel -6b i386.rpm rpm -Uivh libpng fc2.i386.rpm rpm -Uivh libpng -devel i386.rpm rpm -e -- nodeps gd rpm -e -- nodeps gd - devel rpm -e -- nodeps gd - progs rpm -e -- nodeps freetype rpm - Uivh freetype i586. rpm rpm - Uivh freetype2 - devel i586. rpm ldconfig tar xvzf gd tar. gz cd gd / configure && make && make install ldconfig A.9 Php Php est un langage de script couramment utilisé pour le déploiment d application Web. Le site de référence est http :// Pour installer Php, il faut faire cd /mnt/src tar xvjf php tar. bz2 cd php On désintalle toute version de PHP ou dépendance pour toute version < rpm -e -- nodeps php Copions notres php. ini dans le répertoire cgi - bin d Apache cp../ php.ini /var/www/cgi -bin/ Copier les fichiers de PDFLIB dans les sources de PHP cp -r /mnt/src/pdflib -Lite p1 -Unix -src/bind/pdflib/php/ext/pdf/ ext/ cp /mnt/src/php / ext/pdf/ Makefile.php in /mnt/src/php / ext/pdf/ Makefile.in./ configure./ configure --enable -fastcgi --with -config -file =/ var/www/cgi -bin/php.ini --with -gd=/ usr/ local --with -png -dir =/ usr --with -ttf --with -freetype -dir =/ usr --with -zlib --with -pgsql --with -regex=system --enable -dbase --enable -dbx --with -jpeg -dir =/ usr --enable - versioning On compile une première fois sans PDFLIB

19 13 / 48 make PHP doit comprendre maintenant qu il doit prendre en compte PDFLIB./ buildconf -- force./ configure --enable -fastcgi --with -config -file =/ var/www/cgi -bin/php.ini --with -gd=/ usr/ local --with -pdflib --with -png -dir =/ usr --with -ttf --with -freetype -dir =/ usr --with -zlib --with -pgsql --with -regex=system --enable -dbase --enable -dbx --with -jpeg -dir =/ usr -- enable - versioning On compile une deuxième fois avec PDFLIB make make install ldconfig Créons le répertoire des extensions de PHP. Celui - ci accueillera plus tard php_mapscript. so de MapServer On copie aussi php dans le répertoire cgi - bin d Apache mkdir -p $(php -config --extension -dir) cp $(which php) /var/www/cgi -bin/ A.10 Gdal Gdal est un paquetage pour la gestion de divers format SIG connus (raster et vecteur). Il propose par exemple des utilitaires de conversion entre divers formats connus. MapServer utilise Gdal pour pouvoir notamment communiquer avec divers formats SIG aussi bien raster que vecteur. On le trouve à http :// Pour installer Gdal, nous ferons cd /mnt/src tar xvzf gdal tar. gz cd gdal / configure && make && make install ldconfig A.11 MapServer MapServer est un environnement de développement Open Source permettant de construire des applications internet à référence spatiale. Il est au coeur de toute application cartographique open source. Pour de plus amples détails, merci de consulter l url http ://mapserver.gis.umn.edu/ Pour installer MapServer, nous ferons cd /mnt/src tar xvzf mapserver tar. gz cd mapserver / configure --with -postgis --with -proj --with -geos --with -gd=/ usr/local --with -png --with - mapscript --with - wmsclient --with -wfs --with - wfsclient --with -php =/ mnt/src/php enable - fastcgi -- with - gdal -- with - ogr && make cp mapscript /php3/php_mapscript.so $(php -config --extension -dir)/

20 14 / 48 A.12 Installation de l application cartographique de démonstration Pour installer cette application de démonstration, il est impératif d effectuer quelques opérations concernant notamment les serveurs Apapche et PostgreSQL A.12.1 Pour Apache Nous nous assurons d abord qu Apache ne tourne pas sur la machine /etc/init.d/httpd status qui doit nous renvoyer httpd est arrêté Si ce n est pas le cas, on arrête temporairement le serveur en faisant /etc/init.d/httpd stop On supprime le fichier général de configuration d Apache et on met le nôtre rm -f /etc/httpd/conf/httpd.conf cp /mnt/src/httpd.conf /etc/httpd/conf/ Pour finir, faison en sorte qu Apache puisse être démarré en service à chaque redémarrage éventuel de la machine echo /etc/init.d/httpd start >> /etc/rc.local A.12.2 Pour PostgreSQL Copions les divers fichiers concernant respectivement la configuration (postgresql.conf) ainsi que le service de PostgreSQL (postgresql) comme il se doit dans les emplacements prévus à cette effet rm -f /mnt/pgdata/postgresql.conf cp /mnt/src/ postgresql.conf /mnt/pgdata/ cp /mnt/src/ postgresql /etc/init.d/ Faison aussi en sorte que si nous devons plus tard nous reconnecter dans un terminal que les utilitaires de PostgreSQL localisés dans /usr/local/pgsql/bin soient accessibles. Il faut pour celà mettre à jour en une seule fois la variable d environnement PATH de la machine. ll faut aussi que la varibale PGDATA (= /mnt/pgdata) soit aussi accessible. Pour ce faire, il nous suffir de saisir echo export PATH =\"\${PATH }:/ usr/local/pgsql/bin \" >> /etc/bashrc echo export PGDATA =\"/ mnt/ pgdata \" >> / etc/ bashrc Comme pour le service d Apache, il faut aussi que le service de PostgreSQL puisse démarrer à chaque redémarrage de la machine echo / etc/ init.d/ postgresql start >> / etc/ rc. local Nous noterons quand même les remarques suivantes

21 15 / 48 NOTE Pour savoir si le serveur est actif, il suffit de saisir dans un terminal su postgres -c " pg_ctl status" ou bien / etc/ init.d/ postgresql status A chaque démarrage de la machine, vous trouverez les fichiers de log de PostgreSQL dans le répertoire /mnt/pgdata/pg_log qui sont nommés sous la forme postgresql _ log par exemple. Ce dernier précise par exemple que le serveur a démarré le 24 Juin 2006 à Toute message de nature notification ou d erreur est stockée dans le tout dernier fichier de log du serveur PostgreSQL A.12.3 Installer l application de démonstration Pour installer notre application, nous commencerons par créer le répertoire-racine de notre application mkdir -p / var/ www/ serveur_carto_dhtml On se rend ensuite dans le répertoire /mnt/src et on décompresses le fichier d application serveur_carto_dhtml.zip dans le répertoire racine /var/www/serveur_carto_dhtml cd /mnt/src unzip serveur_carto_dhtml. zip -d / var/ www/ serveur_carto_dhtml / On accorde les droits attendus sur le répertoire racine chmod 777 -R / var/ www/ serveur_carto_dhtml / Comme notre application fonctionne par session avec PHP, il faut créer le répertoire /var/www/tmp qui stockera les sessions effectuées et lui accorder les droits en lecture, écriture pour tous mkdir -p /var/www/tmp chmod 777 /var/www/tmp Les images générées par MapServer - cartes, échelle, icônes pour la légende (...) - sont stockées dans le répertoire /var/www/- temp_mapserver auquel nous octroyons aussi les droits attendus mkdir -p / var/ www/ temp_mapserver chmod 777 / var/ www/ temp_mapserver Il nous faut maintenant créer la base de données sous PostgreSQL appelée ddass26 pour la démonstration / etc/ init.d/ postgresql stop / etc/ init.d/ postgresql start cd /mnt/src/ chmod 777 ddass26 *. sql su postgres -c " export PATH =/ usr/ local/ pgsql/ bin: $PATH; createdb ddass26; createlang plpgsql ddass26;psql -d ddass26 -f /usr/local/pgsql/share/contrib/lwpostgis.sql;psql -d ddass26 -f /usr/local/pgsql/share/contrib/spatial_ref_sys.sql;psql -d ddass26 -f /mnt/src/ ddass26 *. sql; createuser -s 01 map" Démarrons le serveur Apache si celà n a pas encore été fait /etc/init.d/httpd start Créeons aussi le fichier /var/www/serveur_carto_dhtml/applis/ddass26/phpinfo.php echo "<? phpinfo ();?>" >> /var/www/ serveur_carto_dhtml /applis/ddass26/phpinfo.php

22 16 / 48 Depuis un navigateur Web comme FireFox ou Internet Explorer, rendons-nous à l URL suivant http ://nom_de_la_machine/phpinfo.php où nom_de_la_machine est le nom_de_la_machine est le nom que vous avez saisi lors de l installation de la Red Hat. Vous devriez obtenir les deux copies d écran suivantes FIG. A.1 Première copie d écran pour PHPINFO Et la suivante

23 17 / 48 FIG. A.2 Seconde copie d écran pour PHPINFO : les extensions de MapServer(MapScript), PDFLIB (pdf) et PostgreSQL (pgsql) ont bien été prises en compte lors de la compilation de PHP

24 18 / 48 Annexe B Fichiers de configuration Sont fournis ici à titre d information le script général utilisé pour l automatisation de l installation ainsi que les divers fichiers de configurations respectif d Apache et de PostgreSQL B.1 Script d installation général Le script est le suivant!/ bin/sh Ce script permet d installer les divers outils nécessaires pour un serveur cartographique sur une machine 32 bits Red hat Linux Enterprise V4 Auteur: TECHER Jean David (01 MAP) Contact: Portable / Fixe Remarque : Abréviations utilisées ici ======== CMMI:./ configure [ OPIONS] && make && make install CO: faire seulement un "./ configure [ OPIONS] " avant de continuer MO: faire seulement un " make" avant de continuer MIO: faire seulement un " make install" avant de continuer repertoire ="/ mnt/src /" if [! -d " $repertoire " ]; then mkdir -p " $repertoire " fi cp $PWD /* $repertoire cd $repertoire Geos ==> CMMI tar xvjf geos tar. bz2 cd geos &&./ configure && make && make install Proj ==> CMMI cd.. tar xvzf proj tar. gz cd proj &&./ configure && make && make install cd.. Rendre accessibles les librairies de Geos et de Proj

25 19 / 48 qui sont dans / usr/ local/ lib echo /usr/local/lib >> /etc/ld.so.conf ldconfig PostgreSQL ==> CMMI rpm -e postgresql rpm -e -- nodeps postgresql tar xvjf postgresql tar. bz2 cd postgresql &&./ configure -- enable - nls && make && make install cd.. Rendre les libraires de PostgreSQL ainsi que ses binaires accessibles echo /usr/local/pgsql/lib >> /etc/ld.so.conf export PATH =/ usr/local/pgsql/bin:$path ldconfig PostGIS tar xvzf postgis tar. gz cd postgis &&./ configure && make && make install cd.. PostgreSQL : ========== - Création du super - administrateur postgres avec comme mot de passe ( Linux) 01 map - Création du répertoire / mnt/ pgdata - réaliser le premier cluster par défaut (/ mnt/ pgdata) avec initdb userdel -r postgres ; rm -rf / mnt/ pgdata /; useradd -p 01 map postgres ; mkdir / mnt/ pgdata /; chown -R postgres : postgres /mnt/pgdata;su postgres -c "export PATH =/ usr/local/pgsql/bin: $PATH; export PGDATA =/ mnt/ pgdata; initdb -E LATIN9 -A trust; mkdir $PGDATA/ pg_log" PDFLib ==> CMMI cd $repertoire tar xvzf PDFlib -Lite p1 -Unix -src.tar.gz cd PDFlib - Lite p1 - Unix - src &&./ configure && make && make install ldconfig cd.. Installation des diveres RPM nécessaires pour GD rpm -Uivh libjpeg -devel -6b i386.rpm rpm -Uivh libpng fc2.i386.rpm rpm -Uivh libpng -devel i386.rpm rpm -e -- nodeps gd rpm -e -- nodeps gd - devel rpm -e -- nodeps gd - progs rpm -e -- nodeps gd rpm -Uivh gd i386.rpm rpm -Uivh gd -devel i386.rpm rpm -Uivh gd -progs i386.rpm rpm -e -- nodeps freetype rpm - Uivh freetype i586. rpm rpm - Uivh freetype2 - devel i586. rpm ldconfig GD ==> CMMI

26 20 / 48 tar xvzf gd tar. gz cd gd / configure && make && make install ldconfig cd.. sleep 5 PHP ==> CMMI tar xvjf php tar. bz2 cd php rpm -e -- nodeps php cp../ php.ini /var/www/cgi -bin/ cp -r /mnt/src/pdflib -Lite p1 -Unix -src/bind/pdflib/php/ext/pdf/ ext/ cp /mnt/src/php / ext/pdf/ Makefile.php in /mnt/src/php / ext/pdf/ Makefile.in rm -f./ configure rm -f configure./ configure --enable -fastcgi --with -config -file =/ var/www/cgi -bin/php.ini --with -gd=/ usr/ local --with -png -dir =/ usr --with -ttf --with -freetype -dir =/ usr --with -zlib --with -pgsql --with -regex=system --enable -dbase --enable -dbx --with -jpeg -dir =/ usr --enable - versioning make rm -f./ configure./ buildconf -- force./ configure --enable -fastcgi --with -config -file =/ var/www/cgi -bin/php.ini --with -gd=/ usr/ local --with -pdflib --with -png -dir =/ usr --with -ttf --with -freetype -dir =/ usr --with -zlib --with -pgsql --with -regex=system --enable -dbase --enable -dbx --with -jpeg -dir =/ usr -- enable - versioning make make install ldconfig mkdir -p $(php -config --extension -dir) cp $(which php) /var/www/cgi -bin/ echo ScriptAlias /cgi -bin/ /var/www/cgi -bin/ >> /etc/httpd/conf/httpd.conf export PATH =/ usr/local/pgsql/bin /: $PATH cd.. tar xvzf gdal tar. gz cd gdal / configure && make && make install ldconfig cd.. tar xvzf mapserver tar. gz cd mapserver / configure --with -postgis --with -proj --with -geos --with -gd=/ usr/local --with -png --with - mapscript --with - wmsclient --with -wfs --with - wfsclient --with -php =/ mnt/src/php enable - fastcgi -- with - gdal -- with - ogr && make cp mapscript /php3/php_mapscript.so $(php -config --extension -dir)/ Mise en place pour l appli carto de la ddass26 cd.. Faire en sorte que le répertoire de PostgreSQL ainsi que la variable PGDATA soient accessibles à tous echo export PATH =\"\${PATH }:/ usr/local/pgsql/bin \" >> /etc/bashrc echo export PGDATA =\"/ mnt/ pgdata \" >> / etc/ bashrc On préconfigure Apache comme il se doit pour nos applis carto echo AddType application /x-httpd -php.php >> /etc/httpd/conf/httpd.conf echo Action application /x-httpd -php /cgi -bin/php >> /etc/httpd/conf/httpd.conf perl -i.bak -pe s/include conf.d\/\*. conf /\ Include conf.d\/\*. conf/g /etc/httpd/conf/

27 21 / 48 httpd.conf perl -i. bak -pe s/ DocumentRoot \"\/ var \/ www \/ html \"/ DocumentRoot \"\/ var \/ www \"/ g / etc/ httpd/conf/httpd.conf perl -i.bak -pe s/ Directory \"\/ var \/ www \/ html \"/ Directory \"\/ var \/ www \"/g /etc/httpd/ conf/httpd.conf echo Alias /applis/ \"/ var/www/ serveur_carto_dhtml /applis /\" >> /etc/httpd/conf/httpd. conf echo Alias /sc/ \"/ var/www/ serveur_carto_dhtml / interface /\" >> /etc/httpd/conf/httpd.conf On crée les divers répertoires attendus pour l application et on en profitera aussi pour décompresser notre belle appli ;-) mkdir -p / var/ www/ serveur_carto_dhtml unzip serveur_carto_dhtml. zip -d / var/ www/ serveur_carto_dhtml / chmod 777 -R / var/ www/ serveur_carto_dhtml echo "<? phpinfo ();?>" >> /var/www/ serveur_carto_dhtml /applis/ddass26/phpinfo.php mkdir -p /var/www/tmp chmod 777 /var/www/tmp mkdir -p / var/ www/ temp_mapserver chmod 777 / var/ www/ temp_mapserver cp postgresql.conf /mnt/pgdata/ cd /mnt/src On configure PostgreSQL en copiant nos propres fichiers de configuration c.a.d le fichier de configuration ainsi que celui qui gère le service cd /mnt/src/ cp postgresql / etc/ init.d/ cp postgresql.conf /mnt/pgdata/ On fait de même pour Apache c.a.d fichier de configuration ( httpd. conf) Remarque : Ici le fichier de configuration est déjà opérationnel pour notre appli cd /mnt/src rm -f /etc/httpd/conf/httpd.conf cp httpd.conf /etc/httpd/conf/ Pour rendre l application carto opérationnelle, il ne reste plus qu à charger le fichier SQL qui contient la export PATH =/ usr/local/pgsql/bin:$path /etc/init.d/httpd restart / etc/ init.d/ postgresql start sleep 7 cd /mnt/src/ chmod 777 ddass26 *. sql su postgres -c " export PATH =/ usr/ local/ pgsql/ bin: $PATH; createdb ddass26; createlang plpgsql ddass26;psql -d ddass26 -f /usr/local/pgsql/share/contrib/lwpostgis.sql;psql -d ddass26 -f /usr/local/pgsql/share/contrib/spatial_ref_sys.sql;psql -d ddass26 -f /mnt/src/ ddass26 *. sql; createuser -s 01 map" On fait en sorte que les services concernant Apache et PostgreSQL soient accessibles au démarrage ==> ils puissent démarrer sans aucun problème echo / etc/ init.d/ postgresql start >> / etc/ rc. local echo /etc/init.d/httpd start >> /etc/rc.local On précise que l installation est terminée clear;echo -e "\n\n\t %%%%%%%%%%%%%%%%%%%%%%%%%%\ n\t% INSTALLATION TERMINEE %\n\t %%%%%%%%%%%%%%%%%%%%%%%%%%\ n\n"

28 22 / 48 B.2 Apache Le fichier de configuration /etc/httpd/conf/httpd.conf utilisé est le suivant Based 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 <URL: http :// httpd. apache. org/ docs -2.0/ > 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 " logs/ foo. log" with ServerRoot set to "/ etc/ httpd" will be interpreted by the server as "/ etc/httpd/logs/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. Don t give away too much information about all the subcomponents we are running. Comment out this line if you don t mind remote sites finding out what major optional modules you are running ServerTokens OS 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.0/ mod/ mpm_common.htmllockfile >); you will save yourself a lot of trouble. Do NOT add a slash at the end of the directory path.

29 23 / 48 ServerRoot "/ etc/ httpd" PidFile: The file in which the server should record its process identification number when it starts. PidFile run/httpd.pid Timeout: The number of seconds before receives and sends time out. Timeout 120 KeepAlive : Whether or not to allow persistent connections ( more than one request per connection ). Set to " Off" to deactivate. KeepAlive Off 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 ServerLimit : maximum value for MaxClients for the lifetime of the server MaxClients : maximum number of server processes allowed to start MaxRequestsPerChild : maximum number of requests a server process serves <IfModule prefork.c> StartServers 8 MinSpareServers 5 MaxSpareServers 20 ServerLimit 256 MaxClients 256 MaxRequestsPerChild 4000 </ 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 ThreadsPerChild : constant number of worker threads in each server process MaxRequestsPerChild : maximum number of requests a server process serves <IfModule worker.c> StartServers 2

30 24 / 48 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0 </ IfModule > Listen: Allows you to bind Apache to specific IP addresses and/ or ports, in addition to the default. See also the <VirtualHost > directive. Change this to Listen on specific IP addresses as shown below to prevent Apache from glomming onto all bound IP addresses ( ) Listen :80 Listen 80 Dynamic Shared Object ( DSO) Support To be able to use the functionality of a module which was built as a DSO you have to place corresponding LoadModule lines at this location so the directives contained in it are actually available _before_ they are used. Statically compiled modules ( those listed by httpd -l ) do not need to be loaded here. Example: LoadModule foo_module modules/ mod_foo. so LoadModule access_module modules/ mod_access. so LoadModule auth_module modules/ mod_auth. so LoadModule auth_anon_module modules/ mod_auth_anon. so LoadModule auth_dbm_module modules/ mod_auth_dbm. so LoadModule auth_digest_module modules/ mod_auth_digest. so LoadModule ldap_module modules/ mod_ldap. so LoadModule auth_ldap_module modules/ mod_auth_ldap. so LoadModule include_module modules/ mod_include. so LoadModule log_config_module modules/ mod_log_config. so LoadModule env_module modules/ mod_env. so LoadModule mime_magic_module modules/ mod_mime_magic. so LoadModule cern_meta_module modules/ mod_cern_meta. so LoadModule expires_module modules/ mod_expires. so LoadModule deflate_module modules/ mod_deflate. so LoadModule headers_module modules/ mod_headers. so LoadModule usertrack_module modules/ mod_usertrack. so LoadModule setenvif_module modules/ mod_setenvif. so LoadModule mime_module modules/ mod_mime. so LoadModule dav_module modules/ mod_dav. so LoadModule status_module modules/ mod_status. so LoadModule autoindex_module modules/ mod_autoindex. so LoadModule asis_module modules/ mod_asis. so LoadModule info_module modules/ mod_info. so LoadModule dav_fs_module modules/ mod_dav_fs. so LoadModule vhost_alias_module modules/ mod_vhost_alias. so LoadModule negotiation_module modules/ mod_negotiation. so LoadModule dir_module modules/ mod_dir. so LoadModule imap_module modules/ mod_imap. so LoadModule actions_module modules/ mod_actions. so LoadModule speling_module modules/ mod_speling. so LoadModule userdir_module modules/ mod_userdir. so LoadModule alias_module modules/ mod_alias. so

31 25 / 48 LoadModule rewrite_module modules/ mod_rewrite. so LoadModule proxy_module modules/ mod_proxy. so LoadModule proxy_ftp_module modules/ mod_proxy_ftp. so LoadModule proxy_http_module modules/ mod_proxy_http. so LoadModule proxy_connect_module modules/ mod_proxy_connect. so LoadModule cache_module modules/ mod_cache. so LoadModule suexec_module modules/ mod_suexec. so LoadModule disk_cache_module modules/ mod_disk_cache. so LoadModule file_cache_module modules/ mod_file_cache. so LoadModule mem_cache_module modules/ mod_mem_cache. so LoadModule cgi_module modules/ mod_cgi. so Load config files from the config directory "/ etc/ httpd/ conf.d". Include conf.d/*. conf ExtendedStatus controls whether Apache will generate " full" status information ( ExtendedStatus On) or just basic information ( ExtendedStatus Off) when the " server - status" handler is called. The default is Off. ExtendedStatus On Section 2: Main server configuration The directives in this section set up the values used by the main server, which responds to any requests that aren t handled by a <VirtualHost > definition. These values also provide defaults for any <VirtualHost > containers you may define later in the file. All of these directives may appear inside <VirtualHost > containers, in which case these default settings will be overridden for the virtual host being defined. If you wish httpd to run as a different user or group, you must run httpd as root initially and it will switch. User/ Group: The name ( or number) of the user/ group to run httpd as.. On SCO ( ODT 3) use " User nouser" and " Group nogroup ".. On HPUX you may not be able to use shared memory as nobody, and the suggested workaround is to create a user www and use that user. NOTE that some kernels refuse to setgid( Group) or semctl( IPC_SET) when the value of ( unsigned ) Group is above 60000; don t use Group -1 on these systems! User apache Group apache ServerAdmin : Your address, where problems with the server should be e- mailed. This address appears on some server - generated pages, such as error documents. e.g. admin@your - domain. com ServerAdmin root@localhost ServerName gives the name and port that the server uses to identify itself. This can often be determined automatically, but we recommend you specify it explicitly to prevent problems during startup.

32 26 / 48 If this is not set to valid DNS name for your host, server - generated redirections will not work. See also the UseCanonicalName directive. If your host doesn t have a registered DNS name, enter its IP address here. You will have to access it by its address anyway, and this will make redirections work in a sensible way. ServerName new.host.name :80 UseCanonicalName : Determines how Apache constructs self - referencing URLs and the SERVER_NAME and SERVER_PORT variables. When set " Off", Apache will use the Hostname and Port supplied by the client. When set " On", Apache will use the value of the ServerName directive. UseCanonicalName Off DocumentRoot : The directory out of which you will serve your documents. By default, all requests are taken from this directory, but symbolic links and aliases may be used to point to other locations. DocumentRoot "/ var/ www/ serveur_carto_dhtml / applis/ ddass26" Each directory to which Apache has access can be configured with respect to which services and features are allowed and/ or disabled in that directory ( and its subdirectories ). First, we configure the " default" to be a very restrictive set of features. <Directory /> Options FollowSymLinks AllowOverride None </ Directory > Note that from this point forward you must specifically allow particular features to be enabled - so if something s not working as you might expect, make sure that you have specifically enabled it below. This should be changed to whatever you set DocumentRoot to. <Directory "/ var/ www/ serveur_carto_dhtml / applis/ ddass26"> Possible values for the Options directive are " None", " All", or any combination of: Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews Note that " MultiViews " must be named * explicitly * --- " Options All" doesn t give it to you. The Options directive is both complicated and important. Please see http :// httpd.apache.org/docs -2.0/ mod/core.htmloptions for more information.

33 27 / 48 Options Indexes FollowSymLinks AllowOverride controls what directives may be placed in. htaccess files. It can be " All", " None", or any combination of the keywords : Options FileInfo AuthConfig Limit AllowOverride None Controls who can get stuff from this server. Order allow, deny Allow from all </ Directory > UserDir: The name of the directory that is appended onto a user s home directory if a ~ user request is received. The path to the end user account public_html directory must be accessible to the webserver userid. This usually means that ~ userid must have permissions of 711, ~ userid/ public_html must have permissions of 755, and documents contained therein must be world - readable. Otherwise, the client will only receive a "403 Forbidden " message. See also: http :// httpd.apache.org/docs/misc/faq.htmlforbidden <IfModule mod_userdir.c> UserDir is disabled by default since it can confirm the presence of a username on the system ( depending on home directory permissions ). UserDir disable To enable requests to /~ user/ to serve the user s public_html directory, remove the " UserDir disable" line above, and uncomment the following line instead: UserDir public_html </ IfModule > Control access to UserDir directories. The following is an example for a site where these directories are restricted to read - only. < Directory / home /*/ public_html > AllowOverride FileInfo AuthConfig Limit 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 >

34 28 / 48 </ Directory > DirectoryIndex : sets the file that Apache will serve if a directory is requested. The index. html. var file (a type - map) is used to deliver content - negotiated documents. The MultiViews Option can be used for the same purpose, but it is much slower. DirectoryIndex index. html index. html. var index. php 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 </Files > TypesConfig describes where the mime. types file ( or equivalent ) is to be found. TypesConfig / etc/ mime. types 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 The mod_mime_magic module allows the server to use various hints from the contents of the file itself to determine its type. The MIMEMagicFile directive tells the module where the hint definitions are located. <IfModule mod_mime_magic.c> MIMEMagicFile /usr/share/magic.mime MIMEMagicFile conf/ magic </ IfModule > HostnameLookups : Log the names of clients or just their IP addresses e.g., www. apache. org ( on) or ( 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.

35 29 / 48 HostnameLookups Off EnableMMAP : Control whether memory - mapping is used to deliver files ( assuming that the underlying OS supports it). The default is on; turn this off if you serve from NFS - mounted filesystems. On some systems, turning it off ( regardless of filesystem ) can improve performance ; for details, please see http :// httpd.apache.org/docs -2.0/ mod/core.htmlenablemmap EnableMMAP off EnableSendfile : Control whether the sendfile kernel support is used to deliver files ( assuming that the OS supports it). The default is on; turn this off if you serve from NFS - mounted filesystems. Please see http :// httpd.apache.org/docs -2.0/ mod/core.html enablesendfile EnableSendfile 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 logs/ 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 The following directives define some format nicknames for use with a CustomLog directive ( see below). LogFormat "%h %l %u %t \"%r\" %>s %b \"%{ Referer}i\" \"%{ User -Agent}i\"" combined LogFormat "% h %l %u %t \"% r\" %>s %b" common LogFormat "%{ Referer}i -> %U" referer LogFormat "%{ User - agent}i" agent The location and format of the access logfile ( Common Logfile Format). If you do not define any access logfiles within a <VirtualHost > container, they will be logged here. Contrariwise, if you * do* define per -< VirtualHost > access logfiles, transactions will be logged therein and * not* in this file. CustomLog logs/ access_log common If you would like to have agent and referer logfiles, uncomment the following directives. CustomLog logs/ referer_log referer CustomLog logs/ agent_log agent

36 30 / 48 For a single logfile with access, agent, and referer information ( Combined Logfile Format), use the following directive : CustomLog logs/ access_log combined Optionally add a line containing the server version and virtual host name to server - generated pages ( internal error documents, FTP directory listings, mod_status and mod_info output etc., but not CGI generated documents or custom error documents ). Set to " " to also include a mailto: link to the ServerAdmin. Set to one of: On Off ServerSignature On Aliases: Add here as many aliases as you need ( with no limit). The format is Alias fakename realname Note that if you include a trailing / on fakename then the server will require it to be present in the URL. So "/ icons" isn t aliased in this example, only "/ icons /". If the fakename is slash - terminated, then the realname must also be slash terminated, and if the fakename omits the trailing slash, the realname must also omit it. We include the / icons/ alias for FancyIndexed directory listings. If you do not use FancyIndexing, you may comment this out. Alias /icons/ "/ var/www/icons /" <Directory "/ var/www/icons"> Options Indexes MultiViews AllowOverride None Order allow, deny Allow from all </ Directory > WebDAV module configuration section. <IfModule mod_dav_fs.c> Location of the WebDAV lock database. DAVLockDB /var/lib/dav/lockdb </ IfModule > ScriptAlias : This controls which directories contain server scripts. ScriptAliases are essentially the same as Aliases, except that documents in the realname directory are treated as applications and run by the server when requested rather than as documents sent to the client. The same rules about trailing "/" apply to ScriptAlias directives as to Alias. ScriptAlias /cgi -bin/ "/ var/www/cgi -bin /" "/ var/ www/ cgi - bin" should be changed to whatever your ScriptAliased CGI directory exists, if you have that configured. <Directory "/ var/www/cgi -bin">

37 31 / 48 AllowOverride None Options None Order allow, deny Allow from all </ Directory > Redirect allows you to tell clients about documents which used to exist in your server s namespace, but do not anymore. This allows you to tell the clients where to look for the relocated document. Example: Redirect permanent / foo http :// www. example. com/ bar Directives controlling the display of server - generated directory listings. IndexOptions : Controls the appearance of server - generated directory listings. IndexOptions FancyIndexing VersionSort NameWidth =* AddIcon* directives tell the server which icon to show for different files or filename extensions. These are only displayed for FancyIndexed directories. AddIconByEncoding ( CMP,/ icons/ compressed. gif) x- compress x- gzip AddIconByType (TXT,/ icons/text.gif) text /* AddIconByType (IMG,/ icons/image2.gif) image /* AddIconByType (SND,/ icons/sound2.gif) audio /* AddIconByType (VID,/ icons/movie.gif) video /* AddIcon /icons/binary.gif.bin.exe AddIcon /icons/binhex.gif.hqx AddIcon /icons/tar.gif.tar AddIcon /icons/world2.gif.wrl.wrl.gz.vrml.vrm.iv AddIcon / icons/ compressed. gif.z.z. tgz. gz. zip AddIcon /icons/a.gif.ps.ai.eps AddIcon /icons/layout.gif.html.shtml.htm.pdf AddIcon /icons/text.gif.txt AddIcon / icons/c. gif.c AddIcon /icons/p.gif.pl.py AddIcon / icons/f. gif. for AddIcon /icons/dvi.gif.dvi AddIcon /icons/uuencoded.gif.uu AddIcon /icons/script.gif.conf.sh.shar.csh.ksh.tcl AddIcon /icons/tex.gif.tex AddIcon / icons/ bomb. gif core AddIcon /icons/back.gif.. AddIcon /icons/hand.right.gif README AddIcon / icons/ folder. gif ^^ DIRECTORY ^^ AddIcon / icons/ blank. gif ^^ BLANKICON ^^ DefaultIcon is which icon to show for files which do not have an icon explicitly set. DefaultIcon / icons/ unknown. gif

38 32 / 48 AddDescription allows you to place a short description after a file in server - generated indexes. These are only displayed for FancyIndexed directories. Format: AddDescription " description " filename AddDescription " GZIP compressed document ". gz AddDescription " tar archive". tar AddDescription " GZIP compressed tar archive". tgz ReadmeName is the name of the README file the server will look for by default, and append to directory listings. HeaderName is the name of a file which should be prepended to directory indexes. ReadmeName README. html HeaderName HEADER. html IndexIgnore is a set of filenames which directory indexing should ignore and not include in the listing. Shell - style wildcarding is permitted. IndexIgnore.??* *~ * HEADER* README* RCS CVS *,v *,t DefaultLanguage and AddLanguage allows you to specify the language of a document. You can then use content negotiation to give a browser a file in a language the user can understand. Specify a default language. This means that all data going out without a specific language tag ( see below) will be marked with this one. You probably do NOT want to set this unless you are sure it is correct for all cases. * It is generally better to not mark a page as * being a certain language than marking it with the wrong * language! DefaultLanguage nl Note 1: The suffix does not have to be the same as the language keyword --- those with documents in Polish ( whose net - standard language code is pl) may wish to use " AddLanguage pl. po" to avoid the ambiguity with the common suffix for perl scripts. Note 2: The example entries below illustrate that in some cases the two character Language abbreviation is not identical to the two character Country code for its country, E.g. Danmark/dk versus Danish/da. Note 3: In the case of ltz we violate the RFC by using a three char specifier. There is work in progress to fix this and get the reference data for rfc1766 cleaned up. Catalan ( ca) - Croatian ( hr) - Czech ( cs) - Danish ( da) - Dutch ( nl) English ( en) - Esperanto ( eo) - Estonian ( et) - French ( fr) - German ( de) Greek - Modern ( el) - Hebrew ( he) - Italian ( it) - Japanese ( ja) Korean ( ko) - Luxembourgeois * ( ltz) - Norwegian Nynorsk ( nn) Norwegian ( no) - Polish ( pl) - Portugese ( pt) Brazilian Portuguese (pt - BR) - Russian ( ru) - Swedish ( sv)

39 33 / 48 Simplified Chinese (zh - CN) - Spanish ( es) - Traditional Chinese (zh - TW) AddLanguage ca. ca AddLanguage cs. cz. cs AddLanguage da. dk AddLanguage de. de AddLanguage el. el AddLanguage en. en AddLanguage eo. eo AddLanguage es. es AddLanguage et. et AddLanguage fr. fr AddLanguage he. he AddLanguage hr. hr AddLanguage it. it AddLanguage ja. ja AddLanguage ko. ko AddLanguage ltz. ltz AddLanguage nl. nl AddLanguage nn. nn AddLanguage no. no AddLanguage pl. po AddLanguage pt. pt AddLanguage pt - BR.pt - br AddLanguage ru. ru AddLanguage sv. sv AddLanguage zh - CN.zh - cn AddLanguage zh - TW.zh - tw LanguagePriority allows you to give precedence to some languages in case of a tie during content negotiation. Just list the languages in decreasing order of preference. We have more or less alphabetized them here. You probably want to change this. LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt - BR ru sv zh -CN zh -TW ForceLanguagePriority allows you to serve a result page rather than MULTIPLE CHOICES ( Prefer) [ in case of a tie] or NOT ACCEPTABLE ( Fallback ) [ in case no accepted languages matched the available variants ] ForceLanguagePriority Prefer Fallback Specify a default charset for all pages sent out. This is always a good idea and opens the door for future internationalisation of your web site, should you ever want it. Specifying it as a default does little harm; as the standard dictates that a page is in iso ( latin1) unless specified otherwise i.e. you are merely stating the obvious. There are also some security reasons in browsers, related to javascript and URL parsing which encourage you to always set a default char set. AddDefaultCharset on Commonly used filename extensions to character sets. You probably want to avoid clashes with the language extensions, unless you are good at carefully testing your setup after each change.

40 34 / 48 See http :// assignments /character -sets for the official list of charset names and their respective RFCs. AddCharset ISO iso latin1 AddCharset ISO iso latin2. cen AddCharset ISO iso latin3 AddCharset ISO iso latin4 AddCharset ISO iso latin5. cyr. iso - ru AddCharset ISO iso latin6. arb AddCharset ISO iso latin7. grk AddCharset ISO iso latin8. heb AddCharset ISO iso latin9. trk AddCharset ISO JP. iso jp. jis AddCharset ISO KR. iso kr. kis AddCharset ISO CN. iso cn. cis AddCharset Big5. Big5. big5 For russian, more than one charset is used ( depends on client, mostly): AddCharset WINDOWS cp win AddCharset CP866. cp866 AddCharset KOI8 -r. koi8 -r. koi8 - ru AddCharset KOI8 -ru.koi8 -uk.ua AddCharset ISO UCS -2. ucs2 AddCharset ISO UCS -4. ucs4 AddCharset UTF -8. utf8 The set below does not map to a specific ( iso) standard but works on a fairly wide range of browsers. Note that capitalization actually matters ( it should not, but it does for some browsers ). See http :// assignments /character -sets for a list of sorts. But browsers support few. AddCharset GB2312. gb2312. gb AddCharset utf -7. utf7 AddCharset utf -8. utf8 AddCharset big5. big5. b5 AddCharset EUC -TW.euc -tw AddCharset EUC -JP.euc -jp AddCharset EUC -KR.euc -kr AddCharset shift_jis. sjis AddType allows you to add to or override the MIME configuration file mime. types for specific file types. AddType application /x- tar. tgz AddEncoding allows you to have certain browsers uncompress information on the fly. Note: Not all browsers support this. Despite the name similarity, the following Add* directives have nothing to do with the FancyIndexing customization directives above. AddEncoding x- compress.z AddEncoding x- gzip. gz. tgz If the AddEncoding directives above are commented - out, then you probably should define those extensions to indicate media types: AddType application /x- compress.z AddType application /x- gzip. gz. tgz

41 35 / 48 AddHandler allows you to map certain file extensions to " handlers ": actions unrelated to filetype. These can be either built into the server or added with the Action directive ( see below) To use CGI scripts outside of ScriptAliased directories : ( You will also need to add " ExecCGI" to the " Options" directive.) AddHandler cgi - script. cgi For files that include their own HTTP headers: AddHandler send -as - is asis For server - parsed imagemap files: AddHandler imap - file map For type maps ( negotiated resources ): ( This is enabled by default to allow the Apache " It Worked" page to be distributed in multiple languages.) AddHandler type - map var Filters allow you to process content before it is sent to the client. To parse. shtml files for server - side includes ( SSI): ( You will also need to add " Includes " to the " Options" directive.) AddType text/ html. shtml AddOutputFilter INCLUDES. shtml Action lets you define media types that will execute a script whenever a matching file is called. This eliminates the need for repeated URL pathnames for oft - used CGI file processors. Format: Action media/ type / cgi - script/ location Format: Action handler - name / cgi - script/ location Customizable error responses come in three flavors: 1) plain text 2) local redirects 3) external redirects Some examples : ErrorDocument 500 " The server made a boo boo." ErrorDocument 404 / missing. html ErrorDocument 404 "/ cgi - bin/ missing_handler. pl" ErrorDocument 402 http :// www. example. com/ subscription_info. html Putting this all together, we can internationalize error responses. We use Alias to redirect any / error/ HTTP_ <error >. html. var response to our collection of by - error message multi - language collections. We use includes to substitute the appropriate text.

42 36 / 48 You can modify the messages appearance without changing any of the default HTTP_ <error >. html. var files by adding the line: Alias /error/include/ "/ your/include/path /" which allows you to create your own set of files by starting with the /var/www/error/include/ files and copying them to / your/ include/ path/, even on a per - VirtualHost basis. Alias /error/ "/ var/www/error /" <IfModule mod_negotiation.c> <IfModule mod_include.c> <Directory "/ var/www/error"> AllowOverride None Options IncludesNoExec AddOutputFilter Includes html AddHandler type - map var Order allow, deny Allow from all LanguagePriority en es de fr ForceLanguagePriority Prefer Fallback </ Directory > ErrorDocument 400 / error/ HTTP_BAD_REQUEST. html. var ErrorDocument 401 / error/ HTTP_UNAUTHORIZED. html. var ErrorDocument 403 / error/ HTTP_FORBIDDEN. html. var ErrorDocument 404 / error/ HTTP_NOT_FOUND. html. var ErrorDocument 405 / error/ HTTP_METHOD_NOT_ALLOWED. html. var ErrorDocument 408 / error/ HTTP_REQUEST_TIME_OUT. html. var ErrorDocument 410 / error/ HTTP_GONE. html. var ErrorDocument 411 / error/ HTTP_LENGTH_REQUIRED. html. var ErrorDocument 412 / error/ HTTP_PRECONDITION_FAILED. html. var ErrorDocument 413 / error/ HTTP_REQUEST_ENTITY_TOO_LARGE. html. var ErrorDocument 414 / error/ HTTP_REQUEST_URI_TOO_LARGE. html. var ErrorDocument 415 / error/ HTTP_UNSUPPORTED_MEDIA_TYPE. html. var ErrorDocument 500 / error/ HTTP_INTERNAL_SERVER_ERROR. html. var ErrorDocument 501 / error/ HTTP_NOT_IMPLEMENTED. html. var ErrorDocument 502 / error/ HTTP_BAD_GATEWAY. html. var ErrorDocument 503 / error/ HTTP_SERVICE_UNAVAILABLE. html. var ErrorDocument 506 / error/ HTTP_VARIANT_ALSO_VARIES. html. var </ IfModule > </ IfModule > The following directives modify normal HTTP response behavior to handle known problems with browser implementations. BrowserMatch " Mozilla /2" nokeepalive BrowserMatch " MSIE 4\.0 b2;" nokeepalive downgrade -1.0 force - response -1.0 BrowserMatch " RealPlayer 4\.0" force - response -1.0 BrowserMatch " Java /1\.0" force - response -1.0 BrowserMatch " JDK /1\.0" force - response -1.0 The following directive disables redirects on non - GET requests for a directory that does not include the trailing slash. This fixes a problem with Microsoft WebFolders which does not appropriately handle redirects for folders with DAV methods.

43 37 / 48 Same deal with Apple s DAV filesystem and Gnome VFS support for DAV. BrowserMatch " Microsoft Data Access Internet Publishing Provider " redirect - carefully BrowserMatch "^ WebDrive " redirect - carefully BrowserMatch "^ WebDAVFS /1.[012]" redirect - carefully BrowserMatch "^ gnome - vfs" redirect - carefully Allow server status reports generated by mod_status, with the URL of http :// servername / server - status Change the ". example. com" to match your domain to enable. < Location /server -status > SetHandler server - status Order deny, allow Deny from all Allow from. example. com </ Location > Allow remote server configuration reports, with the URL of http :// servername / server - info ( requires that mod_info.c be loaded). Change the ". example. com" to match your domain to enable. < Location /server -info > SetHandler server - info Order deny, allow Deny from all Allow from. example. com </ Location > Proxy Server directives. Uncomment the following lines to enable the proxy server: < IfModule mod_proxy.c> ProxyRequests On < Proxy *> Order deny, allow Deny from all Allow from. example. com </Proxy > Enable/ disable the handling of HTTP /1.1 " Via :" headers. (" Full" adds the server version; " Block" removes all outgoing Via: headers) Set to one of: Off On Full Block ProxyVia On To enable a cache of proxied content, uncomment the following lines. See http :// httpd.apache.org/docs -2.0/ mod/ mod_cache.html for more details. < IfModule mod_disk_cache.c> CacheEnable disk / CacheRoot "/ var/ cache/ mod_proxy " </ IfModule > </ IfModule >

44 38 / 48 End of proxy directives. Section 3: Virtual Hosts VirtualHost : If you want to maintain multiple domains/ hostnames on your machine you can setup VirtualHost containers for them. Most configurations use only name - based virtual hosts so the server doesn t need to worry about IP addresses. This is indicated by the asterisks in the directives below. Please see the documentation at <URL:http :// httpd.apache.org/docs -2.0/ vhosts/> for further details before you try to setup virtual hosts. You may use the command line option -S to verify your virtual host configuration. Use name - based virtual hosting. NameVirtualHost *:80 NOTE: NameVirtualHost cannot be used without a port specifier (e.g. :80) if mod_ssl is being used, due to the nature of the SSL protocol. VirtualHost example: Almost any Apache directive may go into a VirtualHost container. The first VirtualHost section is used for requests without a known server name. < VirtualHost *:80 > ServerAdmin webmaster@dummy - host. example. com DocumentRoot /www/docs/dummy -host.example.com ServerName dummy - host. example. com ErrorLog logs/dummy -host.example.com - error_log CustomLog logs/ dummy - host. example. com - access_log common </ VirtualHost > AddType application /x- httpd - php. php Action application /x-httpd -php /cgi -bin/php Alias / applis/ "/ var/ www/ serveur_carto_dhtml / applis /" Alias / sc/ "/ var/ www/ serveur_carto_dhtml / interface /" Alias / temp_mapserver / "/ var/ www/ temp_mapserver /" B.3 PostgreSQL Pour PostgreSQL, nous avons eu recours à deux fichier B.3.1 Fichier de configuration du serveur Le fichier de configuration du serveur /mnt/pgdata/postgresql.conf est le suivant PostgreSQL configuration file This file consists of lines of the form:

45 39 / 48 name = value ( The = is optional.) White space may be used. Comments are introduced with anywhere on a line. The complete list of option names and allowed values can be found in the PostgreSQL documentation. The commented - out settings shown in this file represent the default values. Please note that re - commenting a setting is NOT sufficient to revert it to the default value, unless you restart the postmaster. Any option can also be given as a command line switch to the postmaster, e.g. postmaster -c log_connections =on. Some options can be changed at run - time with the SET SQL command. This file is read on postmaster startup and when the postmaster receives a SIGHUP. If you edit the file on a running system, you have to SIGHUP the postmaster for the changes to take effect, or use " pg_ctl reload ". Some settings, such as listen_addresses, require a postmaster shutdown and restart to take effect FILE LOCATIONS The default values of these variables are driven from the -D command line switch or PGDATA environment variable, represented here as ConfigDir. data_directory = ConfigDir use data in another directory hba_file = ConfigDir / pg_hba. conf host - based authentication file ident_file = ConfigDir / pg_ident. conf IDENT configuration file If external_pid_file is not explicitly set, no extra pid file is written. external_pid_file = ( none) write an extra pid file CONNECTIONS AND AUTHENTICATION Connection Settings - listen_addresses = * what IP address( es) to listen on; comma - separated list of addresses ; defaults to localhost, * = all port = 5432 max_connections = 100 note: increasing max_connections costs ~400 bytes of shared memory per connection slot, plus lock space ( see max_locks_per_transaction ). You might also need to raise shared_buffers to support more connections. superuser_reserved_connections = 2 unix_socket_directory = unix_socket_group = unix_socket_permissions = 0777 octal bonjour_name = defaults to the computer name - Security & Authentication - authentication_timeout = , in seconds ssl = off password_encryption = on

46 40 / 48 db_user_namespace = off Kerberos krb_server_keyfile = krb_srvname = postgres krb_server_hostname = empty string matches any keytab entry krb_caseins_users = off - TCP Keepalives - see man 7 tcp for details tcp_keepalives_idle = 0 TCP_KEEPIDLE, in seconds; 0 selects the system default tcp_keepalives_interval = 0 TCP_KEEPINTVL, in seconds; 0 selects the system default tcp_keepalives_count = 0 TCP_KEEPCNT ; 0 selects the system default RESOURCE USAGE ( except WAL) Memory - shared_buffers = 1000 min 16 or max_connections *2, 8KB each temp_buffers = 1000 min 100, 8KB each max_prepared_transactions = 5 can be 0 or more note: increasing max_prepared_transactions costs ~600 bytes of shared memory per transaction slot, plus lock space ( see max_locks_per_transaction ). work_mem = 1024 min 64, size in KB maintenance_work_mem = min 1024, size in KB max_stack_depth = 2048 min 100, size in KB - Free Space Map - max_fsm_pages = min max_fsm_relations *16, 6 bytes each max_fsm_relations = 1000 min 100, ~70 bytes each - Kernel Resource Usage - max_files_per_process = 1000 min 25 preload_libraries = - Cost - Based Vacuum Delay - vacuum_cost_delay = milliseconds vacuum_cost_page_hit = credits vacuum_cost_page_miss = credits vacuum_cost_page_dirty = credits vacuum_cost_limit = credits - Background writer - bgwriter_delay = milliseconds between rounds bgwriter_lru_percent = % of LRU buffers scanned/ round bgwriter_lru_maxpages = buffers max written/ round bgwriter_all_percent = % of all buffers scanned/ round bgwriter_all_maxpages = buffers max written/ round

47 41 / 48 WRITE AHEAD LOG Settings - fsync = on turns forced synchronization on or off wal_sync_method = fsync the default is the first option supported by the operating system: open_datasync fdatasync fsync fsync_writethrough open_sync full_page_writes = on recover from partial page writes wal_buffers = 8 min 4, 8KB each commit_delay = 0 range , in microseconds commit_siblings = 5 range Checkpoints - checkpoint_segments = 3 in logfile segments, min 1, 16 MB each checkpoint_timeout = 300 range , in seconds checkpoint_warning = 30 in seconds, 0 is off - Archiving - archive_command = command to use to archive a logfile segment QUERY TUNING Planner Method Configuration - enable_bitmapscan = on enable_hashagg = on enable_hashjoin = on enable_indexscan = on enable_mergejoin = on enable_nestloop = on enable_seqscan = on enable_sort = on enable_tidscan = on - Planner Cost Constants - effective_cache_size = 1000 typically 8KB each random_page_cost = 4 units are one sequential page fetch cost cpu_tuple_cost = 0.01 ( same) cpu_index_tuple_cost = ( same) cpu_operator_cost = ( same) - Genetic Query Optimizer - geqo = on geqo_threshold = 12 geqo_effort = 5 range 1-10 geqo_pool_size = 0 selects default based on effort geqo_generations = 0 selects default based on effort

48 42 / 48 geqo_selection_bias = 2.0 range Other Planner Options - default_statistics_target = 10 range constraint_exclusion = off from_collapse_limit = 8 join_collapse_limit = 8 1 disables collapsing of explicit JOINs ERROR REPORTING AND LOGGING Where to Log - log_destination = stderr Valid values are combinations of stderr, syslog and eventlog, depending on platform. This is used when logging to stderr: redirect_stderr = on Enable capturing of stderr into log files These are only used if redirect_stderr is on: log_directory = pg_log Directory where log files are written Can be absolute or relative to PGDATA log_filename = postgresql -%Y-%m-% d_%h%m%s. log Log file name pattern. Can include strftime () escapes log_truncate_on_rotation = off If on, any existing log file of the same name as the new log file will be truncated rather than appended to. But such truncation only occurs on time - driven rotation, not on restarts or size - driven rotation. Default is off, meaning append to existing files in all cases. log_rotation_age = 1440 Automatic rotation of logfiles will happen after so many minutes. 0 to disable. log_rotation_size = Automatic rotation of logfiles will happen after so many kilobytes of log output. 0 to disable. These are relevant when logging to syslog: syslog_facility = LOCAL0 syslog_ident = postgres - When to Log - client_min_messages = notice Values, in order of decreasing detail: debug5 debug4 debug3 debug2 debug1 log notice warning error

49 43 / 48 log_min_messages = notice Values, in order of decreasing detail: debug5 debug4 debug3 debug2 debug1 info notice warning error log fatal panic log_error_verbosity = default terse, default, or verbose messages log_min_error_statement = panic Values in order of increasing severity : debug5 debug4 debug3 debug2 debug1 info notice warning error panic(off) log_min_duration_statement = -1-1 is disabled, 0 logs all statements and their durations, in milliseconds. silent_mode = off DO NOT USE without syslog or redirect_stderr - What to Log - debug_print_parse = off debug_print_rewritten = off debug_print_plan = off debug_pretty_print = off log_connections = off log_disconnections = off log_duration = off log_line_prefix = Special values: %u = user name %d = database name %r = remote host and port %h = remote host %p = PID %t = timestamp ( no milliseconds ) %m = timestamp with milliseconds %i = command tag %c = session id %l = session line number %s = session start timestamp %x = transaction id %q = stop here in non - session processes %% = % e.g. <%u%%%d> log_statement = none none, mod, ddl, all

50 44 / 48 log_hostname = off RUNTIME STATISTICS Statistics Monitoring - log_parser_stats = off log_planner_stats = off log_executor_stats = off log_statement_stats = off - Query/ Index Statistics Collector - stats_start_collector = on stats_command_string = off stats_block_level = off stats_row_level = off stats_reset_on_server_start = off AUTOVACUUM PARAMETERS autovacuum = off enable autovacuum subprocess? autovacuum_naptime = 60 time between autovacuum runs, in secs autovacuum_vacuum_threshold = 1000 min of tuple updates before vacuum autovacuum_analyze_threshold = 500 min of tuple updates before analyze autovacuum_vacuum_scale_factor = 0.4 fraction of rel size before vacuum autovacuum_analyze_scale_factor = 0.2 fraction of rel size before analyze autovacuum_vacuum_cost_delay = -1 default vacuum cost delay for autovac, -1 means use vacuum_cost_delay autovacuum_vacuum_cost_limit = -1 default vacuum cost limit for autovac, -1 means use vacuum_cost_limit CLIENT CONNECTION DEFAULTS Statement Behavior - search_path = $user, public schema names default_tablespace = a tablespace name, uses the default check_function_bodies = on default_transaction_isolation = read committed default_transaction_read_only = off statement_timeout = 0 0 is disabled, in milliseconds - Locale and Formatting - datestyle = iso, mdy

51 45 / 48 timezone = unknown actually, defaults to TZ environment setting australian_timezones = off extra_float_digits = 0 min -15, max 2 client_encoding = sql_ascii actually, defaults to database encoding These settings are initialized by initdb -- they might be changed lc_messages = fr_fr@euro locale for system error message strings lc_monetary = fr_fr@euro locale for monetary formatting lc_numeric = fr_fr@euro locale for number formatting lc_time = fr_fr@euro locale for time formatting - Other Defaults - explain_pretty_print = on dynamic_library_path = $libdir LOCK MANAGEMENT deadlock_timeout = 1000 in milliseconds max_locks_per_transaction = 64 min 10 note: each lock table slot uses ~220 bytes of shared memory, and there are max_locks_per_transaction * ( max_connections + max_prepared_transactions ) lock table slots VERSION/ PLATFORM COMPATIBILITY Previous Postgres Versions - add_missing_from = off regex_flavor = advanced advanced, extended, or basic sql_inheritance = on default_with_oids = off escape_string_warning = off - Other Platforms & Clients - transform_null_equals = off CUSTOMIZED OPTIONS custom_variable_classes = list of custom variable class names B.3.2 Fichier pour le service Le fichier pour gérer le service /etc/init.d/postgresql est le suivant! /bin/sh

52 46 / 48 chkconfig : description : PostgreSQL RDBMS This is an example of a start/ stop script for SysV - style init, such as is used on Linux systems. You should edit some of the variables and maybe the echo commands. Place this file at / etc/ init.d/ postgresql ( or / etc/ rc.d/ init.d/ postgresql ) and make symlinks to /etc/rc.d/rc0.d/ K02postgresql /etc/rc.d/rc1.d/ K02postgresql /etc/rc.d/rc2.d/ K02postgresql /etc/rc.d/rc3.d/ S98postgresql /etc/rc.d/rc4.d/ S98postgresql /etc/rc.d/rc5.d/ S98postgresql Or, if you have chkconfig, simply: chkconfig -- add postgresql Proper init scripts on Linux systems normally require setting lock and pid files under / var/ run as well as reacting to network settings, so you should treat this with care. Original author: Ryan Kirkpatrick < pgsql@rkirkpat. net > $PostgreSQL : pgsql/ contrib/ start - scripts/ linux,v /10/01 18:30:21 tgl Exp $ EDIT FROM HERE Installation prefix prefix =/ usr/local/pgsql Data directory PGDATA ="/ mnt/pgdata" Who to run the postmaster as, usually " postgres ". ( NOT " root ") PGUSER = postgres Where to keep a log file PGLOG ="/ var/log/pgsql" STOP EDITING HERE Check for echo -n vs echo \c if echo \c grep -s c >/ dev/ null 2 >&1 ; then ECHO_N =" echo -n" ECHO_C ="" else ECHO_N =" echo" ECHO_C = \c fi The path that is to be used for the script PATH =/ usr/local/sbin :/ usr/local/bin :/ sbin :/ bin :/ usr/sbin :/ usr/bin What to use to start up the postmaster ( we do NOT use pg_ctl for this, as it adds no value and can cause the postmaster to misrecognize a stale lock file) DAEMON =" $prefix/bin/ postmaster " What to use to shut down the postmaster PGCTL =" $prefix/bin/pg_ctl"

53 47 / 48 set -e Only start if we can find the postmaster. test -x $DAEMON exit 0 Parse command line parameters. case $1 in start) $ECHO_N " Starting PostgreSQL : " $ECHO_C su - $PGUSER -c " $DAEMON -D $PGDATA &" 2 >&1 echo "ok" ;; stop) echo -n " Stopping PostgreSQL : " su - $PGUSER -c " $PGCTL stop -D $PGDATA -s -m fast" echo "ok" ;; restart) echo -n " Restarting PostgreSQL : " su - $PGUSER -c " $PGCTL stop -D $PGDATA -s -m fast -w" su - $PGUSER -c " $DAEMON -D $PGDATA &" 2 >&1 echo "ok" ;; reload) echo -n " Reload PostgreSQL : " su - $PGUSER -c " $PGCTL reload -D $PGDATA -s" echo "ok" ;; status) su - $PGUSER -c " $PGCTL status -D $PGDATA " ;; *) Print help echo "Usage: $0 {start stop restart reload status }" 1>&2 exit 1 ;; esac exit 0

54 48 / 48 Annexe C Bibliographie C.1 [1] [PostGIS Manual] Paul RAMSEY et Sandro Santilli, PostGIS Manual (http ://postgis.refractions.net), Copyright c 2006 Post- GIS Team. C.2 [2] [Documentation PostgreSQL 8.1.4] "Documentation PostgreSQL / Traduction de Guillaume LELARGE http ://traduc.postgresqlfr.org/pgsql fr", Copyright c The PostgreSQL Global Developmet Group.