- syslog-ng - lists.balabit.hu

genh0
by Julian Gordon 15 Nov '99

15 Nov '99

It is mentioned in the documents: "syslog-ng supports keeping of hash values along side the actual log file. To initialize hashing for the first time, you will need to use the program genh0, which gener- ates the initial hash for a log file based on random salt and the passphrase you enter. " However, the distribution does not some to include this program, nor is this program available on the source site. What's up? Julian

2 1

qmail.
by Jacob Zehnder 13 Nov '99

13 Nov '99

ahoy, i recently switched to syslog-ng and am loving it, though im having one small problem. i use qmail and am logging it like this destination qmail { file ("/var/log/maillog" compress(on) sync(0) log_fifo_size(10)); }; it logs fine to /var/log/maillog.. only problem is it also wont stop logging to /var/log/messages. i was wondering if theres a way i can restrict qmails access to /var/log/messages in syslog-ng without having to do some knarly perm changes :> thank yah --jacob * * * * * * * * * * * * * * * * * * Jacob Zehnder * * * * * * * * * Grill Master * * * * * * * * "The dude abides." * * * * 'The Big Lebowski' * * * * * * * * * * * * * *

2 1

CDMA手机包月卡你办了吗？288元可打足一个月的包月卡！详情请电26368636咨询
by hello 06 Nov '99

06 Nov '99

CDMA包月卡包含市区内打进打出的话费（不含长途费，和短信息）：手续费300元市话通500元送400话费详情请电26368636咨询

1 0

Re: syslog-ng
by Balazs Scheidler 01 Nov '99

01 Nov '99

> >Hi > > > >Im trying to build syslog-ng on an SGI Indy running irix-6.5 but the > >build fails with: > > > >ld32: ERROR 33: Unresolved text symbol "door_revoke" -- 1st referenced > >by afstreams.o. > > Use linker option -v to see when and which objects, archives and > >dsos are loaded. > > > >I dont think irix has any of the door functions. > > > >TIA > > > >BB > > > I have just gone to compile syslog-ng on Digital Unix 4.0e and again > there appears to be no door functions/files available. Do you think door > files will come to IRIX and DU before syslog-ng does? Is there anything > we can do? Sorry for not answering this message so long, but I'm a bit overloaded nowadays. So the problem might be that you have a door.h available somewhere in your include directory, and this makes the configure script think, that you have doors. What you could do temporarily (until I fix this problem): * Rename /usr/include/door.h to something else, and rerun configure, but first delete the config.cache file in the syslog-ng directory. * Edit the file config.h after the configure script has been run, and change the line #define HAVE_DOOR_H 1 to #undef HAVE_DOOR_H and rebuild. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

release plans
by Balazs Scheidler 27 Oct '99

27 Oct '99

Hi, I'm planning to release version 1.2.0 of syslog-ng, and start a fork a new development cycle. I was waiting so long to fix Solaris support, but decided to release 1.2.0 anyhow, Solaris support will be fixed later. The recently added macro support will be released as 1.3.0, and development will continue on that branch. So 1.2.0 as I release it now should work without problems on *BSD and Linux, and using a workaround on Solaris. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

Re: Welcome To "syslog-ng"!
by Gael Martinez 27 Oct '99

27 Oct '99

Hi I have some trouble with syslog-ng and Solaris 7 x86 Generic_106542-07 I put that in the .conf file source src { sun-streams("/dev/log" door("/etc/.syslog_door")); }; and when I launch the daemon I get that do_init_afstreams_source: Cannot open sun-stream /dev/log (Operation not supported on transport endpoint) Error initializing configuration, exiting. Terminated Any Clue ? Regards Gael -- Gael MARTINEZ Spacestar Communications, Inc. Dial-up to DS-3 Serving - MN WI ND MI IL www.spacestar.net / Fax (612) 996-0123

2 1

destination filename macro expansion
by Balazs Scheidler 26 Oct '99

26 Oct '99

Hi, I've worked a bit on syslog-ng and implemented macro expansion on destination filenames. It's not complete yet, but anyone interested may play with it a bit. Here's an example how to use this: ----------------------------------------------------- options { long_hostnames(on); time_reopen(2); }; source src { unix-stream("log1"); internal(); }; destination all { file("/var/log/$HOST.log"); }; log { source(src); destination(all); }; ------------------------------------------------------ You'll need to grab the source from the CVS to use this. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

Re: Problems configuring syslog-ng
by Balazs Scheidler 22 Oct '99

22 Oct '99

On Fri, Oct 22, 1999 at 11:35:42PM +1000, John Doe wrote: > Hi, > I just downloaded syslog-ng 1.1.33 and I'm trying to run it on FreeBSD > 3.3. syslog-ng compiles and installs without any problems at all, but nice to hear. > when it comes to running it I get no log entries. The following is my > syslog-ng.conf file which I am using, and I'd guess that I've made some > terrible problem there, if you could please point me to where I am going > wrong it would be much appreciated. > > #----cut----- > options { sync(0); time_reopen(10); log_fifo_size(100) }; > > source src { > unix-stream("/var/run/log"); > internal(); > }; > > destination everything { > file("/var/log/newsyslog" compress(on) sync(0) log_fifo_size(10)); > }; > > log { source(src); destination(everything); }; > #----cut------ The problem is that BSD systems use unix-dgram sockets to send local log messages. So your source statement should look like: source src { unix-dgram("/var/run/log"); internal(); }; This is described in the INSTALL file: BSDi: ----- BSD is similar to Linux (or vice-versa Linux is similar to BSD, but this is another issue), so BSD has also a unix socket for log communication, but it's of type SOCK_DGRAM, and it is located at /var/run/log. So the source statement you are looking for is: source stdlog { unix-dgram("/var/run/log"); }; Or in the .sgml generated documentation doc/sgml/syslog-ng.txt: > I intend to run syslog-ng over (remote logging) my LAN (Linux, OpenBSD > and FreeBSD machines) when I get it going with what-ever > encryption/hashing syslog-ng supports. Sorry for the poor question, > however there doesn't appear to be much documention included with > syslog-ng. Suggestion: how about you include 5 sample setup files which > syslog-ng users have put into effect on their systems in a doc/samples > directory. If you cannot help me with my log-configuration file above, > perhaps you could send me your syslog-ng config file (well actaully I'd > be interested in seeing how you've implemented syslog-ng anway). You can find a demo configuration file which includes all possible parameters syslog-ng parses (doc/syslog-ng.conf.demo), even those syslog-ng doesn't implement yet (compress, encrypt etc. come to mind), and another one meant as a default configuration file: doc/syslog-ng.conf.sample -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

Redhat init script?
by David Robinson 22 Oct '99

22 Oct '99

Has anyone made up a standard syslog-ng start/stop init script for Redhat 6? I noticed there was a debian one.. I'm currently just starting syslog-ng from the rc.local script. If not I'll create one but I don't want to do it if someone has already done it. Regards, David Robinson.

3 5

building syslog-ng on irix-6.5, door functions
by Bevan Broun 21 Oct '99

21 Oct '99

Hi Im trying to build syslog-ng on an SGI Indy running irix-6.5 but the build fails with: ld32: ERROR 33: Unresolved text symbol "door_revoke" -- 1st referenced by afstreams.o. Use linker option -v to see when and which objects, archives and dsos are loaded. I dont think irix has any of the door functions. TIA BB -- Bevan Broun ph (08) 9380 1587 Computer Systems Officer fax (08) 9380 1065 Dept. Electrical and Electronic Engineering University of Western Australia rm. G70

1 0