X-Spam-Check-By: sourceware.org Date: Thu, 23 Feb 2006 18:26:44 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Snapshot report - ssh error Message-ID: <20060223172644.GG4294@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20060223111631 DOT GB31794 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Feb 23 08:54, Karl M wrote: > Hi All... > > It was a permissions problem with /var/run/utmp. > > But that got me looking...back in Nov 2003, Corinna made the following > change to ssh-host-config > [...] > And I am curious why set the permissions to 777 on /var/log/lastlog if it > is a directory? Because /var/log/lastlog can be a directory. In this case sshd creates files under /var/log/lastlog directory with the name of the user and each file only contains logininfo records for that user. We're just missing a lastlog tool which allows examining the lastlog file(s). It's part of the pwdutils package from http://www.thkukuk.de/pam/pwdutils/ *hint, hint* Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/