Différences
Ci-dessous, les différences entre deux révisions de la page.
maxime:openbsd:manpages-fr:8:init [2008/08/31 22:27] 90.2.170.8 |
maxime:openbsd:manpages-fr:8:init [2014/02/17 00:16] |
||
---|---|---|---|
Ligne 1: | Ligne 1: | ||
- | INIT(8) | ||
- | |||
- | ===== NOM ===== | ||
- | **init** - systeme de gestion d' | ||
- | |||
- | ===== RESUME ===== | ||
- | **init** [**-fs**] | ||
- | |||
- | ===== DESCRIPTION ===== | ||
- | Le programme **init** est la derniere etape du processus de boot. Ça | ||
- | execute normallement la sequence des evenements decrite dans [[: | ||
- | et si cela reussis, les operation multi-utilisateur commencent. Si le script | ||
- | de boot echoue, init demarre les operations en simple-utilisateur pour | ||
- | donner au superutilisateur un shell sur la console. | ||
- | Le programme **init** peut être passé en paramètre à partir du programme | ||
- | de boot pour prévenir le fait que le systeme passe en multiutilisateur et | ||
- | pour, à la place, éxecuter un invité de commande simple utilisateur sans | ||
- | initialiser les démons normaux. | ||
- | |||
- | Les paramètres suivant peuvent être passé depuis le programme de | ||
- | démarrage : | ||
- | |||
- | **-f** | ||
- | |||
- | **-s** | ||
- | |||
- | The system is then quiescent for maintenance work and may later be made | ||
- | to go to multi-user by exiting the single-user shell (with ^D). This | ||
- | causes init to run the /etc/rc startup command file in fastboot mode | ||
- | (skipping disk checks). | ||
- | |||
- | If the console entry in the [[: | ||
- | flag, then init will require that the superuser password be entered be- | ||
- | fore the system will start a single-user shell. | ||
- | skipped if the console is marked as ``secure'' | ||
- | The kernel [[: | ||
- | and raised to 1 when the system begins multi-user operations. | ||
- | tion will not take place if the securelevel is -1, and can be modified | ||
- | via the / | ||
- | |||
- | In multi-user operation, init maintains processes for the terminal ports | ||
- | found in the file [[: | ||
- | mand found in the second field. | ||
- | opens and initializes the tty line and executes the login program. | ||
- | login program, when a valid user logs in, executes a shell for that user. | ||
- | When this shell dies, either because the user logged out or an abnormal | ||
- | termination occurred (a signal), the init program wakes up, deletes the | ||
- | user from the [[: | ||
- | wtmp file. The cycle is then restarted by init executing a new getty for | ||
- | the line. | ||
- | |||
- | Line status (on, off, secure, getty, or window information) may be | ||
- | changed in the ttys file without a reboot by sending the signal SIGHUP to | ||
- | init with the command ``kill -s HUP 1'' | ||
- | re-reads the ttys file. When a line is turned off in ttys, init will | ||
- | send a SIGHUP signal to the controlling process for the session associat- | ||
- | ed with the line. For any lines that were previously turned off in the | ||
- | ttys file and are now on, init executes a new getty to enable a new lo- | ||
- | gin. If the getty or window field for a line is changed, the change | ||
- | takes effect at the end of the current login session (e.g., the next time | ||
- | init starts a process on the line). | ||
- | ed from ttys, init will not do anything at all to that line. However, it | ||
- | will complain that the relationship between lines in the ttys file and | ||
- | records in the utmp file is out of sync, so this practice is not recom- | ||
- | mended. | ||
- | |||
- | **init** will terminate multi-user operations and resume single-user mode if | ||
- | sent a terminate (TERM) signal, for example, ``kill -s TERM 1'' | ||
- | there are processes outstanding that are deadlocked (because of hardware | ||
- | or software failure), init will not wait for them all to die (which might | ||
- | take forever), but will time out after 30 seconds and print a warning | ||
- | message. | ||
- | |||
- | **init** will cease creating new [[: | ||
- | away, if it is sent a terminal stop (TSTP) signal, i.e., ``kill -s TSTP | ||
- | 1'' | ||
- | nate will start a single-user shell. | ||
- | [[: | ||
- | |||
- | **init** will terminate multi-user operations, kill all [[: | ||
- | / | ||
- | user-defined signal 2 is received. | ||
- | powerdown is requested. | ||
- | erdown. | ||
- | |||
- | The role of init is so critical that if it dies, the system will reboot | ||
- | itself automatically. | ||
- | located, the system will panic with the message ``panic: init died | ||
- | (signal %d, exit %d)'' | ||
- | |||
- | ===== RESSOURCES ===== | ||
- | When init spawns a process it sets the process priority, umask, and re- | ||
- | source limits based on / | ||
- | the login class ``daemon'' | ||
- | [[: | ||
- | made when entering single user mode. | ||
- | |||
- | ===== FICHIERS ===== | ||
- | / | ||
- | |||
- | / | ||
- | |||
- | / | ||
- | |||
- | / | ||
- | |||
- | / | ||
- | |||
- | / | ||
- | |||
- | / | ||
- | |||
- | / | ||
- | |||
- | / | ||
- | |||
- | ===== DIAGNOSTICS ===== | ||
- | getty repeating too quickly on port %s, sleeping | ||
- | to service a line is exiting quickly each time it is started. | ||
- | often caused by a ringing or noisy terminal line. Init will sleep for 10 | ||
- | seconds, then continue trying to start the process. | ||
- | |||
- | some processes would not die; ps axl advised. | ||
- | could not be killed when the system was shutting down. This condition is | ||
- | usually caused by a process that is stuck in a device driver because of a | ||
- | persistent device error condition. | ||
- | |||
- | ===== VOIR AUSSI ===== | ||
- | [[: | ||
- | [[: | ||
- | [[: | ||
- | |||
- | ===== HISTORIQUE ===== | ||
- | Une commande init est apparue dans la version 6 de l'UNIX d' | ||
- | |||
- | OpenBSD 4.4 24 août 2008 2 | ||