Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<5.2.0.9.2.20021221090526.0293aca0@pop3.cris.com>
X-Sender:	rrschulz AT pop3 DOT cris DOT com
Date:	Sat, 21 Dec 2002 09:07:48 -0800
To:	cygwin AT cygwin DOT com
From:	Randall R Schulz <rrschulz AT cris DOT com>
Subject:	Re: sshd: setgid() fails on second login
In-Reply-To:	<1040480924.20802.4.camel@milo>
References:	<20021218185034 DOT 9606 DOT qmail AT the-means DOT net>
	<20021218185034 DOT 9606 DOT qmail AT the-means DOT net>
Mime-Version:	1.0

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!

Randall Schulz


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/

- Raw text -