From owner-freebsd-current@FreeBSD.ORG Mon Jul 13 06:33:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A5891065680 for ; Mon, 13 Jul 2009 06:33:18 +0000 (UTC) (envelope-from t.hantzsche@fzd.de) Received: from smtpout.fzd.de (ix2.fz-rossendorf.de [149.220.4.86]) by mx1.freebsd.org (Postfix) with ESMTP id 038CF8FC08 for ; Mon, 13 Jul 2009 06:33:17 +0000 (UTC) (envelope-from t.hantzsche@fzd.de) Received: from localhost (localhost [127.0.0.1]) by smtpout.fzd.de (Postfix) with ESMTP id 392EC937A7 for ; Mon, 13 Jul 2009 08:03:17 +0200 (CEST) Received: from smtpout.fzd.de ([127.0.0.1]) by localhost (ix2 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 11848-04-7 for ; Mon, 13 Jul 2009 08:03:17 +0200 (CEST) Received: from fz-rossendorf.de (cg.fzd.de [149.220.4.66]) by smtpout.fzd.de (Postfix) with ESMTP id F3F0A937A6 for ; Mon, 13 Jul 2009 08:03:16 +0200 (CEST) Received: from phoebe.fz-rossendorf.de ([149.220.39.107] verified) by cg2.fz-rossendorf.de (CommuniGate Pro SMTP 5.2.12) with ESMTPS id 2477781 for freebsd-current@freebsd.org; Mon, 13 Jul 2009 08:03:16 +0200 Date: Mon, 13 Jul 2009 08:03:16 +0200 (CEST) From: Torsten Hantzsche To: freebsd-current@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at fz-rossendorf.de X-Mailman-Approved-At: Mon, 13 Jul 2009 11:24:04 +0000 Subject: CURRENT 8.0-BETA 1: init does not respond to -HUP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Jul 2009 06:33:18 -0000 Does anybody get the same effect? Yesterday I checked out the latest sources of CURRENT 8.0, recompiled the whole system, deleted all Ports completely and reinstalled them again (bash, XOrg, windowmaker, slim). After reinstalling everything I changed in /etc/ttys the line ttyv8 "/usr/local/bin/slim" xterm off secure to ttyv8 "/usr/local/bin/slim" xterm on secure and signalled with 'pkill -1 init' to re-read the config-file. Normally X should be starting now and I can see the Login screen, but init does not react to the signal anymore and seems to stay inactive. After reboot the X-Server and slim starting up correctly. Changing the ttyv8 line now in /etc/ttys back to 'off' and sending init a -HUP also does not work to kill the X-Server. Under 7.2-STABLE (checked out last week) init shows the correct behaviour and reacts to the -HUP signal accordingly. Any ideas? Thanks Torsten