Mail Archives: cygwin/2009/09/28/11:46:56
Hi,
On Thu, Mar 19, 2009 at 17:36, Julio Emanuel <> wrote:
> Hi Corinna (I think this is with you),
>
> I've been struggling with a small (but deadly) problem in the current
> syslog-ng package:
> ~ $ cygcheck -c syslog-ng
> Cygwin Package Information
> Package =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Version =C2=A0 =
=C2=A0 =C2=A0 =C2=A0Status
> syslog-ng =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A03.0.1-1 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0OK
>
> The service could not be started after running syslog-ng-config,
> complaining like this: "Improperly formatted configuration pragma,
> colon expected; line=3D'@version 3.0\x0a'".
This still happens :(
... and that's normal, because there were no new syslog releases since! :)
The patch (in correct order this time):
~ $ diff -u /usr/bin/syslog-ng-config.old /usr/bin/syslog-ng-config
--- /usr/bin/syslog-ng-config.old 2009-09-28 16:15:27.367887300 +0100
+++ /usr/bin/syslog-ng-config 2009-09-28 16:15:50.197327200 +0100
@@ -205,7 +205,7 @@
then
echo "Creating default ${SYSCONFDIR}/syslog-ng.conf file"
cat > ${SYSCONFDIR}/syslog-ng.conf << EOF
-@version 3.0
+@version: 3.0
options {
keep_hostname(yes);
owner("system");
Could we have a 3.0.1-2, please? Or a 3.0.x whatever. I recall that
there were some other problems, but those related with upstream code.
I'll probably bump into them in the new few hours :(
Also, as a sidenote, It's very disturbing finding that I'm the only
syslog-ng cygwin user in this 6+ months!?
At least I've no other explanation why no one else had problems with
syslog-ng...
--=20
___________
Julio Costa
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -