X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Message-ID: <47B8FE55.26B702CC@dessent.net>
Date: Sun, 17 Feb 2008 19:41:09 -0800
From: Brian Dessent <brian@dessent.net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: sshd.log /var/empty must be owned by root and not group or     world-writable.
References: <000601c871cb$4dcadf60$0a00a8c0@a64x23800p> <47B8FC9F.AFC60944@dessent.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Brian Dessent wrote:

> I don't know why running ssh-host-config didn't work, you'd probably
> have to debug that a little more to find out.

It just occured that perhaps /var/empty did not exist the first time
ssh-host-config was run and thus the chown failed, and it was only
created when the sshd tried to start and failed.  If that's the case
then simply having ssh-host-config ensure that the directory exists
before setting ownership seems like the right thing.

Brian

--
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/