From rgerhards at hq.adiscon.com Wed Jun 1 11:37:24 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Wed, 1 Jun 2005 11:37:24 +0200 Subject: [rsyslog] syslogd and rsyslogd together Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0621D4@grfint2.intern.adiscon.com> Sorry for the sluggish response. I am a bit overwhelmed at the moment, my mailbox needs a desperate cleanup ;) rsyslogd is intended as a syslogd replacement. As such, it does *NOT* play nice together with stock syslogd. And, yes, rsyslogd binds to port 514/UDP by default. It does so by querying etc/services, which unfortuantely makes it hard to change this default easily. I'll add this to the todo list... Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Tuesday, May 31, 2005 8:44 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] syslogd and rsyslogd together > > Syslogd and rsyslogd didn't seem to play well together on my > system. I had some debugging output, but I don't recall > precisely what it said and I didn't save it. I didn't think > rsyslogd would bind to 514 by default, would it? I think I > will try and reenact the scenario. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Wed Jun 1 14:25:06 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Wed, 1 Jun 2005 07:25:06 -0500 Subject: [rsyslog] sluggish response Message-ID: <001001c566a4$f25e4060$0366a8c0@d> No problemo. Take your time. Frankly, I don't care about syslogd and rsyslogd coexisting. I've got rsyslogd logging everything to my MySQL database now so I'm happy as a clam. I hope the information I compiled helps with tidying up the code a bit. I was wondering about maybe getting this program into the FreeBSD ports tree. As of yet, I still have no boot-time solution. When that's taken care of, I'd like to take a crack at porting it if that's OK with you. Never done anything like this before though. Maybe you prefer to port it personally? But, whatever... I'm diggin' it. From dennisolvany at gmail.com Sun Jun 5 13:13:52 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Sun, 5 Jun 2005 06:13:52 -0500 Subject: [rsyslog] man pages Message-ID: <000a01c569bf$a8d10db0$0366a8c0@d> I was thinking that an incredibly intelligent move would be to publish the man pages on the website. I was trying to get msyslog up and running and the entire documentation was on the man pages, which I could not access because the FreeBSD port did not install them and , of course, they were not available on the site. Lo and behold, I never got msyslog running. It also provides alot of information concerning the complexity of the application and helps people decide if the application will be suitable for their needs. I personally shy away from most software that doesn't offer good support on the website because that's where I go for support. Man pages are difficult to read on the CLI. The web offers a much friendlier interface. From rgerhards at hq.adiscon.com Mon Jun 6 09:06:07 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 6 Jun 2005 09:06:07 +0200 Subject: [rsyslog] man pages Message-ID: <577465F99B41C842AAFBE9ED71E70ABA06223E@grfint2.intern.adiscon.com> Dennis, excellent idea. I'll see that I get them online today (obviously a fairly easy task) ;) All web page updates are done on a staging system and the content is moved nightly. So the update will not appear before tomorrow, just in case you wonder ;) Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Sunday, June 05, 2005 1:14 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] man pages > > I was thinking that an incredibly intelligent move would be > to publish the man pages on the website. I was trying to get > msyslog up and running and the entire documentation was on > the man pages, which I could not access because the FreeBSD > port did not install them and , of course, they were not > available on the site. Lo and behold, I never got msyslog > running. It also provides alot of information concerning the > complexity of the application and helps people decide if the > application will be suitable for their needs. I personally > shy away from most software that doesn't offer good support > on the website because that's where I go for support. Man > pages are difficult to read on the CLI. The web offers a much > friendlier interface. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From rgerhards at hq.adiscon.com Wed Jun 22 18:20:27 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Wed, 22 Jun 2005 18:20:27 +0200 Subject: [rsyslog] rsyslog 0.9.0 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA062374@grfint2.intern.adiscon.com> Hi, Rsyslog 0.9.0 has been released today. It now supports log files larger than 2gb (where supported by OS & file system) and the ability to specify the maximum size for log files. If a log grows larger, a rotation script (or something similiar) can automatically be called from within rsyslog. Also, 0.9.0 includes some minor changes which are in preparation for upcoming major ones. See the changelog for details. So far, 0.9.0 has been compiled and tested on Red Hat and Debian, BSD tests are outstanding. You can obtain the latest release from http://www.monitorware.com/rsyslog/ I hope it is helpful. Feedback please address to the list. Rainer Gerhards Adiscon From dennisolvany at gmail.com Mon Jun 27 17:01:26 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 10:01:26 -0500 Subject: [rsyslog] rsyslog 0.9.0 released References: <577465F99B41C842AAFBE9ED71E70ABA062374@grfint2.intern.adiscon.com> Message-ID: <000d01c57b29$18209030$0366a8c0@d> The links at http://www.monitorware.com/rsyslog/ still point to 0.8.4. From rgerhards at hq.adiscon.com Mon Jun 27 17:13:10 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 17:13:10 +0200 Subject: [rsyslog] rsyslog 0.9.0 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA06239A@grfint2.intern.adiscon.com> Oops... sorry, I forgot to update the download link at the top. The URL for 0.9.0 is http://download.adiscon.com/rsyslog-0.9.0.tar.gz I will change the web, but it will propagate only tonight... Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Monday, June 27, 2005 5:01 PM > To: rsyslog at lists.adiscon.com > Subject: Re: [rsyslog] rsyslog 0.9.0 released > > The links at http://www.monitorware.com/rsyslog/ still point to 0.8.4. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Mon Jun 27 17:33:58 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 10:33:58 -0500 Subject: [rsyslog] FreeBSD: Linux Compatibility Message-ID: <000a01c57b2d$a3786b90$0366a8c0@d> Does rsyslog require Linux Binary Compatibility under FreeBSD? From dennisolvany at gmail.com Mon Jun 27 17:50:23 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 10:50:23 -0500 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties on FreeBSD 5.4 Message-ID: <001701c57b2f$ee50a8b0$0366a8c0@d> FreeBSD 5.4 fresh install. No Linux Binary Compatibility. mysql41-client Configured Makefile lines 15, 16, 24. Fixed syslogd.c: line 184: #include "/usr/local/include/mysql/mysql.h" line 185: #include "/usr/local/include/mysql/errmsg.h" Make output: test# make gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c syslogd.c syslogd.c: In function `writeFile': syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) syslogd.c: At top level: syslogd.c:4633: warning: 'allocate_log' defined but not used gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -c pidfile.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c template.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c stringbuf.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c srUtils.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c outchannel.c In file included from outchannel.c:21: outchannel.h:11: error: syntax error before "off_t" outchannel.c:110: error: syntax error before "off_t" outchannel.c: In function `get_off_t': outchannel.c:113: error: syntax error before "val" outchannel.c:115: error: `pp' undeclared (first use in this function) outchannel.c:115: error: (Each undeclared identifier is reported only once outchannel.c:115: error: for each function it appears in.) outchannel.c:117: error: `pOff_t' undeclared (first use in this function) outchannel.c:122: error: `val' undeclared (first use in this function) outchannel.c: In function `ochAddLine': outchannel.c:205: error: structure has no member named `uSizeLimit' outchannel.c: In function `ochPrintList': outchannel.c:267: error: structure has no member named `uSizeLimit' *** Error code 1 Stop in /usr/home/dennisolvany/rsyslog-0.9.0. test# From rgerhards at hq.adiscon.com Mon Jun 27 17:58:45 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 17:58:45 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties on FreeBSD 5.4 In-Reply-To: <001701c57b2f$ee50a8b0$0366a8c0@d> References: <001701c57b2f$ee50a8b0$0366a8c0@d> Message-ID: <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> ahh... This is the large file support. Seems to be different on FreeBSD. As a quick fix, compile with -DNOLARGEFILE in the c options in makefile. This will disable it. I hope I can fire up FreeBSD tomorrow and see how to do it there. Rainer On Mon, 2005-06-27 at 17:50, Dennis Olvany wrote: > FreeBSD 5.4 fresh install. > No Linux Binary Compatibility. > mysql41-client > > Configured Makefile lines 15, 16, 24. > > Fixed syslogd.c: > line 184: #include "/usr/local/include/mysql/mysql.h" > line 185: #include "/usr/local/include/mysql/errmsg.h" > > Make output: > test# make > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c syslogd.c > syslogd.c: In function `writeFile': > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) > syslogd.c: At top level: > syslogd.c:4633: warning: 'allocate_log' defined but not used > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -c pidfile.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c template.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c stringbuf.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c srUtils.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c outchannel.c > In file included from outchannel.c:21: > outchannel.h:11: error: syntax error before "off_t" > outchannel.c:110: error: syntax error before "off_t" > outchannel.c: In function `get_off_t': > outchannel.c:113: error: syntax error before "val" > outchannel.c:115: error: `pp' undeclared (first use in this function) > outchannel.c:115: error: (Each undeclared identifier is reported only once > outchannel.c:115: error: for each function it appears in.) > outchannel.c:117: error: `pOff_t' undeclared (first use in this function) > outchannel.c:122: error: `val' undeclared (first use in this function) > outchannel.c: In function `ochAddLine': > outchannel.c:205: error: structure has no member named `uSizeLimit' > outchannel.c: In function `ochPrintList': > outchannel.c:267: error: structure has no member named `uSizeLimit' > *** Error code 1 > > Stop in /usr/home/dennisolvany/rsyslog-0.9.0. > test# > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog From dennisolvany at gmail.com Mon Jun 27 18:09:37 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 11:09:37 -0500 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD 5.4 References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> Message-ID: <003b01c57b32$9e356d90$0366a8c0@d> I'm not sure which are the c options in the Makefile. # Makefile for rsyslog CC= gcc #CFLAGS= -g -DSYSV -Wall # Add the -DMTRACE macro if you would like to use mtrace() # to hunt for memory leaks # next 2 lines are debug settings #LDFLAGS= -g -Wall -fno-omit-frame-pointer #CFLAGS= -DSYSV -g -Wall -fno-omit-frame-pointer # the next two lines are essentially the same, but -DWITH_DB # enables the MySQL code. By default, that one is commented out # change the comment chars to activate it if you need MySQL! # In this case, also look down further to uncomment the libs #CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB LDFLAGS= -s INSTALL = install BINDIR = /usr/sbin MANDIR = /usr/share/man # Uncomment the following to use mysql. LIBS = -lmysqlclient #/var/lib/mysql/mysql # There is one report that under an all ELF system there may be a need to # explicilty link with libresolv.a. If linking syslogd fails you may wish # to try uncommenting the following define. # LIBS = /usr/lib/libresolv.a # The following define determines whether the package adheres to the # file system standard. FSSTND = -DFSSTND # The following define establishes ownership for the man pages. # Avery tells me that there is a difference between Debian and # Slackware. Rather than choose sides I am leaving it up to the user. MAN_OWNER = root # MAN_OWNER = man # The following define establishes the name of the pid file for the # rsyslogd daemon. The library include file (paths.h) defines the # name for the rsyslogd pid to be rsyslog.pid. A number of people have # suggested that this should be rsyslogd.pid. You may cast your # ballot below. SYSLOGD_PIDNAME = -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" SYSLOGD_FLAGS= -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS ${FSSTND} \ ${SYSLOGD_PIDNAME} SYSLOG_FLAGS= -DALLOW_KERNEL_LOGGING DEB = .c.o: ${CC} ${CFLAGS} -c $*.c all: syslogd test: syslog_tst tsyslogd install: install_man install_exec syslogd: syslogd.o pidfile.o template.o stringbuf.o srUtils.o outchannel.o ${CC} ${LDFLAGS} -o syslogd syslogd.o pidfile.o template.o outchannel.o stringbuf.o srUtils.o ${LIBS} syslog_tst: syslog_tst.o ${CC} ${LDFLAGS} -o syslog_tst syslog_tst.o tsyslogd: syslogd.c version.h template.o outchannel.o stringbuf.o srUtils.o $(CC) $(CFLAGS) -g -DTESTING $(SYSLOGD_FLAGS) -o tsyslogd syslogd.c pidfile.o template.o outchannel.o stringbuf.o srUtils.o $(LIBS) srUtils.o: srUtils.c srUtils.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c srUtils.c stringbuf.o: stringbuf.c stringbuf.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c stringbuf.c template.o: template.c template.h stringbuf.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c template.c outchannel.o: outchannel.c outchannel.h stringbuf.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c outchannel.c syslogd.o: syslogd.c version.h template.h outchannel.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c syslogd.c syslog.o: syslog.c ${CC} ${CFLAGS} ${SYSLOG_FLAGS} -c syslog.c syslog_tst.o: syslog_tst.c ${CC} ${CFLAGS} -c syslog_tst.c clean: rm -f *.o *.log *~ *.orig clobber: clean rm -f syslogd klogd ksym syslog_tst oops_test TAGS tsyslogd tklogd install_exec: syslogd ${INSTALL} -b -s syslogd ${DESTDIR}${BINDIR}/rsyslogd install_man: ${INSTALL} rsyslogd.8 ${DESTDIR}${MANDIR}/man8/rsyslogd.8 ${INSTALL} rsyslog.conf.5 ${DESTDIR}${MANDIR}/man5/rsyslog.conf.5 test# From rgerhards at hq.adiscon.com Mon Jun 27 18:17:23 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 18:17:23 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD 5.4 In-Reply-To: <003b01c57b32$9e356d90$0366a8c0@d> References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> <003b01c57b32$9e356d90$0366a8c0@d> Message-ID: <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> Dennis, I've fired up a FreeBSD and now see it is a more subtle issue. Bear a little with me, I guess there is even a problem on Linux, which you simply do not notice ;) Rainer On Mon, 2005-06-27 at 18:09, Dennis Olvany wrote: > I'm not sure which are the c options in the Makefile. > > > # Makefile for rsyslog > > CC= gcc > #CFLAGS= -g -DSYSV -Wall > # Add the -DMTRACE macro if you would like to use mtrace() > # to hunt for memory leaks > # next 2 lines are debug settings > #LDFLAGS= -g -Wall -fno-omit-frame-pointer > #CFLAGS= -DSYSV -g -Wall -fno-omit-frame-pointer > > # the next two lines are essentially the same, but -DWITH_DB > # enables the MySQL code. By default, that one is commented out > # change the comment chars to activate it if you need MySQL! > # In this case, also look down further to uncomment the libs > #CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce > CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB > LDFLAGS= -s > > INSTALL = install > BINDIR = /usr/sbin > MANDIR = /usr/share/man > > # Uncomment the following to use mysql. > LIBS = -lmysqlclient #/var/lib/mysql/mysql > > # There is one report that under an all ELF system there may be a need to > # explicilty link with libresolv.a. If linking syslogd fails you may wish > # to try uncommenting the following define. > # LIBS = /usr/lib/libresolv.a > > # The following define determines whether the package adheres to the > # file system standard. > FSSTND = -DFSSTND > > # The following define establishes ownership for the man pages. > # Avery tells me that there is a difference between Debian and > # Slackware. Rather than choose sides I am leaving it up to the user. > MAN_OWNER = root > # MAN_OWNER = man > > # The following define establishes the name of the pid file for the > # rsyslogd daemon. The library include file (paths.h) defines the > # name for the rsyslogd pid to be rsyslog.pid. A number of people have > # suggested that this should be rsyslogd.pid. You may cast your > # ballot below. > SYSLOGD_PIDNAME = -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" > > SYSLOGD_FLAGS= -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS ${FSSTND} \ > ${SYSLOGD_PIDNAME} > SYSLOG_FLAGS= -DALLOW_KERNEL_LOGGING > DEB = > > .c.o: > ${CC} ${CFLAGS} -c $*.c > > all: syslogd > > test: syslog_tst tsyslogd > > install: install_man install_exec > > syslogd: syslogd.o pidfile.o template.o stringbuf.o srUtils.o outchannel.o > ${CC} ${LDFLAGS} -o syslogd syslogd.o pidfile.o template.o outchannel.o stringbuf.o srUtils.o ${LIBS} > > syslog_tst: syslog_tst.o > ${CC} ${LDFLAGS} -o syslog_tst syslog_tst.o > > tsyslogd: syslogd.c version.h template.o outchannel.o stringbuf.o srUtils.o > $(CC) $(CFLAGS) -g -DTESTING $(SYSLOGD_FLAGS) -o tsyslogd syslogd.c pidfile.o template.o outchannel.o stringbuf.o srUtils.o $(LIBS) > > srUtils.o: srUtils.c srUtils.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c srUtils.c > > stringbuf.o: stringbuf.c stringbuf.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c stringbuf.c > > template.o: template.c template.h stringbuf.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c template.c > > outchannel.o: outchannel.c outchannel.h stringbuf.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c outchannel.c > > syslogd.o: syslogd.c version.h template.h outchannel.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c syslogd.c > > syslog.o: syslog.c > ${CC} ${CFLAGS} ${SYSLOG_FLAGS} -c syslog.c > > syslog_tst.o: syslog_tst.c > ${CC} ${CFLAGS} -c syslog_tst.c > > clean: > rm -f *.o *.log *~ *.orig > > clobber: clean > rm -f syslogd klogd ksym syslog_tst oops_test TAGS tsyslogd tklogd > > install_exec: syslogd > ${INSTALL} -b -s syslogd ${DESTDIR}${BINDIR}/rsyslogd > > install_man: > ${INSTALL} rsyslogd.8 ${DESTDIR}${MANDIR}/man8/rsyslogd.8 > ${INSTALL} rsyslog.conf.5 ${DESTDIR}${MANDIR}/man5/rsyslog.conf.5 > test# > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog From rgerhards at hq.adiscon.com Mon Jun 27 18:23:45 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 18:23:45 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD 5.4 In-Reply-To: <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> <003b01c57b32$9e356d90$0366a8c0@d> <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> Message-ID: <1119889425.2097.7.camel@rh9lt.intern.adiscon.com> Dennis, OK, for a quick fix... Add this to the top of outchannel.c: #ifndef NOLARGEFILE # define _GNU_SOURCE # define _LARGEFILE_SOURCE # define _LARGEFILE64_SOURCE # define _FILE_OFFSET_BITS 64 #endif then, add #include after stdio.h in outchannel.c. Alternatively, you can obtain the latest CVS snapshot from sourceforge that includes the fix. Its quick and dirty, I'll go over it in more depth tomorrow. Rainer On Mon, 2005-06-27 at 18:17, Rainer Gerhards wrote: > Dennis, > > I've fired up a FreeBSD and now see it is a more subtle issue. Bear a > little with me, I guess there is even a problem on Linux, which you > simply do not notice ;) > > Rainer > > On Mon, 2005-06-27 at 18:09, Dennis Olvany wrote: > > I'm not sure which are the c options in the Makefile. > > > > > > # Makefile for rsyslog > > > > CC= gcc > > #CFLAGS= -g -DSYSV -Wall > > # Add the -DMTRACE macro if you would like to use mtrace() > > # to hunt for memory leaks > > # next 2 lines are debug settings > > #LDFLAGS= -g -Wall -fno-omit-frame-pointer > > #CFLAGS= -DSYSV -g -Wall -fno-omit-frame-pointer > > > > # the next two lines are essentially the same, but -DWITH_DB > > # enables the MySQL code. By default, that one is commented out > > # change the comment chars to activate it if you need MySQL! > > # In this case, also look down further to uncomment the libs > > #CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce > > CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB > > LDFLAGS= -s > > > > INSTALL = install > > BINDIR = /usr/sbin > > MANDIR = /usr/share/man > > > > # Uncomment the following to use mysql. > > LIBS = -lmysqlclient #/var/lib/mysql/mysql > > > > # There is one report that under an all ELF system there may be a need to > > # explicilty link with libresolv.a. If linking syslogd fails you may wish > > # to try uncommenting the following define. > > # LIBS = /usr/lib/libresolv.a > > > > # The following define determines whether the package adheres to the > > # file system standard. > > FSSTND = -DFSSTND > > > > # The following define establishes ownership for the man pages. > > # Avery tells me that there is a difference between Debian and > > # Slackware. Rather than choose sides I am leaving it up to the user. > > MAN_OWNER = root > > # MAN_OWNER = man > > > > # The following define establishes the name of the pid file for the > > # rsyslogd daemon. The library include file (paths.h) defines the > > # name for the rsyslogd pid to be rsyslog.pid. A number of people have > > # suggested that this should be rsyslogd.pid. You may cast your > > # ballot below. > > SYSLOGD_PIDNAME = -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" > > > > SYSLOGD_FLAGS= -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS ${FSSTND} \ > > ${SYSLOGD_PIDNAME} > > SYSLOG_FLAGS= -DALLOW_KERNEL_LOGGING > > DEB = > > > > .c.o: > > ${CC} ${CFLAGS} -c $*.c > > > > all: syslogd > > > > test: syslog_tst tsyslogd > > > > install: install_man install_exec > > > > syslogd: syslogd.o pidfile.o template.o stringbuf.o srUtils.o outchannel.o > > ${CC} ${LDFLAGS} -o syslogd syslogd.o pidfile.o template.o outchannel.o stringbuf.o srUtils.o ${LIBS} > > > > syslog_tst: syslog_tst.o > > ${CC} ${LDFLAGS} -o syslog_tst syslog_tst.o > > > > tsyslogd: syslogd.c version.h template.o outchannel.o stringbuf.o srUtils.o > > $(CC) $(CFLAGS) -g -DTESTING $(SYSLOGD_FLAGS) -o tsyslogd syslogd.c pidfile.o template.o outchannel.o stringbuf.o srUtils.o $(LIBS) > > > > srUtils.o: srUtils.c srUtils.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c srUtils.c > > > > stringbuf.o: stringbuf.c stringbuf.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c stringbuf.c > > > > template.o: template.c template.h stringbuf.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c template.c > > > > outchannel.o: outchannel.c outchannel.h stringbuf.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c outchannel.c > > > > syslogd.o: syslogd.c version.h template.h outchannel.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c syslogd.c > > > > syslog.o: syslog.c > > ${CC} ${CFLAGS} ${SYSLOG_FLAGS} -c syslog.c > > > > syslog_tst.o: syslog_tst.c > > ${CC} ${CFLAGS} -c syslog_tst.c > > > > clean: > > rm -f *.o *.log *~ *.orig > > > > clobber: clean > > rm -f syslogd klogd ksym syslog_tst oops_test TAGS tsyslogd tklogd > > > > install_exec: syslogd > > ${INSTALL} -b -s syslogd ${DESTDIR}${BINDIR}/rsyslogd > > > > install_man: > > ${INSTALL} rsyslogd.8 ${DESTDIR}${MANDIR}/man8/rsyslogd.8 > > ${INSTALL} rsyslog.conf.5 ${DESTDIR}${MANDIR}/man5/rsyslog.conf.5 > > test# > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog From dennisolvany at gmail.com Mon Jun 27 18:42:57 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 11:42:57 -0500 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD5.4 References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> <003b01c57b32$9e356d90$0366a8c0@d> <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> <1119889425.2097.7.camel@rh9lt.intern.adiscon.com> Message-ID: <000f01c57b37$4669be40$0366a8c0@d> Thanks for quick fix. No rush, though. Just fiddling around. Don't even plan on employing a new version until I set up a new machine, which will be who-knows when. Was thinking of writing a little guide for 090 if necessary. Will wait for next release to do further testing. From rgerhards at hq.adiscon.com Tue Jun 28 16:11:25 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Tue, 28 Jun 2005 16:11:25 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD5.4 Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E34BA@grfint2.intern.adiscon.com> Dennis, I've just uploaded 0.9.1 - official announcement to follow. It is available at http://download.adiscon.com/rsyslog-0.9.1.tar.gz This version also contains some other fixes so that it compiles cleaner under FreeBSD (see NEWS). No source modifications have now been needed in my environment. It would be great if you could give it a quick test. Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Monday, June 27, 2005 6:43 PM > To: rsyslog at lists.adiscon.com > Subject: Re: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile > Difficulties onFreeBSD5.4 > > Thanks for quick fix. No rush, though. Just fiddling around. > Don't even plan on employing a new version until I set up a > new machine, which will be who-knows when. Was thinking of > writing a little guide for 090 if necessary. Will wait for > next release to do further testing. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Tue Jun 28 17:05:15 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Tue, 28 Jun 2005 10:05:15 -0500 Subject: [rsyslog] Rsyslog-0.9.1 w/MySQL on FreeBSD 5.4: One Issue Message-ID: <000801c57bf2$cb067fb0$0366a8c0@d> FreeBSD 5.4 minimal install (fresh). No Linux Binary Compatibility. Mysql41-client installed using, "pkg_add -r mysql41-client". Configured Makefile lines 20, 21, 29. Compile: OK. Fixed Runtime Error: sample.conf [/etc/rsyslog.conf] line 178: *.* >hostname,dbname,userid,password; #requires semi-colon Debug Output: test# rsyslogd -d Allocated parts table for 2656 file descriptors. Starting. Called init. cfsysline --> template TraditionalFormat,"%timegenerated% %HOSTNAME% %syslogtag%%msg:::drop-last-lf%\n" cfsysline --> template precise,"%syslogpriority%,%syslogfacility%,%timegenerated:::fulltime%,%HOSTNAME%,%syslogtag%,%msg%\n" Invalid field option 'fulltime' specified - ignored. cfsysline --> template RFC3164fmt,"<%PRI%>%TIMESTAMP% %HOSTNAME% %syslogtag%%msg%" cfsysline --> template wallmsg,"\r\n\7Message from syslogd@%HOSTNAME% at %timegenerated% ...\r\n %syslogtag%%msg%\n\r" cfsysline --> template WinSyslogFmt,"%HOSTNAME%,%timegenerated:1:10:date-rfc3339%,%timegenerated:12:19:date-rfc3339%,%timegenerated:1:10:date-rfc3339%,%timegenerated:12:19:date-rfc3339%,%syslogfacility%,%syslogpriority%,%syslogtag%%msg%\n" cfsysline --> template dbFormat,"insert into SystemEvents (Message, Facility,FromHost, Priority, DeviceReportedTime, ReceivedAt, InfoUnitID, SysLogTag) values ('%msg%', %syslogfacility%, '%HOSTNAME%',%syslogpriority%, '%timereported:::date-mysql%', '%timegenerated:::date-mysql%', %iut%, '%syslogtag%')",sql cfline(*.* >mysql.carcass.us,rsyslogtest,dennisolvany,password) symbolic name: * ==> 255 leading char in action: > in init() - WITH_DB case logmsg: syslog.err<43>, flags 4, from test, msg rsyslogd: Could not find template 'password' Called fprintlog, logging to CONSOLE Called fprintlog, logging to TTY Jun 28 14:23:27 test rsyslogd: Could not find template 'password' rsyslogd: Could not find template 'password' template 'password' Segmentation fault (core dumped) test# After above procedures, rsyslog-0.9.1 is logging to database. Seems to be running properly. From rgerhards at hq.adiscon.com Tue Jun 28 17:10:13 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Tue, 28 Jun 2005 17:10:13 +0200 Subject: [rsyslog] Rsyslog-0.9.1 w/MySQL on FreeBSD 5.4: One Issue Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E34BB@grfint2.intern.adiscon.com> Will see that I remove the semicolon bug soon. Can't be a big issue, but obviously annoying... All in all, I think I will move the database write to outchannel definitions, but that's more work ;) well... a lot to do. The next things I'd like to do is support for larger size messages and TCP logging. let me see ;) Thanks for the test, Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Tuesday, June 28, 2005 5:05 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] Rsyslog-0.9.1 w/MySQL on FreeBSD 5.4: One Issue > > FreeBSD 5.4 minimal install (fresh). > No Linux Binary Compatibility. > Mysql41-client installed using, "pkg_add -r mysql41-client". > > Configured Makefile lines 20, 21, 29. > Compile: OK. > > Fixed Runtime Error: > > sample.conf [/etc/rsyslog.conf] > line 178: *.* >hostname,dbname,userid,password; > #requires semi-colon > > Debug Output: > > test# rsyslogd -d > Allocated parts table for 2656 file descriptors. > Starting. > Called init. > cfsysline --> template TraditionalFormat,"%timegenerated% > %HOSTNAME% %syslogtag%%msg:::drop-last-lf%\n" > cfsysline --> template > precise,"%syslogpriority%,%syslogfacility%,%timegenerated:::fu lltime%,%HOSTNAME%,%syslogtag%,%msg%\n" > Invalid field option 'fulltime' specified - ignored. > cfsysline --> template RFC3164fmt,"<%PRI%>%TIMESTAMP% > %HOSTNAME% %syslogtag%%msg%" > cfsysline --> template wallmsg,"\r\n\7Message from > syslogd@%HOSTNAME% at %timegenerated% ...\r\n %syslogtag%%msg%\n\r" > cfsysline --> template > WinSyslogFmt,"%HOSTNAME%,%timegenerated:1:10:date-rfc3339%,%ti megenerated:12:19:date-rfc3339%,%timegenerated:1:10:date-> rfc3339%,%timegenerated:12:19:date-rfc3339%,%syslogfacility%,% > syslogpriority%,%syslogtag%%msg%\n" > cfsysline --> template dbFormat,"insert into SystemEvents > (Message, Facility,FromHost, Priority, DeviceReportedTime, > ReceivedAt, InfoUnitID, SysLogTag) values ('%msg%', > %syslogfacility%, '%HOSTNAME%',%syslogpriority%, > '%timereported:::date-mysql%', > '%timegenerated:::date-mysql%', %iut%, '%syslogtag%')",sql > cfline(*.* > >mysql.carcass.us,rsyslogtest,dennisolvany,password) > symbolic name: * ==> 255 > leading char in action: > > in init() - WITH_DB case > logmsg: syslog.err<43>, flags 4, from test, msg rsyslogd: > Could not find template 'password' > > Called fprintlog, logging to CONSOLE > Called fprintlog, logging to TTY > Jun 28 14:23:27 test rsyslogd: Could not find template 'password' > rsyslogd: Could not find template 'password' > template 'password' > Segmentation fault (core dumped) > test# > > > After above procedures, rsyslog-0.9.1 is logging to database. > Seems to be running properly. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Wed Jun 29 14:38:34 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Wed, 29 Jun 2005 07:38:34 -0500 Subject: [rsyslog] Add a Doc? Message-ID: <001201c57ca7$77a4aa30$0366a8c0@d> I was thinking that another cool website addition would be to publish the database schema along with the man pages. This could be helpful and informative to some users. From rgerhards at hq.adiscon.com Wed Jun 29 14:52:30 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Wed, 29 Jun 2005 14:52:30 +0200 Subject: [rsyslog] Add a Doc? Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E34D3@grfint2.intern.adiscon.com> Dennis, definitely :). I've also just talked to the web folks, I'll get a separate page at www.rsyslog.com. That site will be driven by postnuke, so it will probably be (relatively) easy to update - even for you ;) I hope to have this in a few days... Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Wednesday, June 29, 2005 2:39 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] Add a Doc? > > I was thinking that another cool website addition would be to > publish the database schema along with the man pages. This > could be helpful and informative to some users. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From rgerhards at hq.adiscon.com Wed Jun 1 11:37:24 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Wed, 1 Jun 2005 11:37:24 +0200 Subject: [rsyslog] syslogd and rsyslogd together Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0621D4@grfint2.intern.adiscon.com> Sorry for the sluggish response. I am a bit overwhelmed at the moment, my mailbox needs a desperate cleanup ;) rsyslogd is intended as a syslogd replacement. As such, it does *NOT* play nice together with stock syslogd. And, yes, rsyslogd binds to port 514/UDP by default. It does so by querying etc/services, which unfortuantely makes it hard to change this default easily. I'll add this to the todo list... Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Tuesday, May 31, 2005 8:44 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] syslogd and rsyslogd together > > Syslogd and rsyslogd didn't seem to play well together on my > system. I had some debugging output, but I don't recall > precisely what it said and I didn't save it. I didn't think > rsyslogd would bind to 514 by default, would it? I think I > will try and reenact the scenario. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Wed Jun 1 14:25:06 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Wed, 1 Jun 2005 07:25:06 -0500 Subject: [rsyslog] sluggish response Message-ID: <001001c566a4$f25e4060$0366a8c0@d> No problemo. Take your time. Frankly, I don't care about syslogd and rsyslogd coexisting. I've got rsyslogd logging everything to my MySQL database now so I'm happy as a clam. I hope the information I compiled helps with tidying up the code a bit. I was wondering about maybe getting this program into the FreeBSD ports tree. As of yet, I still have no boot-time solution. When that's taken care of, I'd like to take a crack at porting it if that's OK with you. Never done anything like this before though. Maybe you prefer to port it personally? But, whatever... I'm diggin' it. From dennisolvany at gmail.com Sun Jun 5 13:13:52 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Sun, 5 Jun 2005 06:13:52 -0500 Subject: [rsyslog] man pages Message-ID: <000a01c569bf$a8d10db0$0366a8c0@d> I was thinking that an incredibly intelligent move would be to publish the man pages on the website. I was trying to get msyslog up and running and the entire documentation was on the man pages, which I could not access because the FreeBSD port did not install them and , of course, they were not available on the site. Lo and behold, I never got msyslog running. It also provides alot of information concerning the complexity of the application and helps people decide if the application will be suitable for their needs. I personally shy away from most software that doesn't offer good support on the website because that's where I go for support. Man pages are difficult to read on the CLI. The web offers a much friendlier interface. From rgerhards at hq.adiscon.com Mon Jun 6 09:06:07 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 6 Jun 2005 09:06:07 +0200 Subject: [rsyslog] man pages Message-ID: <577465F99B41C842AAFBE9ED71E70ABA06223E@grfint2.intern.adiscon.com> Dennis, excellent idea. I'll see that I get them online today (obviously a fairly easy task) ;) All web page updates are done on a staging system and the content is moved nightly. So the update will not appear before tomorrow, just in case you wonder ;) Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Sunday, June 05, 2005 1:14 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] man pages > > I was thinking that an incredibly intelligent move would be > to publish the man pages on the website. I was trying to get > msyslog up and running and the entire documentation was on > the man pages, which I could not access because the FreeBSD > port did not install them and , of course, they were not > available on the site. Lo and behold, I never got msyslog > running. It also provides alot of information concerning the > complexity of the application and helps people decide if the > application will be suitable for their needs. I personally > shy away from most software that doesn't offer good support > on the website because that's where I go for support. Man > pages are difficult to read on the CLI. The web offers a much > friendlier interface. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From rgerhards at hq.adiscon.com Wed Jun 22 18:20:27 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Wed, 22 Jun 2005 18:20:27 +0200 Subject: [rsyslog] rsyslog 0.9.0 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA062374@grfint2.intern.adiscon.com> Hi, Rsyslog 0.9.0 has been released today. It now supports log files larger than 2gb (where supported by OS & file system) and the ability to specify the maximum size for log files. If a log grows larger, a rotation script (or something similiar) can automatically be called from within rsyslog. Also, 0.9.0 includes some minor changes which are in preparation for upcoming major ones. See the changelog for details. So far, 0.9.0 has been compiled and tested on Red Hat and Debian, BSD tests are outstanding. You can obtain the latest release from http://www.monitorware.com/rsyslog/ I hope it is helpful. Feedback please address to the list. Rainer Gerhards Adiscon From dennisolvany at gmail.com Mon Jun 27 17:01:26 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 10:01:26 -0500 Subject: [rsyslog] rsyslog 0.9.0 released References: <577465F99B41C842AAFBE9ED71E70ABA062374@grfint2.intern.adiscon.com> Message-ID: <000d01c57b29$18209030$0366a8c0@d> The links at http://www.monitorware.com/rsyslog/ still point to 0.8.4. From rgerhards at hq.adiscon.com Mon Jun 27 17:13:10 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 17:13:10 +0200 Subject: [rsyslog] rsyslog 0.9.0 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA06239A@grfint2.intern.adiscon.com> Oops... sorry, I forgot to update the download link at the top. The URL for 0.9.0 is http://download.adiscon.com/rsyslog-0.9.0.tar.gz I will change the web, but it will propagate only tonight... Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Monday, June 27, 2005 5:01 PM > To: rsyslog at lists.adiscon.com > Subject: Re: [rsyslog] rsyslog 0.9.0 released > > The links at http://www.monitorware.com/rsyslog/ still point to 0.8.4. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Mon Jun 27 17:33:58 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 10:33:58 -0500 Subject: [rsyslog] FreeBSD: Linux Compatibility Message-ID: <000a01c57b2d$a3786b90$0366a8c0@d> Does rsyslog require Linux Binary Compatibility under FreeBSD? From dennisolvany at gmail.com Mon Jun 27 17:50:23 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 10:50:23 -0500 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties on FreeBSD 5.4 Message-ID: <001701c57b2f$ee50a8b0$0366a8c0@d> FreeBSD 5.4 fresh install. No Linux Binary Compatibility. mysql41-client Configured Makefile lines 15, 16, 24. Fixed syslogd.c: line 184: #include "/usr/local/include/mysql/mysql.h" line 185: #include "/usr/local/include/mysql/errmsg.h" Make output: test# make gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c syslogd.c syslogd.c: In function `writeFile': syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) syslogd.c: At top level: syslogd.c:4633: warning: 'allocate_log' defined but not used gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -c pidfile.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c template.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c stringbuf.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c srUtils.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c outchannel.c In file included from outchannel.c:21: outchannel.h:11: error: syntax error before "off_t" outchannel.c:110: error: syntax error before "off_t" outchannel.c: In function `get_off_t': outchannel.c:113: error: syntax error before "val" outchannel.c:115: error: `pp' undeclared (first use in this function) outchannel.c:115: error: (Each undeclared identifier is reported only once outchannel.c:115: error: for each function it appears in.) outchannel.c:117: error: `pOff_t' undeclared (first use in this function) outchannel.c:122: error: `val' undeclared (first use in this function) outchannel.c: In function `ochAddLine': outchannel.c:205: error: structure has no member named `uSizeLimit' outchannel.c: In function `ochPrintList': outchannel.c:267: error: structure has no member named `uSizeLimit' *** Error code 1 Stop in /usr/home/dennisolvany/rsyslog-0.9.0. test# From rgerhards at hq.adiscon.com Mon Jun 27 17:58:45 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 17:58:45 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties on FreeBSD 5.4 In-Reply-To: <001701c57b2f$ee50a8b0$0366a8c0@d> References: <001701c57b2f$ee50a8b0$0366a8c0@d> Message-ID: <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> ahh... This is the large file support. Seems to be different on FreeBSD. As a quick fix, compile with -DNOLARGEFILE in the c options in makefile. This will disable it. I hope I can fire up FreeBSD tomorrow and see how to do it there. Rainer On Mon, 2005-06-27 at 17:50, Dennis Olvany wrote: > FreeBSD 5.4 fresh install. > No Linux Binary Compatibility. > mysql41-client > > Configured Makefile lines 15, 16, 24. > > Fixed syslogd.c: > line 184: #include "/usr/local/include/mysql/mysql.h" > line 185: #include "/usr/local/include/mysql/errmsg.h" > > Make output: > test# make > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c syslogd.c > syslogd.c: In function `writeFile': > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) > syslogd.c: At top level: > syslogd.c:4633: warning: 'allocate_log' defined but not used > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -c pidfile.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c template.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c stringbuf.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c srUtils.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c outchannel.c > In file included from outchannel.c:21: > outchannel.h:11: error: syntax error before "off_t" > outchannel.c:110: error: syntax error before "off_t" > outchannel.c: In function `get_off_t': > outchannel.c:113: error: syntax error before "val" > outchannel.c:115: error: `pp' undeclared (first use in this function) > outchannel.c:115: error: (Each undeclared identifier is reported only once > outchannel.c:115: error: for each function it appears in.) > outchannel.c:117: error: `pOff_t' undeclared (first use in this function) > outchannel.c:122: error: `val' undeclared (first use in this function) > outchannel.c: In function `ochAddLine': > outchannel.c:205: error: structure has no member named `uSizeLimit' > outchannel.c: In function `ochPrintList': > outchannel.c:267: error: structure has no member named `uSizeLimit' > *** Error code 1 > > Stop in /usr/home/dennisolvany/rsyslog-0.9.0. > test# > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog From dennisolvany at gmail.com Mon Jun 27 18:09:37 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 11:09:37 -0500 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD 5.4 References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> Message-ID: <003b01c57b32$9e356d90$0366a8c0@d> I'm not sure which are the c options in the Makefile. # Makefile for rsyslog CC= gcc #CFLAGS= -g -DSYSV -Wall # Add the -DMTRACE macro if you would like to use mtrace() # to hunt for memory leaks # next 2 lines are debug settings #LDFLAGS= -g -Wall -fno-omit-frame-pointer #CFLAGS= -DSYSV -g -Wall -fno-omit-frame-pointer # the next two lines are essentially the same, but -DWITH_DB # enables the MySQL code. By default, that one is commented out # change the comment chars to activate it if you need MySQL! # In this case, also look down further to uncomment the libs #CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB LDFLAGS= -s INSTALL = install BINDIR = /usr/sbin MANDIR = /usr/share/man # Uncomment the following to use mysql. LIBS = -lmysqlclient #/var/lib/mysql/mysql # There is one report that under an all ELF system there may be a need to # explicilty link with libresolv.a. If linking syslogd fails you may wish # to try uncommenting the following define. # LIBS = /usr/lib/libresolv.a # The following define determines whether the package adheres to the # file system standard. FSSTND = -DFSSTND # The following define establishes ownership for the man pages. # Avery tells me that there is a difference between Debian and # Slackware. Rather than choose sides I am leaving it up to the user. MAN_OWNER = root # MAN_OWNER = man # The following define establishes the name of the pid file for the # rsyslogd daemon. The library include file (paths.h) defines the # name for the rsyslogd pid to be rsyslog.pid. A number of people have # suggested that this should be rsyslogd.pid. You may cast your # ballot below. SYSLOGD_PIDNAME = -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" SYSLOGD_FLAGS= -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS ${FSSTND} \ ${SYSLOGD_PIDNAME} SYSLOG_FLAGS= -DALLOW_KERNEL_LOGGING DEB = .c.o: ${CC} ${CFLAGS} -c $*.c all: syslogd test: syslog_tst tsyslogd install: install_man install_exec syslogd: syslogd.o pidfile.o template.o stringbuf.o srUtils.o outchannel.o ${CC} ${LDFLAGS} -o syslogd syslogd.o pidfile.o template.o outchannel.o stringbuf.o srUtils.o ${LIBS} syslog_tst: syslog_tst.o ${CC} ${LDFLAGS} -o syslog_tst syslog_tst.o tsyslogd: syslogd.c version.h template.o outchannel.o stringbuf.o srUtils.o $(CC) $(CFLAGS) -g -DTESTING $(SYSLOGD_FLAGS) -o tsyslogd syslogd.c pidfile.o template.o outchannel.o stringbuf.o srUtils.o $(LIBS) srUtils.o: srUtils.c srUtils.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c srUtils.c stringbuf.o: stringbuf.c stringbuf.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c stringbuf.c template.o: template.c template.h stringbuf.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c template.c outchannel.o: outchannel.c outchannel.h stringbuf.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c outchannel.c syslogd.o: syslogd.c version.h template.h outchannel.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c syslogd.c syslog.o: syslog.c ${CC} ${CFLAGS} ${SYSLOG_FLAGS} -c syslog.c syslog_tst.o: syslog_tst.c ${CC} ${CFLAGS} -c syslog_tst.c clean: rm -f *.o *.log *~ *.orig clobber: clean rm -f syslogd klogd ksym syslog_tst oops_test TAGS tsyslogd tklogd install_exec: syslogd ${INSTALL} -b -s syslogd ${DESTDIR}${BINDIR}/rsyslogd install_man: ${INSTALL} rsyslogd.8 ${DESTDIR}${MANDIR}/man8/rsyslogd.8 ${INSTALL} rsyslog.conf.5 ${DESTDIR}${MANDIR}/man5/rsyslog.conf.5 test# From rgerhards at hq.adiscon.com Mon Jun 27 18:17:23 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 18:17:23 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD 5.4 In-Reply-To: <003b01c57b32$9e356d90$0366a8c0@d> References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> <003b01c57b32$9e356d90$0366a8c0@d> Message-ID: <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> Dennis, I've fired up a FreeBSD and now see it is a more subtle issue. Bear a little with me, I guess there is even a problem on Linux, which you simply do not notice ;) Rainer On Mon, 2005-06-27 at 18:09, Dennis Olvany wrote: > I'm not sure which are the c options in the Makefile. > > > # Makefile for rsyslog > > CC= gcc > #CFLAGS= -g -DSYSV -Wall > # Add the -DMTRACE macro if you would like to use mtrace() > # to hunt for memory leaks > # next 2 lines are debug settings > #LDFLAGS= -g -Wall -fno-omit-frame-pointer > #CFLAGS= -DSYSV -g -Wall -fno-omit-frame-pointer > > # the next two lines are essentially the same, but -DWITH_DB > # enables the MySQL code. By default, that one is commented out > # change the comment chars to activate it if you need MySQL! > # In this case, also look down further to uncomment the libs > #CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce > CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB > LDFLAGS= -s > > INSTALL = install > BINDIR = /usr/sbin > MANDIR = /usr/share/man > > # Uncomment the following to use mysql. > LIBS = -lmysqlclient #/var/lib/mysql/mysql > > # There is one report that under an all ELF system there may be a need to > # explicilty link with libresolv.a. If linking syslogd fails you may wish > # to try uncommenting the following define. > # LIBS = /usr/lib/libresolv.a > > # The following define determines whether the package adheres to the > # file system standard. > FSSTND = -DFSSTND > > # The following define establishes ownership for the man pages. > # Avery tells me that there is a difference between Debian and > # Slackware. Rather than choose sides I am leaving it up to the user. > MAN_OWNER = root > # MAN_OWNER = man > > # The following define establishes the name of the pid file for the > # rsyslogd daemon. The library include file (paths.h) defines the > # name for the rsyslogd pid to be rsyslog.pid. A number of people have > # suggested that this should be rsyslogd.pid. You may cast your > # ballot below. > SYSLOGD_PIDNAME = -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" > > SYSLOGD_FLAGS= -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS ${FSSTND} \ > ${SYSLOGD_PIDNAME} > SYSLOG_FLAGS= -DALLOW_KERNEL_LOGGING > DEB = > > .c.o: > ${CC} ${CFLAGS} -c $*.c > > all: syslogd > > test: syslog_tst tsyslogd > > install: install_man install_exec > > syslogd: syslogd.o pidfile.o template.o stringbuf.o srUtils.o outchannel.o > ${CC} ${LDFLAGS} -o syslogd syslogd.o pidfile.o template.o outchannel.o stringbuf.o srUtils.o ${LIBS} > > syslog_tst: syslog_tst.o > ${CC} ${LDFLAGS} -o syslog_tst syslog_tst.o > > tsyslogd: syslogd.c version.h template.o outchannel.o stringbuf.o srUtils.o > $(CC) $(CFLAGS) -g -DTESTING $(SYSLOGD_FLAGS) -o tsyslogd syslogd.c pidfile.o template.o outchannel.o stringbuf.o srUtils.o $(LIBS) > > srUtils.o: srUtils.c srUtils.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c srUtils.c > > stringbuf.o: stringbuf.c stringbuf.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c stringbuf.c > > template.o: template.c template.h stringbuf.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c template.c > > outchannel.o: outchannel.c outchannel.h stringbuf.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c outchannel.c > > syslogd.o: syslogd.c version.h template.h outchannel.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c syslogd.c > > syslog.o: syslog.c > ${CC} ${CFLAGS} ${SYSLOG_FLAGS} -c syslog.c > > syslog_tst.o: syslog_tst.c > ${CC} ${CFLAGS} -c syslog_tst.c > > clean: > rm -f *.o *.log *~ *.orig > > clobber: clean > rm -f syslogd klogd ksym syslog_tst oops_test TAGS tsyslogd tklogd > > install_exec: syslogd > ${INSTALL} -b -s syslogd ${DESTDIR}${BINDIR}/rsyslogd > > install_man: > ${INSTALL} rsyslogd.8 ${DESTDIR}${MANDIR}/man8/rsyslogd.8 > ${INSTALL} rsyslog.conf.5 ${DESTDIR}${MANDIR}/man5/rsyslog.conf.5 > test# > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog From rgerhards at hq.adiscon.com Mon Jun 27 18:23:45 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 18:23:45 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD 5.4 In-Reply-To: <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> <003b01c57b32$9e356d90$0366a8c0@d> <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> Message-ID: <1119889425.2097.7.camel@rh9lt.intern.adiscon.com> Dennis, OK, for a quick fix... Add this to the top of outchannel.c: #ifndef NOLARGEFILE # define _GNU_SOURCE # define _LARGEFILE_SOURCE # define _LARGEFILE64_SOURCE # define _FILE_OFFSET_BITS 64 #endif then, add #include after stdio.h in outchannel.c. Alternatively, you can obtain the latest CVS snapshot from sourceforge that includes the fix. Its quick and dirty, I'll go over it in more depth tomorrow. Rainer On Mon, 2005-06-27 at 18:17, Rainer Gerhards wrote: > Dennis, > > I've fired up a FreeBSD and now see it is a more subtle issue. Bear a > little with me, I guess there is even a problem on Linux, which you > simply do not notice ;) > > Rainer > > On Mon, 2005-06-27 at 18:09, Dennis Olvany wrote: > > I'm not sure which are the c options in the Makefile. > > > > > > # Makefile for rsyslog > > > > CC= gcc > > #CFLAGS= -g -DSYSV -Wall > > # Add the -DMTRACE macro if you would like to use mtrace() > > # to hunt for memory leaks > > # next 2 lines are debug settings > > #LDFLAGS= -g -Wall -fno-omit-frame-pointer > > #CFLAGS= -DSYSV -g -Wall -fno-omit-frame-pointer > > > > # the next two lines are essentially the same, but -DWITH_DB > > # enables the MySQL code. By default, that one is commented out > > # change the comment chars to activate it if you need MySQL! > > # In this case, also look down further to uncomment the libs > > #CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce > > CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB > > LDFLAGS= -s > > > > INSTALL = install > > BINDIR = /usr/sbin > > MANDIR = /usr/share/man > > > > # Uncomment the following to use mysql. > > LIBS = -lmysqlclient #/var/lib/mysql/mysql > > > > # There is one report that under an all ELF system there may be a need to > > # explicilty link with libresolv.a. If linking syslogd fails you may wish > > # to try uncommenting the following define. > > # LIBS = /usr/lib/libresolv.a > > > > # The following define determines whether the package adheres to the > > # file system standard. > > FSSTND = -DFSSTND > > > > # The following define establishes ownership for the man pages. > > # Avery tells me that there is a difference between Debian and > > # Slackware. Rather than choose sides I am leaving it up to the user. > > MAN_OWNER = root > > # MAN_OWNER = man > > > > # The following define establishes the name of the pid file for the > > # rsyslogd daemon. The library include file (paths.h) defines the > > # name for the rsyslogd pid to be rsyslog.pid. A number of people have > > # suggested that this should be rsyslogd.pid. You may cast your > > # ballot below. > > SYSLOGD_PIDNAME = -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" > > > > SYSLOGD_FLAGS= -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS ${FSSTND} \ > > ${SYSLOGD_PIDNAME} > > SYSLOG_FLAGS= -DALLOW_KERNEL_LOGGING > > DEB = > > > > .c.o: > > ${CC} ${CFLAGS} -c $*.c > > > > all: syslogd > > > > test: syslog_tst tsyslogd > > > > install: install_man install_exec > > > > syslogd: syslogd.o pidfile.o template.o stringbuf.o srUtils.o outchannel.o > > ${CC} ${LDFLAGS} -o syslogd syslogd.o pidfile.o template.o outchannel.o stringbuf.o srUtils.o ${LIBS} > > > > syslog_tst: syslog_tst.o > > ${CC} ${LDFLAGS} -o syslog_tst syslog_tst.o > > > > tsyslogd: syslogd.c version.h template.o outchannel.o stringbuf.o srUtils.o > > $(CC) $(CFLAGS) -g -DTESTING $(SYSLOGD_FLAGS) -o tsyslogd syslogd.c pidfile.o template.o outchannel.o stringbuf.o srUtils.o $(LIBS) > > > > srUtils.o: srUtils.c srUtils.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c srUtils.c > > > > stringbuf.o: stringbuf.c stringbuf.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c stringbuf.c > > > > template.o: template.c template.h stringbuf.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c template.c > > > > outchannel.o: outchannel.c outchannel.h stringbuf.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c outchannel.c > > > > syslogd.o: syslogd.c version.h template.h outchannel.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c syslogd.c > > > > syslog.o: syslog.c > > ${CC} ${CFLAGS} ${SYSLOG_FLAGS} -c syslog.c > > > > syslog_tst.o: syslog_tst.c > > ${CC} ${CFLAGS} -c syslog_tst.c > > > > clean: > > rm -f *.o *.log *~ *.orig > > > > clobber: clean > > rm -f syslogd klogd ksym syslog_tst oops_test TAGS tsyslogd tklogd > > > > install_exec: syslogd > > ${INSTALL} -b -s syslogd ${DESTDIR}${BINDIR}/rsyslogd > > > > install_man: > > ${INSTALL} rsyslogd.8 ${DESTDIR}${MANDIR}/man8/rsyslogd.8 > > ${INSTALL} rsyslog.conf.5 ${DESTDIR}${MANDIR}/man5/rsyslog.conf.5 > > test# > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog From dennisolvany at gmail.com Mon Jun 27 18:42:57 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 11:42:57 -0500 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD5.4 References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> <003b01c57b32$9e356d90$0366a8c0@d> <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> <1119889425.2097.7.camel@rh9lt.intern.adiscon.com> Message-ID: <000f01c57b37$4669be40$0366a8c0@d> Thanks for quick fix. No rush, though. Just fiddling around. Don't even plan on employing a new version until I set up a new machine, which will be who-knows when. Was thinking of writing a little guide for 090 if necessary. Will wait for next release to do further testing. From rgerhards at hq.adiscon.com Tue Jun 28 16:11:25 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Tue, 28 Jun 2005 16:11:25 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD5.4 Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E34BA@grfint2.intern.adiscon.com> Dennis, I've just uploaded 0.9.1 - official announcement to follow. It is available at http://download.adiscon.com/rsyslog-0.9.1.tar.gz This version also contains some other fixes so that it compiles cleaner under FreeBSD (see NEWS). No source modifications have now been needed in my environment. It would be great if you could give it a quick test. Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Monday, June 27, 2005 6:43 PM > To: rsyslog at lists.adiscon.com > Subject: Re: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile > Difficulties onFreeBSD5.4 > > Thanks for quick fix. No rush, though. Just fiddling around. > Don't even plan on employing a new version until I set up a > new machine, which will be who-knows when. Was thinking of > writing a little guide for 090 if necessary. Will wait for > next release to do further testing. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Tue Jun 28 17:05:15 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Tue, 28 Jun 2005 10:05:15 -0500 Subject: [rsyslog] Rsyslog-0.9.1 w/MySQL on FreeBSD 5.4: One Issue Message-ID: <000801c57bf2$cb067fb0$0366a8c0@d> FreeBSD 5.4 minimal install (fresh). No Linux Binary Compatibility. Mysql41-client installed using, "pkg_add -r mysql41-client". Configured Makefile lines 20, 21, 29. Compile: OK. Fixed Runtime Error: sample.conf [/etc/rsyslog.conf] line 178: *.* >hostname,dbname,userid,password; #requires semi-colon Debug Output: test# rsyslogd -d Allocated parts table for 2656 file descriptors. Starting. Called init. cfsysline --> template TraditionalFormat,"%timegenerated% %HOSTNAME% %syslogtag%%msg:::drop-last-lf%\n" cfsysline --> template precise,"%syslogpriority%,%syslogfacility%,%timegenerated:::fulltime%,%HOSTNAME%,%syslogtag%,%msg%\n" Invalid field option 'fulltime' specified - ignored. cfsysline --> template RFC3164fmt,"<%PRI%>%TIMESTAMP% %HOSTNAME% %syslogtag%%msg%" cfsysline --> template wallmsg,"\r\n\7Message from syslogd@%HOSTNAME% at %timegenerated% ...\r\n %syslogtag%%msg%\n\r" cfsysline --> template WinSyslogFmt,"%HOSTNAME%,%timegenerated:1:10:date-rfc3339%,%timegenerated:12:19:date-rfc3339%,%timegenerated:1:10:date-rfc3339%,%timegenerated:12:19:date-rfc3339%,%syslogfacility%,%syslogpriority%,%syslogtag%%msg%\n" cfsysline --> template dbFormat,"insert into SystemEvents (Message, Facility,FromHost, Priority, DeviceReportedTime, ReceivedAt, InfoUnitID, SysLogTag) values ('%msg%', %syslogfacility%, '%HOSTNAME%',%syslogpriority%, '%timereported:::date-mysql%', '%timegenerated:::date-mysql%', %iut%, '%syslogtag%')",sql cfline(*.* >mysql.carcass.us,rsyslogtest,dennisolvany,password) symbolic name: * ==> 255 leading char in action: > in init() - WITH_DB case logmsg: syslog.err<43>, flags 4, from test, msg rsyslogd: Could not find template 'password' Called fprintlog, logging to CONSOLE Called fprintlog, logging to TTY Jun 28 14:23:27 test rsyslogd: Could not find template 'password' rsyslogd: Could not find template 'password' template 'password' Segmentation fault (core dumped) test# After above procedures, rsyslog-0.9.1 is logging to database. Seems to be running properly. From rgerhards at hq.adiscon.com Tue Jun 28 17:10:13 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Tue, 28 Jun 2005 17:10:13 +0200 Subject: [rsyslog] Rsyslog-0.9.1 w/MySQL on FreeBSD 5.4: One Issue Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E34BB@grfint2.intern.adiscon.com> Will see that I remove the semicolon bug soon. Can't be a big issue, but obviously annoying... All in all, I think I will move the database write to outchannel definitions, but that's more work ;) well... a lot to do. The next things I'd like to do is support for larger size messages and TCP logging. let me see ;) Thanks for the test, Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Tuesday, June 28, 2005 5:05 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] Rsyslog-0.9.1 w/MySQL on FreeBSD 5.4: One Issue > > FreeBSD 5.4 minimal install (fresh). > No Linux Binary Compatibility. > Mysql41-client installed using, "pkg_add -r mysql41-client". > > Configured Makefile lines 20, 21, 29. > Compile: OK. > > Fixed Runtime Error: > > sample.conf [/etc/rsyslog.conf] > line 178: *.* >hostname,dbname,userid,password; > #requires semi-colon > > Debug Output: > > test# rsyslogd -d > Allocated parts table for 2656 file descriptors. > Starting. > Called init. > cfsysline --> template TraditionalFormat,"%timegenerated% > %HOSTNAME% %syslogtag%%msg:::drop-last-lf%\n" > cfsysline --> template > precise,"%syslogpriority%,%syslogfacility%,%timegenerated:::fu lltime%,%HOSTNAME%,%syslogtag%,%msg%\n" > Invalid field option 'fulltime' specified - ignored. > cfsysline --> template RFC3164fmt,"<%PRI%>%TIMESTAMP% > %HOSTNAME% %syslogtag%%msg%" > cfsysline --> template wallmsg,"\r\n\7Message from > syslogd@%HOSTNAME% at %timegenerated% ...\r\n %syslogtag%%msg%\n\r" > cfsysline --> template > WinSyslogFmt,"%HOSTNAME%,%timegenerated:1:10:date-rfc3339%,%ti megenerated:12:19:date-rfc3339%,%timegenerated:1:10:date-> rfc3339%,%timegenerated:12:19:date-rfc3339%,%syslogfacility%,% > syslogpriority%,%syslogtag%%msg%\n" > cfsysline --> template dbFormat,"insert into SystemEvents > (Message, Facility,FromHost, Priority, DeviceReportedTime, > ReceivedAt, InfoUnitID, SysLogTag) values ('%msg%', > %syslogfacility%, '%HOSTNAME%',%syslogpriority%, > '%timereported:::date-mysql%', > '%timegenerated:::date-mysql%', %iut%, '%syslogtag%')",sql > cfline(*.* > >mysql.carcass.us,rsyslogtest,dennisolvany,password) > symbolic name: * ==> 255 > leading char in action: > > in init() - WITH_DB case > logmsg: syslog.err<43>, flags 4, from test, msg rsyslogd: > Could not find template 'password' > > Called fprintlog, logging to CONSOLE > Called fprintlog, logging to TTY > Jun 28 14:23:27 test rsyslogd: Could not find template 'password' > rsyslogd: Could not find template 'password' > template 'password' > Segmentation fault (core dumped) > test# > > > After above procedures, rsyslog-0.9.1 is logging to database. > Seems to be running properly. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Wed Jun 29 14:38:34 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Wed, 29 Jun 2005 07:38:34 -0500 Subject: [rsyslog] Add a Doc? Message-ID: <001201c57ca7$77a4aa30$0366a8c0@d> I was thinking that another cool website addition would be to publish the database schema along with the man pages. This could be helpful and informative to some users. From rgerhards at hq.adiscon.com Wed Jun 29 14:52:30 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Wed, 29 Jun 2005 14:52:30 +0200 Subject: [rsyslog] Add a Doc? Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E34D3@grfint2.intern.adiscon.com> Dennis, definitely :). I've also just talked to the web folks, I'll get a separate page at www.rsyslog.com. That site will be driven by postnuke, so it will probably be (relatively) easy to update - even for you ;) I hope to have this in a few days... Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Wednesday, June 29, 2005 2:39 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] Add a Doc? > > I was thinking that another cool website addition would be to > publish the database schema along with the man pages. This > could be helpful and informative to some users. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From rgerhards at hq.adiscon.com Wed Jun 1 11:37:24 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Wed, 1 Jun 2005 11:37:24 +0200 Subject: [rsyslog] syslogd and rsyslogd together Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0621D4@grfint2.intern.adiscon.com> Sorry for the sluggish response. I am a bit overwhelmed at the moment, my mailbox needs a desperate cleanup ;) rsyslogd is intended as a syslogd replacement. As such, it does *NOT* play nice together with stock syslogd. And, yes, rsyslogd binds to port 514/UDP by default. It does so by querying etc/services, which unfortuantely makes it hard to change this default easily. I'll add this to the todo list... Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Tuesday, May 31, 2005 8:44 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] syslogd and rsyslogd together > > Syslogd and rsyslogd didn't seem to play well together on my > system. I had some debugging output, but I don't recall > precisely what it said and I didn't save it. I didn't think > rsyslogd would bind to 514 by default, would it? I think I > will try and reenact the scenario. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Wed Jun 1 14:25:06 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Wed, 1 Jun 2005 07:25:06 -0500 Subject: [rsyslog] sluggish response Message-ID: <001001c566a4$f25e4060$0366a8c0@d> No problemo. Take your time. Frankly, I don't care about syslogd and rsyslogd coexisting. I've got rsyslogd logging everything to my MySQL database now so I'm happy as a clam. I hope the information I compiled helps with tidying up the code a bit. I was wondering about maybe getting this program into the FreeBSD ports tree. As of yet, I still have no boot-time solution. When that's taken care of, I'd like to take a crack at porting it if that's OK with you. Never done anything like this before though. Maybe you prefer to port it personally? But, whatever... I'm diggin' it. From dennisolvany at gmail.com Sun Jun 5 13:13:52 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Sun, 5 Jun 2005 06:13:52 -0500 Subject: [rsyslog] man pages Message-ID: <000a01c569bf$a8d10db0$0366a8c0@d> I was thinking that an incredibly intelligent move would be to publish the man pages on the website. I was trying to get msyslog up and running and the entire documentation was on the man pages, which I could not access because the FreeBSD port did not install them and , of course, they were not available on the site. Lo and behold, I never got msyslog running. It also provides alot of information concerning the complexity of the application and helps people decide if the application will be suitable for their needs. I personally shy away from most software that doesn't offer good support on the website because that's where I go for support. Man pages are difficult to read on the CLI. The web offers a much friendlier interface. From rgerhards at hq.adiscon.com Mon Jun 6 09:06:07 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 6 Jun 2005 09:06:07 +0200 Subject: [rsyslog] man pages Message-ID: <577465F99B41C842AAFBE9ED71E70ABA06223E@grfint2.intern.adiscon.com> Dennis, excellent idea. I'll see that I get them online today (obviously a fairly easy task) ;) All web page updates are done on a staging system and the content is moved nightly. So the update will not appear before tomorrow, just in case you wonder ;) Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Sunday, June 05, 2005 1:14 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] man pages > > I was thinking that an incredibly intelligent move would be > to publish the man pages on the website. I was trying to get > msyslog up and running and the entire documentation was on > the man pages, which I could not access because the FreeBSD > port did not install them and , of course, they were not > available on the site. Lo and behold, I never got msyslog > running. It also provides alot of information concerning the > complexity of the application and helps people decide if the > application will be suitable for their needs. I personally > shy away from most software that doesn't offer good support > on the website because that's where I go for support. Man > pages are difficult to read on the CLI. The web offers a much > friendlier interface. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From rgerhards at hq.adiscon.com Wed Jun 22 18:20:27 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Wed, 22 Jun 2005 18:20:27 +0200 Subject: [rsyslog] rsyslog 0.9.0 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA062374@grfint2.intern.adiscon.com> Hi, Rsyslog 0.9.0 has been released today. It now supports log files larger than 2gb (where supported by OS & file system) and the ability to specify the maximum size for log files. If a log grows larger, a rotation script (or something similiar) can automatically be called from within rsyslog. Also, 0.9.0 includes some minor changes which are in preparation for upcoming major ones. See the changelog for details. So far, 0.9.0 has been compiled and tested on Red Hat and Debian, BSD tests are outstanding. You can obtain the latest release from http://www.monitorware.com/rsyslog/ I hope it is helpful. Feedback please address to the list. Rainer Gerhards Adiscon From dennisolvany at gmail.com Mon Jun 27 17:01:26 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 10:01:26 -0500 Subject: [rsyslog] rsyslog 0.9.0 released References: <577465F99B41C842AAFBE9ED71E70ABA062374@grfint2.intern.adiscon.com> Message-ID: <000d01c57b29$18209030$0366a8c0@d> The links at http://www.monitorware.com/rsyslog/ still point to 0.8.4. From rgerhards at hq.adiscon.com Mon Jun 27 17:13:10 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 17:13:10 +0200 Subject: [rsyslog] rsyslog 0.9.0 released Message-ID: <577465F99B41C842AAFBE9ED71E70ABA06239A@grfint2.intern.adiscon.com> Oops... sorry, I forgot to update the download link at the top. The URL for 0.9.0 is http://download.adiscon.com/rsyslog-0.9.0.tar.gz I will change the web, but it will propagate only tonight... Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Monday, June 27, 2005 5:01 PM > To: rsyslog at lists.adiscon.com > Subject: Re: [rsyslog] rsyslog 0.9.0 released > > The links at http://www.monitorware.com/rsyslog/ still point to 0.8.4. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Mon Jun 27 17:33:58 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 10:33:58 -0500 Subject: [rsyslog] FreeBSD: Linux Compatibility Message-ID: <000a01c57b2d$a3786b90$0366a8c0@d> Does rsyslog require Linux Binary Compatibility under FreeBSD? From dennisolvany at gmail.com Mon Jun 27 17:50:23 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 10:50:23 -0500 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties on FreeBSD 5.4 Message-ID: <001701c57b2f$ee50a8b0$0366a8c0@d> FreeBSD 5.4 fresh install. No Linux Binary Compatibility. mysql41-client Configured Makefile lines 15, 16, 24. Fixed syslogd.c: line 184: #include "/usr/local/include/mysql/mysql.h" line 185: #include "/usr/local/include/mysql/errmsg.h" Make output: test# make gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c syslogd.c syslogd.c: In function `writeFile': syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) syslogd.c: At top level: syslogd.c:4633: warning: 'allocate_log' defined but not used gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -c pidfile.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c template.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c stringbuf.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c srUtils.c gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c outchannel.c In file included from outchannel.c:21: outchannel.h:11: error: syntax error before "off_t" outchannel.c:110: error: syntax error before "off_t" outchannel.c: In function `get_off_t': outchannel.c:113: error: syntax error before "val" outchannel.c:115: error: `pp' undeclared (first use in this function) outchannel.c:115: error: (Each undeclared identifier is reported only once outchannel.c:115: error: for each function it appears in.) outchannel.c:117: error: `pOff_t' undeclared (first use in this function) outchannel.c:122: error: `val' undeclared (first use in this function) outchannel.c: In function `ochAddLine': outchannel.c:205: error: structure has no member named `uSizeLimit' outchannel.c: In function `ochPrintList': outchannel.c:267: error: structure has no member named `uSizeLimit' *** Error code 1 Stop in /usr/home/dennisolvany/rsyslog-0.9.0. test# From rgerhards at hq.adiscon.com Mon Jun 27 17:58:45 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 17:58:45 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties on FreeBSD 5.4 In-Reply-To: <001701c57b2f$ee50a8b0$0366a8c0@d> References: <001701c57b2f$ee50a8b0$0366a8c0@d> Message-ID: <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> ahh... This is the large file support. Seems to be different on FreeBSD. As a quick fix, compile with -DNOLARGEFILE in the c options in makefile. This will disable it. I hope I can fire up FreeBSD tomorrow and see how to do it there. Rainer On Mon, 2005-06-27 at 17:50, Dennis Olvany wrote: > FreeBSD 5.4 fresh install. > No Linux Binary Compatibility. > mysql41-client > > Configured Makefile lines 15, 16, 24. > > Fixed syslogd.c: > line 184: #include "/usr/local/include/mysql/mysql.h" > line 185: #include "/usr/local/include/mysql/errmsg.h" > > Make output: > test# make > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c syslogd.c > syslogd.c: In function `writeFile': > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3038: warning: long unsigned int format, different type arg (arg 6) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 5) > syslogd.c:3045: warning: long unsigned int format, different type arg (arg 6) > syslogd.c: At top level: > syslogd.c:4633: warning: 'allocate_log' defined but not used > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -c pidfile.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c template.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c stringbuf.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c srUtils.c > gcc -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS -DFSSTND -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" -c outchannel.c > In file included from outchannel.c:21: > outchannel.h:11: error: syntax error before "off_t" > outchannel.c:110: error: syntax error before "off_t" > outchannel.c: In function `get_off_t': > outchannel.c:113: error: syntax error before "val" > outchannel.c:115: error: `pp' undeclared (first use in this function) > outchannel.c:115: error: (Each undeclared identifier is reported only once > outchannel.c:115: error: for each function it appears in.) > outchannel.c:117: error: `pOff_t' undeclared (first use in this function) > outchannel.c:122: error: `val' undeclared (first use in this function) > outchannel.c: In function `ochAddLine': > outchannel.c:205: error: structure has no member named `uSizeLimit' > outchannel.c: In function `ochPrintList': > outchannel.c:267: error: structure has no member named `uSizeLimit' > *** Error code 1 > > Stop in /usr/home/dennisolvany/rsyslog-0.9.0. > test# > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog From dennisolvany at gmail.com Mon Jun 27 18:09:37 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 11:09:37 -0500 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD 5.4 References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> Message-ID: <003b01c57b32$9e356d90$0366a8c0@d> I'm not sure which are the c options in the Makefile. # Makefile for rsyslog CC= gcc #CFLAGS= -g -DSYSV -Wall # Add the -DMTRACE macro if you would like to use mtrace() # to hunt for memory leaks # next 2 lines are debug settings #LDFLAGS= -g -Wall -fno-omit-frame-pointer #CFLAGS= -DSYSV -g -Wall -fno-omit-frame-pointer # the next two lines are essentially the same, but -DWITH_DB # enables the MySQL code. By default, that one is commented out # change the comment chars to activate it if you need MySQL! # In this case, also look down further to uncomment the libs #CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB LDFLAGS= -s INSTALL = install BINDIR = /usr/sbin MANDIR = /usr/share/man # Uncomment the following to use mysql. LIBS = -lmysqlclient #/var/lib/mysql/mysql # There is one report that under an all ELF system there may be a need to # explicilty link with libresolv.a. If linking syslogd fails you may wish # to try uncommenting the following define. # LIBS = /usr/lib/libresolv.a # The following define determines whether the package adheres to the # file system standard. FSSTND = -DFSSTND # The following define establishes ownership for the man pages. # Avery tells me that there is a difference between Debian and # Slackware. Rather than choose sides I am leaving it up to the user. MAN_OWNER = root # MAN_OWNER = man # The following define establishes the name of the pid file for the # rsyslogd daemon. The library include file (paths.h) defines the # name for the rsyslogd pid to be rsyslog.pid. A number of people have # suggested that this should be rsyslogd.pid. You may cast your # ballot below. SYSLOGD_PIDNAME = -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" SYSLOGD_FLAGS= -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS ${FSSTND} \ ${SYSLOGD_PIDNAME} SYSLOG_FLAGS= -DALLOW_KERNEL_LOGGING DEB = .c.o: ${CC} ${CFLAGS} -c $*.c all: syslogd test: syslog_tst tsyslogd install: install_man install_exec syslogd: syslogd.o pidfile.o template.o stringbuf.o srUtils.o outchannel.o ${CC} ${LDFLAGS} -o syslogd syslogd.o pidfile.o template.o outchannel.o stringbuf.o srUtils.o ${LIBS} syslog_tst: syslog_tst.o ${CC} ${LDFLAGS} -o syslog_tst syslog_tst.o tsyslogd: syslogd.c version.h template.o outchannel.o stringbuf.o srUtils.o $(CC) $(CFLAGS) -g -DTESTING $(SYSLOGD_FLAGS) -o tsyslogd syslogd.c pidfile.o template.o outchannel.o stringbuf.o srUtils.o $(LIBS) srUtils.o: srUtils.c srUtils.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c srUtils.c stringbuf.o: stringbuf.c stringbuf.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c stringbuf.c template.o: template.c template.h stringbuf.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c template.c outchannel.o: outchannel.c outchannel.h stringbuf.h liblogging-stub.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c outchannel.c syslogd.o: syslogd.c version.h template.h outchannel.h ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c syslogd.c syslog.o: syslog.c ${CC} ${CFLAGS} ${SYSLOG_FLAGS} -c syslog.c syslog_tst.o: syslog_tst.c ${CC} ${CFLAGS} -c syslog_tst.c clean: rm -f *.o *.log *~ *.orig clobber: clean rm -f syslogd klogd ksym syslog_tst oops_test TAGS tsyslogd tklogd install_exec: syslogd ${INSTALL} -b -s syslogd ${DESTDIR}${BINDIR}/rsyslogd install_man: ${INSTALL} rsyslogd.8 ${DESTDIR}${MANDIR}/man8/rsyslogd.8 ${INSTALL} rsyslog.conf.5 ${DESTDIR}${MANDIR}/man5/rsyslog.conf.5 test# From rgerhards at hq.adiscon.com Mon Jun 27 18:17:23 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 18:17:23 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD 5.4 In-Reply-To: <003b01c57b32$9e356d90$0366a8c0@d> References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> <003b01c57b32$9e356d90$0366a8c0@d> Message-ID: <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> Dennis, I've fired up a FreeBSD and now see it is a more subtle issue. Bear a little with me, I guess there is even a problem on Linux, which you simply do not notice ;) Rainer On Mon, 2005-06-27 at 18:09, Dennis Olvany wrote: > I'm not sure which are the c options in the Makefile. > > > # Makefile for rsyslog > > CC= gcc > #CFLAGS= -g -DSYSV -Wall > # Add the -DMTRACE macro if you would like to use mtrace() > # to hunt for memory leaks > # next 2 lines are debug settings > #LDFLAGS= -g -Wall -fno-omit-frame-pointer > #CFLAGS= -DSYSV -g -Wall -fno-omit-frame-pointer > > # the next two lines are essentially the same, but -DWITH_DB > # enables the MySQL code. By default, that one is commented out > # change the comment chars to activate it if you need MySQL! > # In this case, also look down further to uncomment the libs > #CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce > CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB > LDFLAGS= -s > > INSTALL = install > BINDIR = /usr/sbin > MANDIR = /usr/share/man > > # Uncomment the following to use mysql. > LIBS = -lmysqlclient #/var/lib/mysql/mysql > > # There is one report that under an all ELF system there may be a need to > # explicilty link with libresolv.a. If linking syslogd fails you may wish > # to try uncommenting the following define. > # LIBS = /usr/lib/libresolv.a > > # The following define determines whether the package adheres to the > # file system standard. > FSSTND = -DFSSTND > > # The following define establishes ownership for the man pages. > # Avery tells me that there is a difference between Debian and > # Slackware. Rather than choose sides I am leaving it up to the user. > MAN_OWNER = root > # MAN_OWNER = man > > # The following define establishes the name of the pid file for the > # rsyslogd daemon. The library include file (paths.h) defines the > # name for the rsyslogd pid to be rsyslog.pid. A number of people have > # suggested that this should be rsyslogd.pid. You may cast your > # ballot below. > SYSLOGD_PIDNAME = -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" > > SYSLOGD_FLAGS= -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS ${FSSTND} \ > ${SYSLOGD_PIDNAME} > SYSLOG_FLAGS= -DALLOW_KERNEL_LOGGING > DEB = > > .c.o: > ${CC} ${CFLAGS} -c $*.c > > all: syslogd > > test: syslog_tst tsyslogd > > install: install_man install_exec > > syslogd: syslogd.o pidfile.o template.o stringbuf.o srUtils.o outchannel.o > ${CC} ${LDFLAGS} -o syslogd syslogd.o pidfile.o template.o outchannel.o stringbuf.o srUtils.o ${LIBS} > > syslog_tst: syslog_tst.o > ${CC} ${LDFLAGS} -o syslog_tst syslog_tst.o > > tsyslogd: syslogd.c version.h template.o outchannel.o stringbuf.o srUtils.o > $(CC) $(CFLAGS) -g -DTESTING $(SYSLOGD_FLAGS) -o tsyslogd syslogd.c pidfile.o template.o outchannel.o stringbuf.o srUtils.o $(LIBS) > > srUtils.o: srUtils.c srUtils.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c srUtils.c > > stringbuf.o: stringbuf.c stringbuf.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c stringbuf.c > > template.o: template.c template.h stringbuf.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c template.c > > outchannel.o: outchannel.c outchannel.h stringbuf.h liblogging-stub.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c outchannel.c > > syslogd.o: syslogd.c version.h template.h outchannel.h > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c syslogd.c > > syslog.o: syslog.c > ${CC} ${CFLAGS} ${SYSLOG_FLAGS} -c syslog.c > > syslog_tst.o: syslog_tst.c > ${CC} ${CFLAGS} -c syslog_tst.c > > clean: > rm -f *.o *.log *~ *.orig > > clobber: clean > rm -f syslogd klogd ksym syslog_tst oops_test TAGS tsyslogd tklogd > > install_exec: syslogd > ${INSTALL} -b -s syslogd ${DESTDIR}${BINDIR}/rsyslogd > > install_man: > ${INSTALL} rsyslogd.8 ${DESTDIR}${MANDIR}/man8/rsyslogd.8 > ${INSTALL} rsyslog.conf.5 ${DESTDIR}${MANDIR}/man5/rsyslog.conf.5 > test# > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog From rgerhards at hq.adiscon.com Mon Jun 27 18:23:45 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Mon, 27 Jun 2005 18:23:45 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD 5.4 In-Reply-To: <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> <003b01c57b32$9e356d90$0366a8c0@d> <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> Message-ID: <1119889425.2097.7.camel@rh9lt.intern.adiscon.com> Dennis, OK, for a quick fix... Add this to the top of outchannel.c: #ifndef NOLARGEFILE # define _GNU_SOURCE # define _LARGEFILE_SOURCE # define _LARGEFILE64_SOURCE # define _FILE_OFFSET_BITS 64 #endif then, add #include after stdio.h in outchannel.c. Alternatively, you can obtain the latest CVS snapshot from sourceforge that includes the fix. Its quick and dirty, I'll go over it in more depth tomorrow. Rainer On Mon, 2005-06-27 at 18:17, Rainer Gerhards wrote: > Dennis, > > I've fired up a FreeBSD and now see it is a more subtle issue. Bear a > little with me, I guess there is even a problem on Linux, which you > simply do not notice ;) > > Rainer > > On Mon, 2005-06-27 at 18:09, Dennis Olvany wrote: > > I'm not sure which are the c options in the Makefile. > > > > > > # Makefile for rsyslog > > > > CC= gcc > > #CFLAGS= -g -DSYSV -Wall > > # Add the -DMTRACE macro if you would like to use mtrace() > > # to hunt for memory leaks > > # next 2 lines are debug settings > > #LDFLAGS= -g -Wall -fno-omit-frame-pointer > > #CFLAGS= -DSYSV -g -Wall -fno-omit-frame-pointer > > > > # the next two lines are essentially the same, but -DWITH_DB > > # enables the MySQL code. By default, that one is commented out > > # change the comment chars to activate it if you need MySQL! > > # In this case, also look down further to uncomment the libs > > #CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce > > CFLAGS= $(RPM_OPT_FLAGS) -O3 -DSYSV -fomit-frame-pointer -Wall -fno-strength-reduce -DWITH_DB > > LDFLAGS= -s > > > > INSTALL = install > > BINDIR = /usr/sbin > > MANDIR = /usr/share/man > > > > # Uncomment the following to use mysql. > > LIBS = -lmysqlclient #/var/lib/mysql/mysql > > > > # There is one report that under an all ELF system there may be a need to > > # explicilty link with libresolv.a. If linking syslogd fails you may wish > > # to try uncommenting the following define. > > # LIBS = /usr/lib/libresolv.a > > > > # The following define determines whether the package adheres to the > > # file system standard. > > FSSTND = -DFSSTND > > > > # The following define establishes ownership for the man pages. > > # Avery tells me that there is a difference between Debian and > > # Slackware. Rather than choose sides I am leaving it up to the user. > > MAN_OWNER = root > > # MAN_OWNER = man > > > > # The following define establishes the name of the pid file for the > > # rsyslogd daemon. The library include file (paths.h) defines the > > # name for the rsyslogd pid to be rsyslog.pid. A number of people have > > # suggested that this should be rsyslogd.pid. You may cast your > > # ballot below. > > SYSLOGD_PIDNAME = -DSYSLOGD_PIDNAME=\"rsyslogd.pid\" > > > > SYSLOGD_FLAGS= -DSYSLOG_INET -DSYSLOG_UNIXAF -DNO_SCCS ${FSSTND} \ > > ${SYSLOGD_PIDNAME} > > SYSLOG_FLAGS= -DALLOW_KERNEL_LOGGING > > DEB = > > > > .c.o: > > ${CC} ${CFLAGS} -c $*.c > > > > all: syslogd > > > > test: syslog_tst tsyslogd > > > > install: install_man install_exec > > > > syslogd: syslogd.o pidfile.o template.o stringbuf.o srUtils.o outchannel.o > > ${CC} ${LDFLAGS} -o syslogd syslogd.o pidfile.o template.o outchannel.o stringbuf.o srUtils.o ${LIBS} > > > > syslog_tst: syslog_tst.o > > ${CC} ${LDFLAGS} -o syslog_tst syslog_tst.o > > > > tsyslogd: syslogd.c version.h template.o outchannel.o stringbuf.o srUtils.o > > $(CC) $(CFLAGS) -g -DTESTING $(SYSLOGD_FLAGS) -o tsyslogd syslogd.c pidfile.o template.o outchannel.o stringbuf.o srUtils.o $(LIBS) > > > > srUtils.o: srUtils.c srUtils.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c srUtils.c > > > > stringbuf.o: stringbuf.c stringbuf.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c stringbuf.c > > > > template.o: template.c template.h stringbuf.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c template.c > > > > outchannel.o: outchannel.c outchannel.h stringbuf.h liblogging-stub.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c outchannel.c > > > > syslogd.o: syslogd.c version.h template.h outchannel.h > > ${CC} ${CFLAGS} ${SYSLOGD_FLAGS} $(DEB) -c syslogd.c > > > > syslog.o: syslog.c > > ${CC} ${CFLAGS} ${SYSLOG_FLAGS} -c syslog.c > > > > syslog_tst.o: syslog_tst.c > > ${CC} ${CFLAGS} -c syslog_tst.c > > > > clean: > > rm -f *.o *.log *~ *.orig > > > > clobber: clean > > rm -f syslogd klogd ksym syslog_tst oops_test TAGS tsyslogd tklogd > > > > install_exec: syslogd > > ${INSTALL} -b -s syslogd ${DESTDIR}${BINDIR}/rsyslogd > > > > install_man: > > ${INSTALL} rsyslogd.8 ${DESTDIR}${MANDIR}/man8/rsyslogd.8 > > ${INSTALL} rsyslog.conf.5 ${DESTDIR}${MANDIR}/man5/rsyslog.conf.5 > > test# > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog From dennisolvany at gmail.com Mon Jun 27 18:42:57 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Mon, 27 Jun 2005 11:42:57 -0500 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD5.4 References: <001701c57b2f$ee50a8b0$0366a8c0@d> <1119887925.2097.1.camel@rh9lt.intern.adiscon.com> <003b01c57b32$9e356d90$0366a8c0@d> <1119889042.2097.3.camel@rh9lt.intern.adiscon.com> <1119889425.2097.7.camel@rh9lt.intern.adiscon.com> Message-ID: <000f01c57b37$4669be40$0366a8c0@d> Thanks for quick fix. No rush, though. Just fiddling around. Don't even plan on employing a new version until I set up a new machine, which will be who-knows when. Was thinking of writing a little guide for 090 if necessary. Will wait for next release to do further testing. From rgerhards at hq.adiscon.com Tue Jun 28 16:11:25 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Tue, 28 Jun 2005 16:11:25 +0200 Subject: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile Difficulties onFreeBSD5.4 Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E34BA@grfint2.intern.adiscon.com> Dennis, I've just uploaded 0.9.1 - official announcement to follow. It is available at http://download.adiscon.com/rsyslog-0.9.1.tar.gz This version also contains some other fixes so that it compiles cleaner under FreeBSD (see NEWS). No source modifications have now been needed in my environment. It would be great if you could give it a quick test. Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Monday, June 27, 2005 6:43 PM > To: rsyslog at lists.adiscon.com > Subject: Re: [rsyslog] Rsyslog-0.9.0 w/MySQL Compile > Difficulties onFreeBSD5.4 > > Thanks for quick fix. No rush, though. Just fiddling around. > Don't even plan on employing a new version until I set up a > new machine, which will be who-knows when. Was thinking of > writing a little guide for 090 if necessary. Will wait for > next release to do further testing. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Tue Jun 28 17:05:15 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Tue, 28 Jun 2005 10:05:15 -0500 Subject: [rsyslog] Rsyslog-0.9.1 w/MySQL on FreeBSD 5.4: One Issue Message-ID: <000801c57bf2$cb067fb0$0366a8c0@d> FreeBSD 5.4 minimal install (fresh). No Linux Binary Compatibility. Mysql41-client installed using, "pkg_add -r mysql41-client". Configured Makefile lines 20, 21, 29. Compile: OK. Fixed Runtime Error: sample.conf [/etc/rsyslog.conf] line 178: *.* >hostname,dbname,userid,password; #requires semi-colon Debug Output: test# rsyslogd -d Allocated parts table for 2656 file descriptors. Starting. Called init. cfsysline --> template TraditionalFormat,"%timegenerated% %HOSTNAME% %syslogtag%%msg:::drop-last-lf%\n" cfsysline --> template precise,"%syslogpriority%,%syslogfacility%,%timegenerated:::fulltime%,%HOSTNAME%,%syslogtag%,%msg%\n" Invalid field option 'fulltime' specified - ignored. cfsysline --> template RFC3164fmt,"<%PRI%>%TIMESTAMP% %HOSTNAME% %syslogtag%%msg%" cfsysline --> template wallmsg,"\r\n\7Message from syslogd@%HOSTNAME% at %timegenerated% ...\r\n %syslogtag%%msg%\n\r" cfsysline --> template WinSyslogFmt,"%HOSTNAME%,%timegenerated:1:10:date-rfc3339%,%timegenerated:12:19:date-rfc3339%,%timegenerated:1:10:date-rfc3339%,%timegenerated:12:19:date-rfc3339%,%syslogfacility%,%syslogpriority%,%syslogtag%%msg%\n" cfsysline --> template dbFormat,"insert into SystemEvents (Message, Facility,FromHost, Priority, DeviceReportedTime, ReceivedAt, InfoUnitID, SysLogTag) values ('%msg%', %syslogfacility%, '%HOSTNAME%',%syslogpriority%, '%timereported:::date-mysql%', '%timegenerated:::date-mysql%', %iut%, '%syslogtag%')",sql cfline(*.* >mysql.carcass.us,rsyslogtest,dennisolvany,password) symbolic name: * ==> 255 leading char in action: > in init() - WITH_DB case logmsg: syslog.err<43>, flags 4, from test, msg rsyslogd: Could not find template 'password' Called fprintlog, logging to CONSOLE Called fprintlog, logging to TTY Jun 28 14:23:27 test rsyslogd: Could not find template 'password' rsyslogd: Could not find template 'password' template 'password' Segmentation fault (core dumped) test# After above procedures, rsyslog-0.9.1 is logging to database. Seems to be running properly. From rgerhards at hq.adiscon.com Tue Jun 28 17:10:13 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Tue, 28 Jun 2005 17:10:13 +0200 Subject: [rsyslog] Rsyslog-0.9.1 w/MySQL on FreeBSD 5.4: One Issue Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E34BB@grfint2.intern.adiscon.com> Will see that I remove the semicolon bug soon. Can't be a big issue, but obviously annoying... All in all, I think I will move the database write to outchannel definitions, but that's more work ;) well... a lot to do. The next things I'd like to do is support for larger size messages and TCP logging. let me see ;) Thanks for the test, Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Tuesday, June 28, 2005 5:05 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] Rsyslog-0.9.1 w/MySQL on FreeBSD 5.4: One Issue > > FreeBSD 5.4 minimal install (fresh). > No Linux Binary Compatibility. > Mysql41-client installed using, "pkg_add -r mysql41-client". > > Configured Makefile lines 20, 21, 29. > Compile: OK. > > Fixed Runtime Error: > > sample.conf [/etc/rsyslog.conf] > line 178: *.* >hostname,dbname,userid,password; > #requires semi-colon > > Debug Output: > > test# rsyslogd -d > Allocated parts table for 2656 file descriptors. > Starting. > Called init. > cfsysline --> template TraditionalFormat,"%timegenerated% > %HOSTNAME% %syslogtag%%msg:::drop-last-lf%\n" > cfsysline --> template > precise,"%syslogpriority%,%syslogfacility%,%timegenerated:::fu lltime%,%HOSTNAME%,%syslogtag%,%msg%\n" > Invalid field option 'fulltime' specified - ignored. > cfsysline --> template RFC3164fmt,"<%PRI%>%TIMESTAMP% > %HOSTNAME% %syslogtag%%msg%" > cfsysline --> template wallmsg,"\r\n\7Message from > syslogd@%HOSTNAME% at %timegenerated% ...\r\n %syslogtag%%msg%\n\r" > cfsysline --> template > WinSyslogFmt,"%HOSTNAME%,%timegenerated:1:10:date-rfc3339%,%ti megenerated:12:19:date-rfc3339%,%timegenerated:1:10:date-> rfc3339%,%timegenerated:12:19:date-rfc3339%,%syslogfacility%,% > syslogpriority%,%syslogtag%%msg%\n" > cfsysline --> template dbFormat,"insert into SystemEvents > (Message, Facility,FromHost, Priority, DeviceReportedTime, > ReceivedAt, InfoUnitID, SysLogTag) values ('%msg%', > %syslogfacility%, '%HOSTNAME%',%syslogpriority%, > '%timereported:::date-mysql%', > '%timegenerated:::date-mysql%', %iut%, '%syslogtag%')",sql > cfline(*.* > >mysql.carcass.us,rsyslogtest,dennisolvany,password) > symbolic name: * ==> 255 > leading char in action: > > in init() - WITH_DB case > logmsg: syslog.err<43>, flags 4, from test, msg rsyslogd: > Could not find template 'password' > > Called fprintlog, logging to CONSOLE > Called fprintlog, logging to TTY > Jun 28 14:23:27 test rsyslogd: Could not find template 'password' > rsyslogd: Could not find template 'password' > template 'password' > Segmentation fault (core dumped) > test# > > > After above procedures, rsyslog-0.9.1 is logging to database. > Seems to be running properly. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > From dennisolvany at gmail.com Wed Jun 29 14:38:34 2005 From: dennisolvany at gmail.com (Dennis Olvany) Date: Wed, 29 Jun 2005 07:38:34 -0500 Subject: [rsyslog] Add a Doc? Message-ID: <001201c57ca7$77a4aa30$0366a8c0@d> I was thinking that another cool website addition would be to publish the database schema along with the man pages. This could be helpful and informative to some users. From rgerhards at hq.adiscon.com Wed Jun 29 14:52:30 2005 From: rgerhards at hq.adiscon.com (Rainer Gerhards) Date: Wed, 29 Jun 2005 14:52:30 +0200 Subject: [rsyslog] Add a Doc? Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E34D3@grfint2.intern.adiscon.com> Dennis, definitely :). I've also just talked to the web folks, I'll get a separate page at www.rsyslog.com. That site will be driven by postnuke, so it will probably be (relatively) easy to update - even for you ;) I hope to have this in a few days... Rainer > -----Original Message----- > From: rsyslog-bounces at lists.adiscon.com > [mailto:rsyslog-bounces at lists.adiscon.com] On Behalf Of Dennis Olvany > Sent: Wednesday, June 29, 2005 2:39 PM > To: rsyslog at lists.adiscon.com > Subject: [rsyslog] Add a Doc? > > I was thinking that another cool website addition would be to > publish the database schema along with the man pages. This > could be helpful and informative to some users. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog >