[syslog-ng]RE: Recommended windows event logger products to w ork
with syslog-ng
TUTOLO, Bert
syslog-ng@lists.balabit.hu
Fri, 22 Apr 2005 07:58:09 +1000
Hello,
We are using Snare Agent from http://sourceforge.net/projects/snare/
Cheers,
Bert Tutolo
IOOF Investment Management Ltd.
AFS Licence No 230524
Network Architect/Security Officer
IT Risk and Assurance
03 8614 4612
0417 513 581
-----Original Message-----
From: syslog-ng-admin@lists.balabit.hu
[mailto:syslog-ng-admin@lists.balabit.hu] On Behalf Of Stevan Popovic
Sent: Thursday, 21 April 2005 7:55 PM
To: syslog-ng@lists.balabit.hu
Subject: [syslog-ng]RE: Recommended windows event logger products to work
with syslog-ng
Hello
I have configured syslog-ng to work on my linux box.
I am wondering does anyone use syslog-ng to log windows event logs. If so
which products from the windows side are used?
TIA
-----Original Message-----
From: syslog-ng-request@lists.balabit.hu
[mailto:syslog-ng-request@lists.balabit.hu]
Sent: 19 April 2005 17:06
To: syslog-ng@lists.balabit.hu
Subject: [SPAM] - syslog-ng digest, Vol 1 #1228 - 9 msgs - Email found in
subject
Send syslog-ng mailing list submissions to
syslog-ng@lists.balabit.hu
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.balabit.hu/mailman/listinfo/syslog-ng
or, via email, send a message with subject or body 'help' to
syslog-ng-request@lists.balabit.hu
You can reach the person managing the list at
syslog-ng-admin@lists.balabit.hu
When replying, please edit your Subject line so it is more specific than
"Re: Contents of syslog-ng digest..."
Today's Topics:
1. RE: Re: [syslog-ng]can't compile syslog in HP-UX 11.23
(skywalk2@netian.com)
2. RE: Re: [syslog-ng]can't compile syslog in HP-UX 11.23 (Balazs
Scheidler)
3. Bug: nul chars at end of log lines (W. Borgert)
4. Re: Bug: nul chars at end of log lines (Balazs Scheidler)
5. Re: trouble configuring syslog-ng with libraries (John Thrumston)
6. Re: Bug: nul chars at end of log lines (W. Borgert)
7. Re: trouble configuring syslog-ng with libraries (Balazs Scheidler)
8. Re: trouble configuring syslog-ng with libraries (John Thrumston)
9. RE: Logging Java stack traces with syslog-ng and log4j (Vaibhav Goel)
--__--__--
Message: 1
From: <skywalk2@netian.com>
To: <syslog-ng@lists.balabit.hu>
Subject: RE: Re: [syslog-ng]can't compile syslog in HP-UX 11.23
Date: Tue, 19 Apr 2005 16:00:41 +0900
Reply-To: syslog-ng@lists.balabit.hu
I applied the patch that you submitted, Bazsi But I got many warnings in
'yy__' things when I did 'make'
and also when I did 'make install', I got the same warnings (The binary file
'syslog-ng' was created, but I could'nt start syslog-ng
properly)
For your information,
Before I 've posted my problems on mailing-list in the first time I 've
modified the 'configure' file once (deleted the ' -Wl,-Bstatic'
'-Wl,-Bdynamic' ld options in line 7455 just like below) => LIBS="$LIBS
$LIBOL_LIBS $LEXLIB $LIBWRAP_LIBS $LIBNET_LIBS "
and once I've used 'enable_full_static' option when running 'configure'
In the above two cases, I got the same problems like applying the patch
submitted
Really thanks for your consideration once more, though I 've got another
problems And errors(warnings) are belows
----- warning when running 'make' ---------------
/usr/local/bin/gcc -g -O2 -Wall -I/home/libol-0.3.15/src -D_GNU_SOURCE -
o test_nscache test_nscache.o ../nscache.o -lnsl /home/libol-
0.3.15/src/.libs/libol.a -lnsl -lxnet -ll -lwrap
ld: (Warning) Unsatisfied symbol "yyleng" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yylenguc" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyinput" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyunput" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyolsp" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yytext" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyoutput" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yytextuc" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyextra" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyfnd" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyprevious" in file
/usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yylex" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yylsp" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyout" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "deny_severity" in file
/usr/lib/hpux32/libwrap.so
ld: (Warning) Unsatisfied symbol "allow_severity" in file
/usr/lib/hpux32/libwrap.so
ld: (Warning) Unsatisfied symbol "yylstate" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yytextarr" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyback" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "rfc931_timeout" in file
/usr/lib/hpux32/libwrap.so 20 warnings.
----------- warning when running 'make install' ---------------
Making install in .
/usr/local/bin/gcc -g -O2 -Wall -I/home/libol-0.3.15/src -
D_GNU_SOURCE -o syslog-ng main.o sources.o center.o filters.o
destinations.o log.o cfgfile.o cfg-grammar.o cfg-lex.o affile.o afsocket.o
afunix.o afinet.o afinter.o afuser.o afstreams.o afprogram.o afremctrl.o
nscache.o utils.o syslog-names.o macros.o getopt.o getopt1.o - lnsl
/home/libol-0.3.15/src/.libs/libol.a -lnsl -lxnet -ll -lwrap
ld: (Warning) Unsatisfied symbol "yylenguc" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyinput" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyunput" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyolsp" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyoutput" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yytextuc" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyextra" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyfnd" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyprevious" in file
/usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yylsp" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "deny_severity" in file
/usr/lib/hpux32/libwrap.so
ld: (Warning) Unsatisfied symbol "allow_severity" in file
/usr/lib/hpux32/libwrap.so
ld: (Warning) Unsatisfied symbol "yylstate" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yytextarr" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyback" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "rfc931_timeout" in file
/usr/lib/hpux32/libwrap.so
16 warnings.
/bin/sh /home/syslog-ng-1.6.7/mkinstalldirs /usr/local/sbin
.././install-sh -c syslog-ng /usr/local/sbin/syslog-ng Making install in
tests
/usr/local/bin/gcc -g -O2 -Wall -I/home/libol-0.3.15/src -
D_GNU_SOURCE -o test_nscache test_nscache.o ../nscache.o -lnsl
/home/libol-0.3.15/src/.libs/libol.a -lnsl -lxnet -ll -lwrap
ld: (Warning) Unsatisfied symbol "yyleng" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yylenguc" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyinput" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyunput" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyolsp" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yytext" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyoutput" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yytextuc" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyextra" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyfnd" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyprevious" in file
/usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yylex" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yylsp" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyout" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "deny_severity" in file
/usr/lib/hpux32/libwrap.so
ld: (Warning) Unsatisfied symbol "allow_severity" in file
/usr/lib/hpux32/libwrap.so
ld: (Warning) Unsatisfied symbol "yylstate" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yytextarr" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "yyback" in file /usr/lib/hpux32/libl.so
ld: (Warning) Unsatisfied symbol "rfc931_timeout" in file
/usr/lib/hpux32/libwrap.so 20 warnings.
----------- warning when starting 'syslog-ng' ---------------
# /sbin/init.d/syslog-ng start
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yylsp' in load module
'/usr/lib/hpux32/libl.so.1'.
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yyolsp' in load module
'/usr/lib/hpux32/libl.so.1'.
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yyfnd' in load module
'/usr/lib/hpux32/libl.so.1'.
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yytextuc' in load module
'/usr/lib/hpux32/libl.so.1'.
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yylenguc' in load module
'/usr/lib/hpux32/libl.so.1'.
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yylstate' in load module
'/usr/lib/hpux32/libl.so.1'.
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yyprevious' in load module
'/usr/lib/hpux32/libl.so.1'.
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yytextarr' in load module
'/usr/lib/hpux32/libl.so.1'.
/usr/lib/hpux32/dld.so: Unsatisfied data symbol 'yyextra' in load module
'/usr/lib/hpux32/libl.so.1'.
/sbin/init.d/syslog-ng[89]: 19984 Killed EXIT CODE: 137
-----Original Message-----
From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-
admin@lists.balabit.hu] On Behalf Of Balazs Scheidler
Sent: Monday, April 18, 2005 6:09 PM
To: syslog-ng@lists.balabit.hu
Subject: Re: Re: [syslog-ng]can't compile syslog in HP-UX 11.23
On Mon, 2005-04-18 at 17:26 +0900, XX XXXX wrote:
> Thank You Bazsi for your consideration :) I'll apply it as soon as
> possible
>
> "ld -V" output is as follows
>
> ld: 92453-07 linker ld HP Itanium(R) B.12.23 PBO 040721 (IPF/IPF)
> ld: No input files
> Fatal error.
>
Can you check if applying this patch autodetects you ld options correctly?
--__--__--
Message: 2
Subject: RE: Re: [syslog-ng]can't compile syslog in HP-UX 11.23
From: Balazs Scheidler <bazsi@balabit.hu>
To: syslog-ng@lists.balabit.hu
Date: Tue, 19 Apr 2005 10:28:02 +0200
Reply-To: syslog-ng@lists.balabit.hu
On Tue, 2005-04-19 at 16:00 +0900, skywalk2@netian.com wrote:
> I applied the patch that you submitted, Bazsi But I got many warnings
> in 'yy__' things when I did 'make'
> and also when I did 'make install', I got the same warnings (The
> binary file 'syslog-ng' was created, but I could'nt start syslog-ng
> properly)
>
> For your information,
> Before I 've posted my problems on mailing-list in the first time I
> 've modified the 'configure' file once (deleted the ' -Wl,-Bstatic'
> '-Wl,-Bdynamic' ld options in line 7455 just like below) =>
> LIBS="$LIBS $LIBOL_LIBS $LEXLIB $LIBWRAP_LIBS $LIBNET_LIBS "
>
> and once I've used 'enable_full_static' option when running 'configure'
>
> In the above two cases, I got the same problems like applying the
> patch submitted
>
As I see from the link command line no option was added to it, e.g. it
linked without trying to link statically. This happened either because you
did not rerun the configure script, or not regenerated it using autoconf.
The other problems are that for some reason your libl.so library does not
seem to match the lexing code in syslog-ng.
Although libl.so on other platforms seems to be ok, maybe on HP-UX this is
not the case. Could you try installing GNU flex and verify that syslog-ng
links to libfl.{so,a} instead of libl.so ?
--
Bazsi
--__--__--
Message: 3
Date: Tue, 19 Apr 2005 12:13:03 +0200
From: "W. Borgert" <debacle@debian.org>
To: syslog-ng@lists.balabit.hu
Subject: [syslog-ng]Bug: nul chars at end of log lines
Reply-To: syslog-ng@lists.balabit.hu
Hi,
I reported this on 2004-11-24 as Debian bug against version 1.6.4,
but I'm curious, whether problem is known on other platforms, too.
(See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282782)
A nul character at the end of an UDP transferred log message is
included in the actual syslog file. In the terminal window the
character is shown as ^@. Two problems: It looks ugly and it
makes the file look "binary" to tools such as grep, which does
not print lines anymore, but says "Binary file matches" :-(
A test script to (< 15 lines of code) reproduce the behaviour
can be downloaded from here:
http://bugs.debian.org/cgi-bin/bugreport.cgi/logtest.py?bug=282782&msg=3&att
=1
Don't forget to enable udp() as source, if you run the test.
Cheers, WB
--__--__--
Message: 4
Subject: Re: [syslog-ng]Bug: nul chars at end of log lines
From: Balazs Scheidler <bazsi@balabit.hu>
To: syslog-ng@lists.balabit.hu
Date: Tue, 19 Apr 2005 12:15:55 +0200
Reply-To: syslog-ng@lists.balabit.hu
On Tue, 2005-04-19 at 12:13 +0200, W. Borgert wrote:
> Hi,
>
> I reported this on 2004-11-24 as Debian bug against version 1.6.4,
> but I'm curious, whether problem is known on other platforms, too.
> (See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282782)
>
> A nul character at the end of an UDP transferred log message is
> included in the actual syslog file. In the terminal window the
> character is shown as ^@. Two problems: It looks ugly and it
> makes the file look "binary" to tools such as grep, which does
> not print lines anymore, but says "Binary file matches" :-(
>
> A test script to (< 15 lines of code) reproduce the behaviour
> can be downloaded from here:
>
http://bugs.debian.org/cgi-bin/bugreport.cgi/logtest.py?bug=282782&msg=3&att
=1
>
> Don't forget to enable udp() as source, if you run the test.
This should have already been fixed in 1.6.5
--
Bazsi
--__--__--
Message: 5
Date: Tue, 19 Apr 2005 06:42:10 -0700 (PDT)
From: John Thrumston <john_thrumston@yahoo.com>
Subject: Re: [syslog-ng]trouble configuring syslog-ng with libraries
To: syslog-ng@lists.balabit.hu
Reply-To: syslog-ng@lists.balabit.hu
--0-2016648080-1113918130=:52861
Content-Type: text/plain; charset=us-ascii
I am still having trouble with this. I am working on it. One question I have
that I don't see answered anywhere (maybe I am just blind). But do you have
to run syslog-ng on each server you want to log to the logserver? Is this
something I have to do for each of my machines? I am not sure I completely
understand the process.
Balazs Scheidler <bazsi@balabit.hu> wrote:On Thu, 2005-04-14 at 12:03 -0700,
John Thrumston wrote:
> I tried the ./configure --enable-dynamic-linking as it suggests, got
> the exact same results.
>
> Sunfreeware has a newer version of GLIB (SMCglib-2.6.2 out there.
> My questions are, if I add that package.
> 1) how will the server know which version to use?
> 2. Will this corrupt any other packages that may currently be using
> the SUNWGlib that was installed?
>
> Sorry to ask all these questions, I just don't know library functions
> very well and don't want to blow the box up so to speak.
hm. the configure test checking static glib does not check whether
--enable-dynamic-linking was specified and always errors out.
This patch should fix it:
--- orig/configure.in
+++ mod/configure.in
@@ -113,7 +113,7 @@
blb_cv_static_glib=no)])
LIBS=$old_LIBS
-if test "x$blb_cv_static_glib" = "xno"; then
+if test "x$enable_dynamic_linking" = "xno" -a "x$blb_cv_static_glib" =
"xno"; then
AC_MSG_ERROR([static GLib libraries not found, either link GLib dynamically
using the --enable-dynamic-linking or install a static GLib])
fi
You'll need to regenerate the configure script after patching it
(using autoconf), alternatively you could also comment out this check
from the already generated configure script.
--
Bazsi
_______________________________________________
syslog-ng maillist - syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
---------------------------------
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search. Learn more.
--0-2016648080-1113918130=:52861
Content-Type: text/html; charset=us-ascii
<DIV>I am still having trouble with this. I am working on it. One question I
have that I don't see answered anywhere (maybe I am just blind). But do you
have to run syslog-ng on each server you want to log to the logserver? Is
this something I have to do for each of my machines? I am not sure I
completely understand the process.<BR><BR><B><I>Balazs Scheidler
<bazsi@balabit.hu></I></B> wrote:
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px;
BORDER-LEFT: #1010ff 2px solid">On Thu, 2005-04-14 at 12:03 -0700, John
Thrumston wrote:<BR>> I tried the ./configure --enable-dynamic-linking as
it suggests, got<BR>> the exact same results. <BR>> <BR>>
Sunfreeware has a newer version of GLIB (SMCglib-2.6.2 out there. <BR>>
My questions are, if I add that package. <BR>> 1) how will the server
know which version to use? <BR>> 2. Will this corrupt any other packages
that may currently be using<BR>> the SUNWGlib that was installed?<BR>>
<BR>> Sorry to ask all these questions, I just don't know library
functions<BR>> very well and don't want to blow the box up so to
speak.<BR><BR><BR>hm. the configure test checking static glib does not check
whether<BR>--enable-dynamic-linking was specified and always errors
out.<BR><BR>This patch should fix it:<BR><BR>--- orig/configure.in<BR>+++
mod/configure.in<BR>@@ -113,7 +113,7
@@<BR>blb_cv_static_glib=no)])<BR>LIBS=$old_LIBS<BR><BR>-if test
"x$blb_cv_static_glib" = "xno"; then<BR>+if test "x$enable_dynamic_linking"
= "xno" -a "x$blb_cv_static_glib" = "xno"; then<BR>AC_MSG_ERROR([static GLib
libraries not found, either link GLib dynamically using the
--enable-dynamic-linking or install a static GLib])<BR>fi<BR><BR><BR>You'll
need to regenerate the configure script after patching it <BR>(using
autoconf), alternatively you could also comment out this check<BR>from the
already generated configure script.<BR><BR>--
<BR>Bazsi<BR><BR><BR>_______________________________________________<BR>sysl
og-ng maillist -
syslog-ng@lists.balabit.hu<BR>https://lists.balabit.hu/mailman/listinfo/sysl
og-ng<BR>Frequently asked questions at
http://www.campin.net/syslog-ng/faq.html<BR><BR></BLOCKQUOTE></DIV><p>
<hr size=1>Do you Yahoo!?<br>
Yahoo! Mail - Find what you need with new enhanced search. <a
href="http://us.rd.yahoo.com/evt=29917/*http://info.mail.yahoo.com/mail_250"
>Learn more.</a>
--0-2016648080-1113918130=:52861--
--__--__--
Message: 6
Date: Tue, 19 Apr 2005 15:55:21 +0200
From: "W. Borgert" <debacle@debian.org>
To: syslog-ng@lists.balabit.hu
Subject: [syslog-ng]Re: Bug: nul chars at end of log lines
Reply-To: syslog-ng@lists.balabit.hu
On Tue, 19 Apr 2005 12:15:55 +0200, Balazs Scheidler wrote:
> This should have already been fixed in 1.6.5
I tried my test script and I can still see the nul char :-(
Debian GNU/Linux "sarge", syslog-ng version 1.6.5-2. Could
you please try this on your system? Thanks in advance!
Cheers, WB
--__--__--
Message: 7
Subject: Re: [syslog-ng]trouble configuring syslog-ng with libraries
From: Balazs Scheidler <bazsi@balabit.hu>
To: syslog-ng@lists.balabit.hu
Date: Tue, 19 Apr 2005 16:31:06 +0200
Reply-To: syslog-ng@lists.balabit.hu
On Tue, 2005-04-19 at 06:42 -0700, John Thrumston wrote:
> I am still having trouble with this. I am working on it. One question
> I have that I don't see answered anywhere (maybe I am just blind). But
> do you have to run syslog-ng on each server you want to log to the
> logserver? Is this something I have to do for each of my machines? I
> am not sure I completely understand the process.
not necessarily, syslog-ng supports the good old UDP based syslog
protocol.
one minor note: if you are not that experienced you might want to stick
to a stable release (currently 1.6.7) and not a BETA grade software like
1.9.4 is.
--
Bazsi
--__--__--
Message: 8
Date: Tue, 19 Apr 2005 08:28:42 -0700 (PDT)
From: John Thrumston <john_thrumston@yahoo.com>
Subject: Re: [syslog-ng]trouble configuring syslog-ng with libraries
To: syslog-ng@lists.balabit.hu
Reply-To: syslog-ng@lists.balabit.hu
--0-1852989970-1113924522=:91452
Content-Type: text/plain; charset=us-ascii
I have done just that, I have version 1.6.5 put when I try and configure it,
it tells me that it found libol 0.3.14 and tells me
checking libol version >= 0.3.14... configure: error: libol-config not found
in the specified location.
So I tried the ./configure --with-libol=/usr/local/lib and that still gave
me the same result.
not sure what to do now.
Balazs Scheidler <bazsi@balabit.hu> wrote:
On Tue, 2005-04-19 at 06:42 -0700, John Thrumston wrote:
> I am still having trouble with this. I am working on it. One question
> I have that I don't see answered anywhere (maybe I am just blind). But
> do you have to run syslog-ng on each server you want to log to the
> logserver? Is this something I have to do for each of my machines? I
> am not sure I completely understand the process.
not necessarily, syslog-ng supports the good old UDP based syslog
protocol.
one minor note: if you are not that experienced you might want to stick
to a stable release (currently 1.6.7) and not a BETA grade software like
1.9.4 is.
--
Bazsi
_______________________________________________
syslog-ng maillist - syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--0-1852989970-1113924522=:91452
Content-Type: text/html; charset=us-ascii
<DIV>I have done just that, I have version 1.6.5 put when I try and
configure it, it tells me that it found libol 0.3.14 and tells me</DIV>
<DIV>checking libol version >= 0.3.14... configure: error: libol-config
not found in the specified location.</DIV>
<DIV>So I tried the ./configure --with-libol=/usr/local/lib and that
still gave me the same result.</DIV>
<DIV> </DIV>
<DIV>not sure what to do now.<BR><BR><B><I>Balazs Scheidler
<bazsi@balabit.hu></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px;
BORDER-LEFT: #1010ff 2px solid">On Tue, 2005-04-19 at 06:42 -0700, John
Thrumston wrote:<BR>> I am still having trouble with this. I am working
on it. One question<BR>> I have that I don't see answered anywhere (maybe
I am just blind). But<BR>> do you have to run syslog-ng on each server
you want to log to the<BR>> logserver? Is this something I have to do for
each of my machines? I<BR>> am not sure I completely understand the
process.<BR><BR>not necessarily, syslog-ng supports the good old UDP based
syslog<BR>protocol.<BR><BR>one minor note: if you are not that experienced
you might want to stick<BR>to a stable release (currently 1.6.7) and not a
BETA grade software like<BR>1.9.4 is.<BR><BR>--
<BR>Bazsi<BR><BR><BR>_______________________________________________<BR>sysl
og-ng maillist -
syslog-ng@lists.balabit.hu<BR>https://lists.balabit.hu/mailman/listinfo/sysl
og-ng<BR>Frequently asked questio
ns at
http://www.campin.net/syslog-ng/faq.html<BR><BR></BLOCKQUOTE><p>____________
______________________________________<br>Do You Yahoo!?<br>Tired of spam?
Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com
--0-1852989970-1113924522=:91452--
--__--__--
Message: 9
Subject: RE: [syslog-ng]Logging Java stack traces with syslog-ng and log4j
Date: Tue, 19 Apr 2005 09:05:36 -0700
From: "Vaibhav Goel" <vgoel@cucbc.com>
To: <syslog-ng@lists.balabit.hu>
Reply-To: syslog-ng@lists.balabit.hu
DQpZZXMgdGhlIHN0YWNrIHRyYWNlIGlzIG11bHRpcGxlIGxpbmVzLiAgV2UgYXJlIGFjdHVhbGx5
IHVzaW5nIGxvZzRqIHRvIGxvZyB0aGUgdHJhY2VzIGxvY2FsbHkgYXMgd2VsbCBhcyBvdmVyIGEg
Y3VzdG9tIFRDUCBhcHBlbmRlciB3aGljaCBob29rcyB1cCB0byBzeXNsb2ctbmcgYW5kIHNlbmRz
IHRoZSBsb2dzIHRvIHRoZSBsb2dob3N0LiAgVGhpcyBpcyBob3cgSSB3YXMgYWJsZSB0byBmaW5k
IHRoZSBwcm9ibGVtLiAgVGhlIGV4Y2VwdGlvbiBlcnJvciBzaG93ZWQgdXAgb24gYm90aCB0aGUg
bG9jYWwgbG9nIGFzIHdlbGwgYXMgdGhlIHN5c2xvZy1uZyBwcm9kdWNlZCBsb2cgYnV0IHN0YWNr
IHRyYWNlIGFmdGVyIHRoZSBlcnJvciBkaWQgbm90IHNob3cgdXAgKGFzIHlvdSBtZW50aW9uZWQg
c3lzbG9nLW5nIHNob3VsZCBtYXRjaCBlYWNoIGFuZCBldmVyeSBsaW5lKS4gIEkgZG8gaGF2ZSBs
b2dzdXJmZXIgb24gdGhlIGFwcCBzZXJ2ZXIgaG93ZXZlciBJIGRvbuKAmXQgdGhpbmsgSSB3b3Vs
ZCBrbm93IHRoZSBpbml0aWFsIGxpbmUgb2YgdGhlIHN0YWNrIHRyYWNlIHNpbmNlIGl0cyBhcmJp
cnRyYXJ5IGRlcGVuZGluZyBvbiB0aGUgZXJyb3IuDQoNCkkgaGVhciB5YSBvbiB0aGUgU1RET1VU
IG5ld2xpbmUgaXNzdWUuICBJIHRoaW5rIEkgZGlkIHJ1biBpbnRvIHRoYXQgb25jZSB3aGVyZSBJ
IHdhcyBmZWVkaW5nIHN0ZGluIGZyb20gc3lzbG9nLW5nIHRvIGEgcGVybCBzY3JpcHQuLi4NCg0K
DQpUaGFua3MsDQoNClZhaWJoYXYgR29lbA0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IHN5c2xvZy1uZy1hZG1pbkBsaXN0cy5iYWxhYml0Lmh1IFttYWlsdG86c3lzbG9nLW5nLWFk
bWluQGxpc3RzLmJhbGFiaXQuaHVdIE9uIEJlaGFsZiBPZiBVTklYIEFkbWluDQpTZW50OiBBcHJp
bCAxOCwgMjAwNSA5OjQ0IFBNDQpUbzogc3lzbG9nLW5nQGxpc3RzLmJhbGFiaXQuaHUNClN1Ympl
Y3Q6IFJlOiBbc3lzbG9nLW5nXUxvZ2dpbmcgSmF2YSBzdGFjayB0cmFjZXMgd2l0aCBzeXNsb2ct
bmcgYW5kIGxvZzRqDQoNClRoZSBqYXZhIHN0YWNrIHRyYWNlIGlzIG11bHRpcGxlIGxpbmVzLCBy
aWdodD8gU3lzbG9nIG1lc3NhZ2VzIGFyZQ0Kc2luZ2xlIGxpbmVzIC0gYW5kIHNvIHN5c2xvZy1u
ZydzIGZpbHRlcnMgbWF0Y2ggb25lIGxpbmUgYXQgYSB0aW1lLg0KDQpZb3UgbmVlZCB0byBtYXRj
aCBlYWNoIGFuZCBldmVyeSBsaW5lIG9yIGp1c3QgaGF2ZSB0aGUgamF2YSBhcHAgbG9nIHRvDQph
IGZpbGUgYW5kIHBhcnNlIGl0LiBJZiB5b3UgaGF2ZSBzd2F0Y2ggb3IgbG9nc3VyZmVyIG9yIFNF
QyBvcg0Kc29tZXRoaW5nIHRoZSB5b3UgY2FuIHByb2JhYmx5IHNlZSB0aGUgaW5pdGlhbCBsaW5l
IG9mIHRoZSBzdGFjayB0cmFjZQ0KYW5kIGFuZCBsb29rIGZvciB0aGUgcmVzdCBvZiB0aGUgbWVz
c2FnZSBhbmQgc2VuZCB0aGUgd2hvbGUgdGhpbmcgdmlhDQplbWFpbC9zbm1wIHRyYXAvcGFnZXIv
bW9uIHRyYXAvd2hhdGV2ZXIuDQoNCkFyZSB5b3UganVzdCBmZWVkaW5nIFNURE9VVCBvZiB0aGUg
YXBwIHNlcnZlciBpbnRvIGxvZ2dlciBvcg0Kc29tZXRoaW5nPyBJIGhvcGUgaXQgZG9lc24ndCBz
ZW5kIG1lc3NhZ2VzIHdpdGggbmV3bGluZXMgaW4gdGhlbSBpbnRvDQpvcGVubG9nKCkvc3lzbG9n
KCkuIEkgaGF0ZSB3aGVuIHRoYXQgaGFwcGVucywgYnV0IGNyYXBweSBsb2dzIGFyZQ0KYmV0dGVy
IHRoYW4gbm8gbG9ncywgSSBhbHdheXMgc2F5LiA7KQ0KDQpPbiA0LzE4LzA1LCBWYWliaGF2IEdv
ZWwgPHZnb2VsQGN1Y2JjLmNvbT4gd3JvdGU6DQo+ICANCj4gIA0KPiANCj4gSGkgYWxsIA0KPiAN
Cj4gICANCj4gDQo+IEkgYW0gdHJ5aW5nIHRvIGdldCBzeXNsb2ctbmcgdG8gbG9nIGEgamF2YSBz
dGFjayB0cmFjZSBzdWNoIGFzIG9uZSBzaG93bg0KPiBiZWxvdy4gDQo+IA0KPiAgIA0KPiANCj4g
UFNUOjIwMDUtMDMtMTUvMTA6NDY6NDkuNjU3IFtFeGVjdXRlVGhyZWFkOiAnMjMnIGZvciBxdWV1
ZToNCj4gJ3dlYmxvZ2ljLmtlcm5lbC5EZWZhdWx0J10gTE9HRVJST1INCj4gandzbS5jb20uY3Vj
YmMudGFnbGliLmNvbnRlbnQuSW5jbHVkZVRhZ0NvbnRlbnQgLS0NCj4gU2VydmxldEV4Y2UgDQo+
IA0KPiBwdGlvbiBvbiBpbmNsdWRlIHRhZyANCj4gDQo+IGphdmF4LnNlcnZsZXQuU2VydmxldEV4
Y2VwdGlvbjogR290IGVycm9yOiA0MDQgDQo+IA0KPiAgICAgICAgIGF0DQo+IGNvbS5jdWNiYy5z
ZXJ2bGV0LlNpbXBsZU1EUmVxdWVzdERpc3BhdGNoZXIuaGFuZGxlRXJyb3IoU2ltcGxlTURSZXF1
ZXN0RGlzcGF0Y2hlci5qYXZhOjcyKQ0KPiANCj4gICAgICAgICBhdA0KPiBjb20uY3VjYmMuc2Vy
dmxldC5BYnN0cmFjdE1EUmVxdWVzdERpc3BhdGNoZXIuY2hlY2tGb3JFcnJvcihBYnN0cmFjdE1E
UmVxdWVzdERpc3BhdGNoZXIuamF2YTo4NykNCj4gDQo+ICAgICAgICAgYXQNCj4gY29tLmN1Y2Jj
LnNlcnZsZXQuQWJzdHJhY3RNRFJlcXVlc3REaXNwYXRjaGVyLmluY2x1ZGUoQWJzdHJhY3RNRFJl
cXVlc3REaXNwYXRjaGVyLmphdmE6NzEpDQo+IA0KPiAgICAgICAgIGF0DQo+IGNvbS5jdWNiYy50
YWdsaWIuY29udGVudC5JbmNsdWRlVGFnQ29udGVudC53cml0ZShJbmNsdWRlVGFnLmphdmE6MTM3
KQ0KPiANCj4gICAgICAgICBhdA0KPiBjb20uY3VjYmMudGFnbGliLmNvbnRlbnQuQ29udGVudFRh
Z1N1cHBvcnQuZG9FbmRUYWcoQ29udGVudFRhZ1N1cHBvcnQuamF2YTo1MikNCj4gDQo+ICAgICAg
ICAgYXQNCj4ganNwX3NlcnZsZXQuX3BlcnNvbmFsLl9faW5kZXguX2pzcFNlcnZpY2UoaW5kZXgu
anNwOjYzKSANCj4gDQo+ICAgICAgICAgYXQNCj4gd2VibG9naWMuc2VydmxldC5qc3AuSnNwQmFz
ZS5zZXJ2aWNlKEpzcEJhc2UuamF2YTozMykgDQo+IA0KPiAgICAgICAgIGF0DQo+IHdlYmxvZ2lj
LnNlcnZsZXQuaW50ZXJuYWwuU2VydmxldFN0dWJJbXBsJFNlcnZsZXRJbnZvY2F0aW9uQWN0aW9u
LnJ1bihTZXJ2bGV0U3R1YkltcGwuamF2YTo5OTYpDQo+IA0KPiAgICAgICAgIGV0Y+KApiANCj4g
DQo+ICAgDQo+IA0KPiBJIGhhdmUgYSBmaWx0ZXIgbWF0Y2ggIkxPR0VSUk9SIiBjb25maWd1cmVk
IGZvciBzeXNsb2ctbmcuICBJdCBtYXRjaGVzIGZpbmUNCj4gYW5kIGxvZ3MgdGhlIGxpbmU6IA0K
PiANCj4gUFNUOjIwMDUtMDMtMTUvMTA6NDY6NDkuNjU3IFtFeGVjdXRlVGhyZWFkOiAnMjMnIGZv
ciBxdWV1ZToNCj4gJ3dlYmxvZ2ljLmtlcm5lbC5EZWZhdWx0J10gTE9HRVJST1INCj4gandzbS5j
b20uY3VjYmMudGFnbGliLmNvbnRlbnQuSW5jbHVkZVRhZ0NvbnRlbnQgLS0NCj4gU2VydmxldEV4
Y2UgDQo+IA0KPiBwdGlvbiBvbiBpbmNsdWRlIHRhZyANCj4gDQo+ICAgDQo+IA0KPiBIb3dldmVy
LCB0aGUgc3RhY2sgdHJhY2UgYWZ0ZXIgdGhhdCBpcyBpZ25vcmVk4oCmLiANCj4gDQo+ICAgDQo+
IA0KPiBBbnkgd2F5IHRvIGdldCB0aGF0PyAgSSBndWVzcyBhIHJlZ2V4cCBtYXRjaCBvbiBMT0dF
UlJPUiBpcyBvdXQgb2YgdGhlDQo+IHF1ZXN0aW9u4oCmIA0KPiANCj4gICANCj4gDQo+IFRoYW5r
cw0KwrMrJcKiCcOg4oSiwqjCpeKAkystwrMrJcKiCcOg4oCTKy3CscK2wqVpwrjCreKAoMOobcK2
4oC6P8O+WMKswrbDhsOa4oCiwqbDosK2G8K/4oSiwqjCpeKEosKpw7/igJMrLcWgd8Oow77DjMKs
4oCTy4Yn4oKsWsOewqrDp8KnwrZcxaHCskfCncKqw6fCrMK2KifCscKrYcK2w5p/w78NCjBxwqnC
qcWgecOewrfDuzLCslogxb4Pw59qwqhtDQoNCg==
--__--__--
_______________________________________________
syslog-ng maillist - syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
End of syslog-ng Digest
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/
This message (including any attachments and/or related materials) is
confidential to, copyright by, and is the property of Nikken UK Limited,
unless otherwise noted. If you are not the intended recipient, you should
delete this message and are hereby notified that any disclosure, copying, or
distribution of this message, or the taking of any action based on it, is
strictly prohibited.
_______________________________________________
syslog-ng maillist - syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
****************************************************************************
IMPORTANT - PLEASE READ
This communication is intended only for the use of the addressee and
may contain personal information, confidential information or legally
privileged information. If personal information is contained in this e-mail,
then it is governed by the Privacy Act 1988 and must be treated in
accordance with the Privacy Act 1988 by the recipient. The legal
privilege and confidentiality attached to this e-mail is not waivered,
lost or destroyed by reason of mistaken delivery to you. If you are not
the intended recipient, we would appreciate immediate notification by
return e-mail or telephoning +61-3-8614-4444 and ask that the message
be permanently deleted from your system. If you are the intended
recipient of this communication you should not copy, disclose or distribute
this communication without the authority of IOOF or its related entities
(the IOOF Group).
Any views expressed in this message are those of the individual sender,
except where they are specifically stated to be the views of the IOOF
Group.
This e-mail and any attachments have been scanned for computer viruses
using anti-viral software, but you should also perform your own scan. We
do not accept liability for any loss or damage, whether caused by our own
negligence or not, that results from a computer virus or a defect in the
transmission of the e-mail or any attached file.
****************************************************************************