Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 21 Dec 2002 12:57:01 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: sshd: setgid() fails on second login Message-ID: <20021221175701.GB22610@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20021218185034 DOT 9606 DOT qmail AT the-means DOT net> <20021218185034 DOT 9606 DOT qmail AT the-means DOT net> <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20021221090526 DOT 0293aca0 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.2.0.9.2.20021221090526.0293aca0@pop3.cris.com> User-Agent: Mutt/1.5.1i On Sat, Dec 21, 2002 at 09:07:48AM -0800, Randall R Schulz wrote: >David, > >Now I'm a big Linux proponent and only currently wed to Windows by a quirk >of my personal employment history, but never did I realize that rebooting a >Linux system would fix a broken disk. > >Those Linux kernel programmers really _are_ miracle workers, aren't they? > >Wow! Just as an added note, Randall, rebooting a windows system would fix a broken disk under Cygwin B20, too. Just FYI. cgf >At 06:28 2002-12-21, David Means wrote: >>Hum... I should have known. A reboot fixed the problem. I suppose that >>what I get for being a Unix geek: you don't _have_ to reboot a unix system >>to fix broken stuff. (unless it's really broken, like disks, etc, etc). -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/