Résultat de l’API de MediaWiki
Voici la représentation HTML du format JSON. HTML convient au débogage, mais est inapproprié pour être utilisé dans une application.
Spécifiez le paramètre format pour modifier le format de sortie. Pour voir la représentation non HTML du format JSON, mettez format=json.
Voir la documentation complète, ou l’aide de l’API pour plus d’informations.
{
"batchcomplete": "",
"continue": {
"gapcontinue": "TOMCAT",
"continue": "gapcontinue||"
},
"warnings": {
"main": {
"*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
},
"revisions": {
"*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
}
},
"query": {
"pages": {
"27": {
"pageid": 27,
"ns": 0,
"title": "SUBVERSION",
"revisions": [
{
"contentformat": "text/x-wiki",
"contentmodel": "wikitext",
"*": "= Mise en place et configuration de subversion (svn) =\n== Configuration apache ==\n\n <Location /my_svn>\n DAV svn\n SVNPath /repository_svn\n AuthUserFile /etc/apache2/dav_svn.passwd\n \n # To enable authorization via mod_authz_svn\n AuthzSVNAccessFile /etc/apache2/dav_svn.authz\n <LimitExcept GET PROPFIND OPTIONS REPORT>\n </LimitExcept>\n </Location>\n\n== mettre en place des droits==\n* Il est possible de restreindre les acc\u00e8s \u00e0 certaines parties du repository soit en lecture, soit en lecture / \u00e9criture.\n* La gestion des droits se d\u00e9finit dans le fichier suivant :\n /etc/apache2/dav_svn.authz\n\n [groups]\n groupe1 = user1,user2,user3\n groupe2 = user4,user5\n groupe3 = user6,user7\n \n [repository:/project]\n @groupe1 = r\n @groupe2 = rw\n \n [/]\n user1 = r\n @groupe3 = rw\n @groupe2 = r\n\n* la d\u00e9finition des users et de leurs password sont d\u00e9finis dans le fichier suivant:\n /etc/apache2/dav_svn.passwd\n\n\n\n* dump d'un repository\n svnadmin dump\n\n* import d'un dump\n svnadmin create /path/to/repository\n svnadmin load /path/to/repository < dumpfile\n\n\n[[category:syst\u00e8me]]\n[[category:Linux]]"
}
]
},
"41": {
"pageid": 41,
"ns": 0,
"title": "SYSTEMD",
"revisions": [
{
"contentformat": "text/x-wiki",
"contentmodel": "wikitext",
"*": "== systemd c'est quoi ? ==\n* systemd est le rempla\u00e7ant de systemVinit\n* Les scripts dans /etc/init.d deviennent obsol\u00e8tes et le fichier inittab est remplac\u00e9 par /etc/systemd/system/default.target\n\n== Quels sont les avantages ? ==\n* D\u00e9marrage plus rapide car les services d\u00e9marrent en parall\u00e8les\n* les projets systemd et udev sont fusionn\u00e9s mais pour le moment install\u00e9s avec des paquets diff\u00e9rents ---------- system V init\n* Meilleur tra\u00e7abilit\u00e9 sur les erreurs de d\u00e9marrage des services\n\n== Quelques commandes utiles ==\n* systemctl : commande permettant de contr\u00f4ler systemd\n* systemctl {start|stop|reload|restart|status} service\n* systemctl --system daemon-reload : recharge tous les scripts de d\u00e9marrage et recr\u00e9e l'arbre de d\u00e9pendances\n* systemctl reboot\n* systemctl poweroff\n* systemctl list-units : liste les services qui sont activ\u00e9s et affiche leur \u00e9tat\n** Exemple\n UNIT LOAD ACTIVE SUB JOB DESCRIPTION\n proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Autom\n sys-devices-pci0...t2:0:0-2:0:0:0-block-sr0.device loaded active plugged VBOX_CD-ROM\n sys-devices-pci0...00-0000:00:03.0-net-p2p1.device loaded active plugged 82540EM Gigabit Ethernet Controller\n sys-devices-pci0...0000:00:05.0-sound-card0.device loaded active plugged 82801AA AC'97 Audio Controller\n sys-devices-pci0...0-0:0:0:0-block-sda-sda1.device loaded active plugged VBOX_HARDDISK\n sys-devices-pci0...0-0:0:0:0-block-sda-sda2.device loaded active plugged VBOX_HARDDISK\n sys-devices-pci0...t0:0:0-0:0:0:0-block-sda.device loaded active plugged VBOX_HARDDISK\n sys-devices-platform-serial8250-tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0\n sys-devices-platform-serial8250-tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1\n sys-devices-platform-serial8250-tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2\n sys-devices-platform-serial8250-tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3\n sys-devices-virtual-block-dm\\x2d0.device loaded active plugged /sys/devices/virtual/block/dm-0\n sys-devices-virtual-block-dm\\x2d1.device loaded active plugged /sys/devices/virtual/block/dm-1\n sys-module-configfs.device loaded active plugged /sys/module/configfs\n sys-module-fuse.device loaded active plugged /sys/module/fuse\n sys-subsystem-net-devices-p2p1.device loaded active plugged 82540EM Gigabit Ethernet Controller\n -.mount loaded active mounted /\n boot.mount loaded active mounted /boot\n dev-hugepages.mount loaded active mounted Huge Pages File System\n dev-mqueue.mount loaded active mounted POSIX Message Queue File System\n run-user-1000-gvfs.mount loaded active mounted /run/user/1000/gvfs\n sys-fs-fuse-connections.mount loaded active mounted FUSE Control File System\n sys-kernel-config.mount loaded active mounted Configuration File System\n sys-kernel-debug.mount loaded active mounted Debug File System\n rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon\n\n* systemctl status rngd : permet de consult\u00e9 les erreurs de d\u00e9marrage d'un service\n rngd.service - Hardware RNG Entropy Gatherer Daemon\n Loaded: loaded (/usr/lib/systemd/system/rngd.service; enabled)\n Active: failed (Result: exit-code) since Thu, 2013-07-11 14:38:33 CEST; 1h 52min ago\n Main PID: 588 (code=exited, status=1/FAILURE)\n CGroup: name=systemd:/system/rngd.service\n \n Jul 11 14:38:33 chmartin2.ecritel.net systemd[1]: Starting Hardware RNG Entropy Gatherer Daemon...\n Jul 11 14:38:33 chmartin2.ecritel.net systemd[1]: Started Hardware RNG Entropy Gatherer Daemon.\n Jul 11 14:38:33 chmartin2.ecritel.net rngd[588]: Unable to open file: /dev/tpm0\n Jul 11 14:38:33 chmartin2.ecritel.net rngd[588]: can't open any entropy source\n Jul 11 14:38:33 chmartin2.ecritel.net rngd[588]: Maybe RNG device modules are not loaded\n Jul 11 14:38:33 chmartin2.ecritel.net systemd[1]: rngd.service: main process exited, code=exited, status=1/FAILURE\n Jul 11 14:38:33 chmartin2.ecritel.net systemd[1]: Unit rngd.service entered failed state\n\n\n* systemctl list-unit-files : liste les services qui sont activ\u00e9s\n** Exemple\n UNIT FILE STATE\n proc-sys-fs-binfmt_misc.automount static\n dev-hugepages.mount static\n dev-mqueue.mount static\n proc-fs-nfsd.mount static\n proc-sys-fs-binfmt_misc.mount static\n sys-fs-fuse-connections.mount static\n sys-kernel-config.mount static\n sys-kernel-debug.mount static\n tmp.mount static\n var-lib-nfs-rpc_pipefs.mount static\n cups.path enabled\n systemd-ask-password-console.path static\n systemd-ask-password-plymouth.path static\n systemd-ask-password-wall.path static\n abrt-ccpp.service enabled\n abrt-oops.service enabled\n abrt-vmcore.service enabled\n initrd-switch-root.service static\n instperf.service static\n ip6tables.service disabled\n iptables.service disabled\n\n== Emplacement des scripts de d\u00e9marrage des services ==\n* Les scripts de d\u00e9marrage sont situ\u00e9s dans le dossier /usr/lib/systemd/system/\n\n== Les diff\u00e9rents types de fichiers ==\n* Les fichiers avec extension .mount\n** Ces fichiers permettent de monter les \"device\" et point de montage\n* Les fichiers .service\n** Ces fichiers permettent de d\u00e9marrer les services\n* Les fichiers .umount\n* Les fichiers .target\n* Les fichiers .socket\n\n== Comment d\u00e9finir le \"runlevel\" ? ==\n ln -s /lib/systemd/system/multi-user.target /etc/systemd/system/default.target\n ln -s /lib/systemd/system/graphical.target /etc/systemd/system/default.target\n\n== Contenu des scripts de d\u00e9marrage ==\n* Exemple de contenu de script systemd avec ssh\n [Unit]\n Description=OpenSSH server daemon\n After=syslog.target network.target auditd.service\n \n [Service]\n EnvironmentFile=/etc/sysconfig/sshd\n ExecStartPre=/usr/sbin/sshd-keygen\n ExecStart=/usr/sbin/sshd -D $OPTIONS\n ExecReload=/bin/kill -HUP $MAINPID\n KillMode=process\n \n [Install]\n WantedBy=multi-user.target\n\n* Autre exemple avec le script de d\u00e9marrage de MySQL\n [Unit]\n Description=MySQL database server\n After=syslog.target\n After=network.target\n \n [Service]\n Type=simple\n User=mysql\n Group=mysql\n \n ExecStartPre=/usr/libexec/mysqld-prepare-db-dir %n\n # Note: we set --basedir to prevent probes that might trigger SELinux alarms,\n # per bug #547485\n ExecStart=/usr/bin/mysqld_safe --basedir=/usr\n ExecStartPost=/usr/libexec/mysqld-wait-ready $MAINPID\n \n # Give a reasonable amount of time for the server to start up/shut down\n TimeoutSec=300\n \n # Place temp files in a secure directory, not /tmp\n PrivateTmp=true\n \n [Install]\n WantedBy=multi-user.target\n\n== Howto sur systemd ==\n=== Activer un service au boot ===\n* systemctl enable mon_service\n** R\u00e9sultat de la commande sur une fedora :\n ln -s '/usr/lib/systemd/system/mon_service.service' '/etc/systemd/system/multi-user.target.wants/mon_service.service'\n\n=== Comment \u00e9crire un script de d\u00e9marrage ===\n* Exemple pour le lancement de tomcat\n [Unit]\n Description=Tomcat server\n After=syslog.target\n After=network.target\n \n [Service]\n Type=simple\n User=tomcat\n Group=tomcat\n \n ExecStart=/usr/local/tomcat/bin/startup.sh\n ExecStop=/usr/local/tomcat/bin/shutdown.sh\n RemainAfterExit=yes\n \n [Install]\n WantedBy=multi-user.target\n\n=== Options disponible pour les scripts de d\u00e9marrage ===\n* Type = {simple, forking, oneshot, dbus, notify, idle}\n** simple : (c'est la valeur par d\u00e9faut si BusName= n'est pas sp\u00e9cifi\u00e9). le processus lanc\u00e9 par 'ExecStart=' est le processus principal du service\n** forking : le processus lanc\u00e9 par 'ExecStart=' fait appel \u00e0 fork() lors du d\u00e9marrage. il est recommander d'utiliser l'option 'PIDFile=' afin que systemd puisse identifier le processus principal du daemon.\n** oneshot : Le comportement est similaire \u00e0 simple. 'RemainAfterExit=' est utile pour ce type de service.\n** dbus : Le comportement est similaire \u00e0 simple. however it is expected that the daemon acquires a name on the D-Bus bus, as configured by BusName=. systemd will proceed starting follow-up units after the D-Bus bus name has been acquired. Service units with this option configured implicitly gain dependencies on the dbus.socket unit. This type is the default if BusName= is specified.\n** notify : Le comportement est simailaire \u00e0 simple. il s\u2019attend \u00e0 ce que le demon envoie une notification via 'sd_notify(3)' ou \u00e9quivalent \u00e0 la fin du d\u00e9marrage du service.\n** idle : Le comportement est similaire \u00e0 simple, toutefois l'ex\u00e9cution r\u00e9elle du binaire est retard\u00e9e jusqu'a ce que tous les jobs soient termin\u00e9es\n\n* RemainAfterExit = {yes|no}\n** Par d\u00e9faut \u00e0 no, le service peut-\u00eatre consid\u00e9r\u00e9 actif m\u00eame quand le process \u00e0 exit.\n\n* GuessMainPID=\n** Takes a boolean value that specifies whether systemd should try to guess the main PID of a service if it cannot be determined reliably. This option is ignored unless Type=forking is set and PIDFile= is unset because for the other types or with an explicitly configured PID file the main PID is always known. The guessing algorithm might come to incorrect conclusions if a daemon consists of more than one process. If the main PID cannot be determined failure detection and automatic restarting of a service will not work reliably. Defaults to yes.\n\n* PIDFile=\n** Takes an absolute file name pointing to the PID file of this daemon. Use of this option is recommended for services where Type= is set to forking. systemd will read the PID of the main process of the daemon after start-up of the service. systemd will not write to the file configured here.\n\n* BusName=\n** Takes a D-Bus bus name, that this service is reachable as. This option is mandatory for services where Type= is set to dbus, but its use is otherwise recommended as well if the process takes a name on the D-Bus bus.\n\n* ExecStart=\n** Commande avec ses arguments qui sera ex\u00e9cuter lors du d\u00e9marrage du service. le premier argument doit \u00eatre le chemin absolu\n** Si Type =/= onse shot, une seule commande peut-\u00eatre fournie.\n** Si Type=oneshot on peut utiliser plusieurs commandes avec un \"semicolon\". Les commandes seront ex\u00e9cut\u00e9es s\u00e9quentiellement et dans l'ordre de la ligne de commande. Si une commande \u00e9choue, les autres commandes sont ignor\u00e9es et consid\u00e9r\u00e9es en \u00e9chec \u00e0 moins d'utiliser le prefix \"-\".\n** Si on souhaite utilis\u00e9 une commande du shell, il faut pr\u00e9ciser le shell comme dans l'exemple suivant :\n ExecStart=/bin/sh -c 'dmesg | tac'\n\n* ExecStartPre=, ExecStartPost=\n** Additional commands that are executed before or after the command in ExecStart=, respectively. Syntax is the same as for ExecStart=, except that multiple command lines are allowed and the commands are executed one after the other, serially. If any of those commands (not prefixed with \"-\") fail, the rest are not executed and the unit is considered failed.\n\n* ExecReload=\n** Commande \u00e0 ex\u00e9cuter pour effectuer un reload du serivice. Tout comme 'ExecStart=', il peut y avoir plusieurs commandes. Si $MAINPID est connu, on peut utiliser une commande comme celle-ci :\n /bin/kill -HUP $MAINPID\n\n* ExecStop=\n** Commandes \u00e0 ex\u00e9cuter pour arr\u00eater le service qui a \u00e9t\u00e9 d\u00e9marrer par 'ExecStart='. All processes remaining for a service after the commands configured in this option are run are terminated according to the KillMode= setting (see systemd.kill(5)). If this option is not specified the process is terminated right-away when service stop is requested. Specifier and environment variable substitution is supported (including $MAINPID, see above).\n\n* ExecStopPost=\n** \u00c9ventuelles commandes \u00e0 ex\u00e9cuter apr\u00e8s l'arr\u00eat du service. This includes cases where the commands configured in ExecStop= were used, where the service doesn't have any ExecStop= defined, or where the service exited unexpectedly. This argument takes multiple command lines, following the same scheme as described for ExecStart. Use of these settings is optional. Specifier and environment variable substitution is supported.\n\n* RestartSec=\n** Configures the time to sleep before restarting a service (as configured with Restart=). Takes a unit-less value in seconds, or a time span value such as \"5min 20s\". Defaults to 100ms.\n\n* TimeoutStartSec=\n** Configures the time to wait for start-up. If a daemon service does not signal start-up completion within the configured time, the service will be considered failed and be shut down again. Takes a unit-less value in seconds, or a time span value such as \"5min 20s\". Pass 0 to disable the timeout logic. Defaults to 90s, except when Type=oneshot is used in which case the timeout is disabled by default. \n\n* TimeoutStopSec=\n** Configures the time to wait for stop. If a service is asked to stop but does not terminate in the specified time, it will be terminated forcibly via SIGTERM, and after another delay of this time with SIGKILL (See KillMode= in systemd.kill(5)). Takes a unit-less value in seconds, or a time span value such as \"5min 20s\". Pass 0 to disable the timeout logic. Defaults to 90s. \n\n* TimeoutSec=\n** A shorthand for configuring both TimeoutStartSec= and TimeoutStopSec= to the specified value. \n\n* WatchdogSec=\n** Configures the watchdog timeout for a service. The watchdog is activated when the start-up is completed. The service must call sd_notify(3) regularly with \"WATCHDOG=1\" (i.e. the \"keep-alive ping\"). If the time between two such calls is larger than the configured time then the service is placed in a failure state. By setting Restart= to on-failure or always the service will be automatically restarted. The time configured here will be passed to the executed service process in the WATCHDOG_USEC= environment variable. This allows daemons to automatically enable the keep-alive pinging logic if watchdog support is enabled for the service. If this option is used NotifyAccess= (see below) should be set to open access to the notification socket provided by systemd. If NotifyAccess= is not set, it will be implicitly set to main. Defaults to 0, which disables this feature.\n\n* Restart=\n** Peut avoir comme valeur : {no, on-success, on-failure, on-abort, always}\n*** Configures whether the service shall be restarted when the service process exits, is killed, or a timeout is reached. The service process may be the main service process, but also one of the processes specified with ExecStartPre=, ExecStartPost=, ExecStopPre=, ExecStopPost=, or ExecReload=. When the death of the process is a result of systemd operation (e.g. service stop or restart), the service will not be restarted. Timeouts include missing the watchdog \"keep-alive ping\" deadline and a service start, reload, and stop operation timeouts.\nTakes one of no, on-success, on-failure, on-abort, or always. If set to no (the default) the service will not be restarted. If set to on-success it will be restarted only when the service process exits cleanly. In this context, a clean exit means an exit code of 0, or one of the signals SIGHUP, SIGINT, SIGTERM, or SIGPIPE, and additionally, exit statuses and signals specified in SuccessExitStatus=. If set to on-failure the service will be restarted when the process exits with an nonzero exit code, is terminated by a signal (including on core dump), when an operation (such as service reload) times out, and when the configured watchdog timeout is triggered. If set to on-abort the service will be restarted only if the service process exits due to an uncaught signal not specified as a clean exit status. If set to always the service will be restarted regardless whether it exited cleanly or not, got terminated abnormally by a signal or hit a timeout.\nIn addition to the above settings, the service will not be restarted if the exit code or signal is specified in RestartPreventExitStatus= (see below).\n\n* SuccessExitStatus=\n** Takes a list of exit status definitions that when returned by the main service process will be considered successful termination, in addition to the normal successful exit code 0 and the signals SIGHUP, SIGINT, SIGTERM and SIGPIPE. Exit status definitions can either be numeric exit codes or termination signal names, separated by spaces. Example: \"SuccessExitStatus=1 2 8 SIGKILL\", ensures that exit codes 1, 2, 8 and the termination signal SIGKILL are considered clean service terminations. This option may appear more than once in which case the list of successful exit statuses is merged. If the empty string is assigned to this option the list is reset, all prior assignments of this option will have no effect.\n\n* RestartPreventExitStatus=\n** Takes a list of exit status definitions that when returned by the main service process will prevent automatic service restarts regardless of the restart setting configured with Restart=. Exit status definitions can either be numeric exit codes or termination signal names, and are separated by spaces. Defaults to the empty list, so that by default no exit status is excluded from the configured restart logic. Example: \"RestartPreventExitStatus=1 6 SIGABRT\", ensures that exit codes 1 and 6 and the termination signal SIGABRT will not result in automatic service restarting. This option may appear more than once in which case the list of restart preventing statuses is merged. If the empty string is assigned to this option the list is reset, all prior assignments of this option will have no effect.\n\n* PermissionsStartOnly=\n** Takes a boolean argument. If true, the permission related execution options as configured with User= and similar options (see systemd.exec(5) for more information) are only applied to the process started with ExecStart=, and not to the various other ExecStartPre=, ExecStartPost=, ExecReload=, ExecStop=, ExecStopPost= commands. If false, the setting is applied to all configured commands the same way. Defaults to false.\n\n* RootDirectoryStartOnly=\n** Takes a boolean argument. If true, the root directory as configured with the RootDirectory= option (see systemd.exec(5) for more information) is only applied to the process started with ExecStart=, and not to the various other ExecStartPre=, ExecStartPost=, ExecReload=, ExecStop=, ExecStopPost= commands. If false, the setting is applied to all configured commands the same way. Defaults to false.\n\n* NonBlocking=\n** Set O_NONBLOCK flag for all file descriptors passed via socket-based activation. If true, all file descriptors >= 3 (i.e. all except STDIN/STDOUT/STDERR) will have the O_NONBLOCK flag set and hence are in non-blocking mode. This option is only useful in conjunction with a socket unit, as described in systemd.socket(5). Defaults to false.\n\n* NotifyAccess=\n** Controls access to the service status notification socket, as accessible via the sd_notify(3) call. Takes one of none (the default), main or all. If none no daemon status updates are accepted from the service processes, all status update messages are ignored. If main only service updates sent from the main process of the service are accepted. If all all services updates from all members of the service's control group are accepted. This option should be set to open access to the notification socket when using Type=notify or WatchdogSec= (see above). If those options are used but NotifyAccess= not configured it will be implicitly set to main.\n\n* Sockets=\n** Specifies the name of the socket units this service shall inherit the sockets from when the service is started. Normally it should not be necessary to use this setting as all sockets whose unit shares the same name as the service (ignoring the different suffix of course) are passed to the spawned process.\nNote that the same socket may be passed to multiple processes at the same time. Also note that a different service may be activated on incoming traffic than inherits the sockets. Or in other words: the Service= setting of .socket units doesn't have to match the inverse of the Sockets= setting of the .service it refers to.\nThis option may appear more than once, in which case the list of socket units is merged. If the empty string is assigned to this option the list of sockets is reset, all prior uses of this setting will have no effect.\n\n* StartLimitInterval=, StartLimitBurst=\n** Configure service start rate limiting. By default services which are started more often than 5 times within 10s are not permitted to start any more times until the 10s interval ends. With these two options this rate limiting may be modified. Use StartLimitInterval= to configure the checking interval (defaults to 10s, set to 0 to disable any kind of rate limiting). Use StartLimitBurst= to configure how many starts per interval are allowed (defaults to 5). These configuration options are particularly useful in conjunction with Restart=, however apply to all kinds of starts (including manual), not just those triggered by the Restart= logic. Note that units which are configured for Restart= and which reach the start limit are not attempted to be restarted anymore, however they may still be restarted manually at a later point from which point on the restart logic is again activated. Note that systemctl reset-failed will cause the restart rate counter for a service to be flushed, which is useful if the administrator wants to manually start a service and the start limit interferes with that.\n\n* StartLimitAction=\n** Configure the action to take if the rate limit configured with StartLimitInterval= and StartLimitBurst= is hit. Takes one of none, reboot, reboot-force or reboot-immediate. If none is set, hitting the rate limit will trigger no action besides that the start will not be permitted. reboot causes a reboot following the normal shutdown procedure (i.e. equivalent to systemctl reboot), reboot-force causes an forced reboot which will terminate all processes forcibly but should cause no dirty file systems on reboot (i.e. equivalent to systemctl reboot -f) and reboot-immediate causes immediate execution of the reboot(2) system call, which might result in data loss. Defaults to none."
}
]
}
}
}
}