X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20090319182945.GA9322@calimero.vinschen.de> References: <20090319182945 DOT GA9322 AT calimero DOT vinschen DOT de> Date: Thu, 19 Mar 2009 23:49:10 +0000 Message-ID: Subject: Re: syslog-ng: some packaging glitches From: Julio Emanuel To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 Thu, Mar 19, 2009 at 18:29, Corinna Vinschen wrote: > On Mar 19 16:36, Julio Emanuel wrote: >> Hi Corinna (I think this is with you), > > Nevertheless, this is the wrong mailing list. =C2=A0Next time, please rep= ort > problems always to the cygwin AT cygwin dot com ML, except you're a > package maintainer or you're providing code to setup.exe. =C2=A0Thanks. > Ooops. Sorry for the noise. And the funny thing is, I told myself two or three times to not forget to check the correct list. Things happen! :) >> >> ...to put the 'lost colon' back in place in the first line written to >> the syslog-ng.conf :) > > The patch seems to be reverted, but I see. Ooops (again). But you got the point. I think you have that mind-reading capability... :) > =C2=A0I'll update that and send > the patch upstream. =C2=A0Thanks. > >> Now, for the part I didn't manage to solve yet: the syslog-ng service >> also spits this warning (error?) when starting: "Error resolving user; >> user=3D'system'", but I have the 'vanilla' system entry in /etc/passwd: >> ~ $ grep system /etc/passwd >> system:*:18:544:,S-1-5-18:: >> and indeed all does seem well: >> ~ $ id system >> uid=3D18(system) gid=3D544(Administrators) groups=3D544(Administrators) >> >> Is it any misleading message, maybe? > > Is the /etc/syslog-ng.conf file owned by the system user? > ~ $ ls -l /etc/syslog-ng.conf -rw-r--r--+ 1 security Domain Users 1171 Mar 19 16:07 /etc/syslog-ng.conf No it isn't. it is owned by an admin user named 'security' . Should be owned by system? Note that the default config contains the lines owner("SYSTEM"); group("root"); perm(0660); that defines the default ownership and mode of created files. But this IS working: ~ $ ls -l /var/log/*messages -rw-rw---- 1 system root 1854 Mar 19 23:28 /var/log/20090319_messages And so this error message (from /var/log/syslog-ng.log) seems to be misleading... Is there anything I can do to help hunting down the root cause (if there is a need to do so)? >> And finally, the most wanted (at the moment): The man page refers >> 'NOTE: This file is not up to date. Please refer to the html >> documentation'. Looking at >> ~ $ cygcheck -l syslog-ng >> /usr/sbin/syslog-ng.exe >> /usr/bin/loggen.exe >> /usr/bin/syslog-ng-config >> /usr/share/man/man5/syslog-ng.conf.5 >> /usr/share/man/man8/syslog-ng.8 >> /usr/share/doc/syslog-ng/syslog-ng.conf.sample >> /usr/share/doc/syslog-ng/syslog-ng.conf.solaris >> /usr/share/doc/Cygwin/syslog-ng.README >> >> Hrmmm... where is it? > > Not available, sorry. =C2=A0The HTML documentation was not part of the > upstream package, so I couldn't provide it. =C2=A0I'm not even sure the > documentation for the 3.0 series is finshed yet. > Hm, I see. After a bit of research, here it is a link for anyone who might be asking for documentation: http://www.balabit.com/dl/guides/syslog-ng-v3.0-guide-admin-en.pdf The html version is also there, but it is an ugly conversion. Thanks for the help! __________ Julio Costa -- 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/