summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2016-11-01 15:58:42 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2016-11-01 15:58:42 +0100
commit070659a33c57ffcd9182749c7c2c74f8cf63d38d (patch)
treef13a2735f9dcd62000196353dca0472e92748f14
parent46b09e5063a2580baeeb40348e148c11675c63c4 (diff)
document workaround
-rw-r--r--open_issues/increasing_bogus_port_at_boot.mdwn7
1 files changed, 6 insertions, 1 deletions
diff --git a/open_issues/increasing_bogus_port_at_boot.mdwn b/open_issues/increasing_bogus_port_at_boot.mdwn
index 9851557..483b284 100644
--- a/open_issues/increasing_bogus_port_at_boot.mdwn
+++ b/open_issues/increasing_bogus_port_at_boot.mdwn
@@ -23,4 +23,9 @@ When the ntpdate package is installed, one gets at boot something like:
This is coming from the execution of the shell script
/etc/network/if-up.d/ntpdate, whose stdout/stderr is on the Mach console, but
part of which gets executed after getty starts on it. It happens that getty uses
-revoke() to revoke access to it from other programs, and thus the ntpdate shell scripts gets its stdout/stderr in a bogus state, which libc doesn't really cope with correctly.
+revoke() to revoke access to it from other programs, and thus the ntpdate shell
+scripts gets its stdout/stderr in a bogus state, which libc doesn't really cope
+with correctly.
+
+Commenting `c:23:respawn:/sbin/getty 38400 console` from `/etc/inittab` works
+around the issue (but removes the getty from the Mach console)