Hi, 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 -- 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 "I started using PostgreSQL around a month ago, and the feeling is similar to the switch from Linux to FreeBSD in '96 -- 'wow!'." -- Oddbjorn SteffensenReceived on Fri Sep 07 2007 - 13:35:27 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:17 UTC