X-Spam-Check-By:	sourceware.org
Message-ID:	<9a6449f40708071419o94b8968m46447ab2630af18f@mail.gmail.com>
Date:	Tue, 7 Aug 2007 17:19:24 -0400
From:	"Joel Harrison" <harr2969 AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: sshd not working on nineteen w2k servers (/var/empty must be owned by root) works on five win2k servers, works with svc acct and works on w2k3
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Im still unsure of your exact process here, but It is my understanding
that sshd needs to be able to access /var/empty and /var/log. so if
you want ssd to run as a service as a user account other than the
system account, /var/log and /var/empty need to be accessible by that
user as well.

Im not exactly sure why though, I have no idea what /var/empty is
supposed to be for or what it does.
------------------

I don't actually want to use a service account, I would much rather
localsystem work out of the box. I've simply documented the process
that works around what seems to be broken "out of the box" (on most of
my servers) in the fewest steps possible.

--Joel

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -