Date: Thu, 18 Oct 2007 10:49:05 +0300 From: Stefan Lambrev <stefan.lambrev@moneybookers.com> To: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= <askbill@conducive.net> Cc: freebsd-current@freebsd.org Subject: Re: Broken su in current - trying to fix myself, help needed! Message-ID: <47170FF1.3050602@moneybookers.com> In-Reply-To: <471667DB.1010601@conducive.net> References: <00bd01c810ec$10371230$0c00a8c0@Artem> <8cb6106e0710171143m3dff7546o457192ede76e6598@mail.gmail.com> <012c01c810f3$aafeecf0$0c00a8c0@Artem> <20071017193615.GO9006@server.vk2pj.dyndns.org> <471667DB.1010601@conducive.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
=E9=9F=93=E5=AE=B6=E6=A8=99 Bill Hacker wrote:
> Peter Jeremy wrote:
>> On Wed, Oct 17, 2007 at 11:26:48PM +0400, Artem Kuchin wrote:
>>> I have rerun all configs and started jails - still works. Then i=20
>>> remembered
>>> that i have always run this script fro midnight commander.
>>> Started mc
>>> Pressed ENTER on this script and it got suspended.
>>>
>>> Now i am lost, whose problem is this? su's or mc's? or both?
>>> If i remove su from the script and run simply
>>> system('echo heck');
>>> from mc it work fine. With su it gets suspended.
>>
>> This bug (or another one with identical symptoms) affects the 'su'
>> commands within the ports build system if you are using tcsh or zsh
>> and maybe related to the gdb-with-tcsh problems that have been
>> reported. It appeared in -current in the middle of 2006. The
>> suggestions to date have been that there's something wrong with the
>> signal handling in the kernel but you have opened a new line of attack=
=2E
>>
>
> It doesn't seem to 'bite' when invoking a build from a 'seat' using=20
> bash or csh or sh.
>
> Keeping in mind that scripting WITIHIN Makefiles always has its own=20
> specification as to which shell is wanted, I wouldn't expect it to=20
> matter.
> Unless the sh and csh binaries have been removed or over-written?
>
> If someone can tell me which ports exhibit the alleged problem, I'll=20
> try it and see what happens (no 5.X, but otherwise have 4.11 thru=20
> 8-CURRENT ready to hand)..
>
> I will not be surprised if it occurs when building as an 'ordinary=20
> user' and does NOT occur when building as root....
>
> BNL (BSD's Not Linux)....
>
> Bill
>
>
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to=20
> "freebsd-current-unsubscribe@freebsd.org"
I see something similar on all ports that have OPTIONS (make config).
Here is example (do this as user member of wheel, but not root):
#cd /usr/ports/misc/mc
#make config
=3D=3D=3D> Switching to root credentials to create /var/db/ports/mc
=3D=3D=3D> Returning to user credentials
zsh: suspended (tty output) make config
FreeBSD 7.0-CURRENT #5: Fri Oct 5 14:05:56 EEST 2007
On FreeBSD-6 everything works fine.
--=20
Best Wishes,
Stefan Lambrev
ICQ# 24134177
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47170FF1.3050602>