This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: logon failure from subauth in 2006-08-02 snapshot
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 10 Aug 2006 09:21:30 +0200
- Subject: Re: logon failure from subauth in 2006-08-02 snapshot
- References: <20060809183753.GA2940@tela.daveroth.dyndns.org>
- Reply-to: cygwin at cygwin dot com
On Aug 9 11:37, David Rothenberger wrote:
> I've noticed repeated logon failures in my Security event log with
> the 2006-08-02 snapshot. (I have security auditing enabled.)
>
> It looks like these failures occur when cron runs a job. I attached
> strace to cron and saw the following:
>
> 2315 31545159 [main] CRON 4164 subauth: LsaLogonUser: -1073741702
> 2072 31547231 [main] CRON 4164 seterrno_from_win_error: /netrel/src/cygwin-snapshot-20060802-1/winsup/cygwin/security.cc:1067 windows error 127
> 686 31547917 [main] CRON 4164 geterrno_from_win_error: windows error 127 == errno 3
>
> I'm not sure whether this is expected behavior or not. It does fill
> up the Security event log pretty quick, though.
It's expected behaviour if you didn't set up subauthentication.
There's nothing I can do about this at this point. I've noted it
on my TODO list to look into at one point. As usual, PTC.
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/