Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-Id: <200309282016.h8SKGsEj028807@crag.niss.com>
From: Scott Bolte <listS+cygwin AT niss DOT com>
To: cygwin AT cygwin DOT com
Subject: does syslog works only for SYSTEM account on w2k?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28805 DOT 1064780214 DOT 1 AT crag DOT niss DOT com>
Date: Sun, 28 Sep 2003 15:16:54 -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?

I have a test script that uses logger. When I call it manually no messages
appear in the event log. When I turn it into a service, where it is invoked
with SYSTEM privileges, the test messages make it into the event log.

FYI: my goal is to interleave status messages from concurrently running
perl scripts into a single log file where the entries are sorted by
generation time. The NT event log will be fine, I can extract my
messages via a separate perl script, but I don't want to turn these
scripts into services

Here's my configuration and test information:
	- Cygwin DLL version 1.5.5-1
	- OS w2k SP4
	- environment variable CYGWIN=ntsec
	- test script (sltest.bat):

		@echo off
		echo  ---
		echo  ---
		echo  ---
		echo Running the syslog logger test
		D:\cygwin\bin\date
		D:\cygwin\bin\logger testing
		D:\cygwin\bin\id
		D:\cygwin\bin\printenv
		D:\cygwin\bin\sleep 5
		rem vim: fileformat=dos

	- Command to create the service:
		cygrunsrv --install sltest -p ~/sltest.bat --type auto
	- Command to start the service:
		cygrunsrv --start sltest

Btw, google searches, and searches of the cygwin archives, failed to enlighten
me wrt any SYSTEM constraint.

	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/