From owner-freebsd-current@FreeBSD.ORG Mon May 26 13:29:33 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DDA937B405 for ; Mon, 26 May 2003 13:29:33 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (fump.kawo2.RWTH-Aachen.DE [134.130.181.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id 768FA43F3F for ; Mon, 26 May 2003 13:29:32 -0700 (PDT) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: from fump.kawo2.rwth-aachen.de (localhost.kawo2.rwth-aachen.de [127.0.0.1])h4QKTUj2011705; Mon, 26 May 2003 22:29:30 +0200 (CEST) (envelope-from alex@fump.kawo2.rwth-aachen.de) Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.12.9/8.12.9/Submit) id h4QKTUEe011704; Mon, 26 May 2003 22:29:30 +0200 (CEST) Date: Mon, 26 May 2003 22:29:30 +0200 From: Alexander Langer To: current@FreeBSD.org Message-ID: <20030526202930.GL1170@fump.kawo2.rwth-aachen.de> Mail-Followup-To: Alexander Langer , current@FreeBSD.org, freebsd-rc@yahoogroups.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Fingerprint: 7EC1 5B98 4554 2A63 9079 2B2F 9A94 CD6F 7F14 EFA4 X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. User-Agent: Mutt/1.5.3i cc: freebsd-rc@yahoogroups.com Subject: bootup: no foregroup process group X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 20:29:33 -0000 Hi! After switching from a Mar 24 -CURRENT to a 5.1-BETA -CURRENT, the new rc system or anything else on the bootup is broken. In particular, for the sendmail startup script, which takes minutes due to an unresolveable IP on an interface, pressing Ctrl-T produces "no foreground process group", and Ctrl-C doesn't work either, of course. I haven't tested for other daemons/startup scripts yet, and I just did a fresh mergemaster run to see if it will go away on the next boot, but I thought I might let you know before I forget about it. This defenitely should be fixed for 5.1, if it is really broken. Alex