From owner-freebsd-current@FreeBSD.ORG Wed Sep 12 15:18:45 2007 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 0BC0716A41B for ; Wed, 12 Sep 2007 15:18:45 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 5AF5113C478 for ; Wed, 12 Sep 2007 15:18:44 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id l8CFHKaC086336 for ; Wed, 12 Sep 2007 17:17:28 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id l8CFHK8L086335; Wed, 12 Sep 2007 17:17:20 +0200 (CEST) (envelope-from olli) Date: Wed, 12 Sep 2007 17:17:20 +0200 (CEST) Message-Id: <200709121517.l8CFHK8L086335@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 12 Sep 2007 17:17:28 +0200 (CEST) X-Mailman-Approved-At: Fri, 14 Sep 2007 11:00:11 +0000 Cc: Subject: /libexec/ld-elf.so.1: environment corrupt; missing value for X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Sep 2007 15:18:45 -0000 Hi, (I've already posted this a few days ago, but it didn't seem to get through to the list. I have updated the 7-current machine today, and the problem is still the same.) This started to happen after updating to a recent 7-current about one week ago (it was working fine with a previous 7- current that was a few weeks older). The shell is zsh. zsh$ /usr/bin/su /libexec/ld-elf.so.1: environment corrupt; missing value for zsh$ So su(1) fails to start. Interestingly, when I first start an sh shell, I still get the same error message, but the shell starts anyway. Then I can use su(1) without problems: zsh$ sh sh: environment corrupt; missing value for $ /usr/bin/su Password: It was my impression that there should be more printed in the error message after "missing value for", so I made a hexdump: 6e 67 20 76 61 6c 75 65 20 66 6f 72 20 1b 5b 34 |ng value for .[4| 7e 0a |~.| Sure enough, my environment _does_ seem to be corrupt when I look at the output of env(1): There are several empty lines and some lines with random garbage characters and control characters. However, after starting sh, the garbage is gone. So sh seems to "repair" it somehow. Is this a bug in -current's environment handling? Or is it a bug in zsh that has only been triggered by recent changes in FreeBSD -current? Note that I use exactly the same zsh version and exactly the same zsh start profiles (i.e. basically the same environment contents) on a large number of machines, FreeBSD and other, and this problem _only_ exists on a recent FreeBSD 7-current. Best regards Oliver PS: I'm using zsh's "allexport" option, so all shell variables are automatically exported to the environment. It still isn't very big; "env | wc" reports 2.5 KB. -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Whatever happened to the days when hacking started at the cerebral cortex, and not at the keyboard?" -- Sid on userfriendly.org by Illiad, 2007-06-20