diff options
| author | Mattias Andrée <maandree@operamail.com> | 2014-08-12 15:43:27 +0200 |
|---|---|---|
| committer | Mattias Andrée <maandree@operamail.com> | 2014-08-12 15:43:27 +0200 |
| commit | 761076329e62b177fe66ad00ad56c2bdf94e0fa1 (patch) | |
| tree | 55e1e4b8596976edaa09e83f8d735556a605bd22 | |
| parent | fix tabulation (diff) | |
| download | mds-761076329e62b177fe66ad00ad56c2bdf94e0fa1.tar.gz mds-761076329e62b177fe66ad00ad56c2bdf94e0fa1.tar.bz2 mds-761076329e62b177fe66ad00ad56c2bdf94e0fa1.tar.xz | |
typo
Signed-off-by: Mattias Andrée <maandree@operamail.com>
| -rw-r--r-- | README | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -42,7 +42,7 @@ side effects. Servers serialises their state saves it to RAM (in a directory created by the kernel), re-exec themself and loads their serialised state. The kernel cannot do this because when has spawn the master server -it has no reasone to re-exec, its only mission is to +it has no reason to re-exec, its only mission is to respawn the master server it if would happen to crash. It would (probably) technically be possible to enable the kernel to re-exec but it is not worth it as it as |