From 070659a33c57ffcd9182749c7c2c74f8cf63d38d Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Tue, 1 Nov 2016 15:58:42 +0100 Subject: document workaround --- open_issues/increasing_bogus_port_at_boot.mdwn | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'open_issues') diff --git a/open_issues/increasing_bogus_port_at_boot.mdwn b/open_issues/increasing_bogus_port_at_boot.mdwn index 9851557c..483b2844 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) -- cgit v1.2.3