Date: Tue, 25 Jun 2002 19:52:43 -0400 From: Alexander Kabaev <kabaev@bellatlantic.net> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: current@FreeBSD.ORG Subject: Re: su gets SIGHUP randomly on startup with latest current Message-ID: <20020625195243.6a655c8a.kabaev@bellatlantic.net> In-Reply-To: <200206252327.g5PNR05U051967@apollo.backplane.com> References: <20020625071455.GA42940@calvin.in.ibm.com> <20020625081225.GC21301@CPE0030ab0ef2bb.cpe.net.cable.rogers.com> <3D18CE39.CC63442E@mindspring.com> <200206252327.g5PNR05U051967@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matt, the problem is not new. Dag-Erling committed su.c rev 1.51 to fix the problem with su taking signals instead of its children and his fix has this unfortunate side effect you are seeing. I proposed a different patch, which does not have unwanted side-effects and which I am using for at leat one year now. Please see current@freebsd.org archives for a thread "zsh exits upon ^C after su'ing to root with zsh as its shell". It took place somewhen at the end of the May. -- Alexander Kabaev P.S. As usual, my home email sucks, so there is a good chance that this mail will not be delivered :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020625195243.6a655c8a.kabaev>