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:	<200309291203.h8TC3gEj083538@crag.niss.com>
From:	Scott Bolte <listS+cygwin AT niss DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: does syslog works only for SYSTEM account on w2k?
MIME-Version:	1.0
Date:	Mon, 29 Sep 2003 07:03:42 -0500

> 
> > It seems like cygwin syslog on w2k, both the logger command the
> > syslog(3) routine, works only for the SYSTEM account. Is that true?
> 
> No.  Perhaps the users privileges don't allow that?  Members of the
> group "Users" (or the native analogon) have the appropriate permissions
> by default.

	I expect my test user has sufficient privileges.  It is
	in groups None, Administrators, Power Users, and User.

	I guess I'll try to learn more about the internals of w2k,
	more then I ever wanted to know, starting with ReportEventA().

	Unfortunately my configure of cygwin-1.5.5-1 died looking
	for an errant install-sh. In case my w2k environment is
	insufficient to build cygwin from scratch, could you add a
	check of return code from ReportEventA()? That might shed
	light on the problem.

		Thank you,

		   Scott




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