- syslog-ng - lists.balabit.hu

Compile Error for syslog-ng-1.1.30
by georg.funke＠netcologne.de 06 Aug '99

06 Aug '99

Hi, when i try to syslog-ng-1.1.30, i get the following error: utils.c: In function `getutent': utils.c:70: syntax error before `ut' utils.c:77: `ut' undeclared (first use in this function) utils.c:77: (Each undeclared identifier is reported only once utils.c:77: for each function it appears in.) utils.c:79: warning: control reaches end of non-void function My System is Redhat 6.0 with kernel 2.2.10 and the compiler is gcc-2.95. Can you help me why i get this error? Thanks Georg -- Georg Funke Crowns & Flames SDC Cologne, Germany; http://www.geocities.com/Colosseum/4893 "Friendship is Square Dancing's greatest Reward"

3 4

syslog-ng 1.1.30
by Balazs Scheidler 04 Aug '99

04 Aug '99

Hi, I have released syslog-ng 1.1.30 and the corresponding libol version 0.2.2. Changes include: * Sun-Streams support cleaned up, it does compile (and it is really compiled in), and should work, but it's now completely untested. Please report success/failure you may had. * NetBSD didn't have getutent() calls, so I implemented them in utils.c. Again this is untested, I have no *BSD machines lieing around. Nothing has changed in libol, only a new symbol has been made public. You can find these at the usual place: http://www.balabit.hu/products/syslog-ng And the tarballs & pgp signatures at: http://www.balabit.hu/downloads/syslog-ng/source -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

2 1

Re: syslog-ng memory usage
by Balazs Scheidler 04 Aug '99

04 Aug '99

On Tue, Aug 03, 1999 at 09:05:04AM -0400, mr(a)noc.1st.net wrote: > Here's what it looked like today: > > root 13410 0.3 54.2 70452 69716 ? S Aug02 5:00 syslog-ng > > I've attached the conf file. What kind of system do you have? I mean is it Linux or something else? I tried to track down that memory leak, but syslog-ng was not growing at all for any of the stresstests I used. (I tried both the file and the udp source driver, and file destination driver) I see the following possibilities: 1) your malloc() implementation in the libc doesn't like fragmentation. syslog-ng allocates lots of memory blocks, but frees them as well, maybe your malloc() implementation may have problems with fragmented memory. You may have a look at GNU Malloc, which is AFAIR available separate from libc, and can be compiled to a standalone shared lib. 2) The output queues of syslog-ng begin to fill up, because it is unable to handle the load. This should not be a problem though, since by default the output queues are 100 entries long for each file. (using 200 bytes as an estimated length of a message we get 20*100*200 = 400000 Bytes for twenty file destinations) 3) The libc itself leaks somewhere. I use GNU libc 2.1.1, GNU/Linux Debian, potato distribution. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

2 1

.. beginner question src Sol 7 (intel)
by Werner Dundler 04 Aug '99

04 Aug '99

hello after trying to get a usefull logging with the standart solaris syslog i removed that damn program and install the newest version of syslog-ng. i compiled it (straight) using gcc and took a basic configuration and changed it. but i ran into one trouble.... my syslog-ng deamon runs fine and when i send a -HUP to it i get a nice message that syslog-ng initiolized a new configuration. but i can´t get it to log system messages. i used: source src { unix-stream("/dev/log"); internal(); }; and source src { unix-stream("/etc/.syslog_door"); internal(); }; i tested both configurations with # logger -t auth.debug "bla" .. but never got a response into my logfile. system is a solaris 7 intel machine. filter and log for auth.* should be up and running .... does anybody know what i did wrong ? ciao and thx werner

2 1

Syslog ng 1.1.29 under Solaris 7
by Rob See 04 Aug '99

04 Aug '99

I've been attempting to get syslog-ng to run under solaris 7, and have been running into the same problems that were mentioned in a previous message. The config script seems to only be checking for stropts.h and not strlog.h, so the sun-stream support isn't getting compiled in no matter what. When I change afstream.c so that it will compile that support in, it has problems with tmp not being defined. the line "char tmp[MAX_LINE + 1]" around line 70 is commented out. When I uncomment it, it compiles, but segfaults any time a message is sent to it in _vformat_length. Does anyone have any ideas that could help ? -Rob See

1 0

Re: [syslog-ng] Re: syslog-ng 1.1.29 and Solaris 7 support
by Balazs Scheidler 04 Aug '99

04 Aug '99

> > > On Mon, Aug 02, 1999 at 01:00:49PM -0400, Mike Wade wrote: > > > > How do I enable Solaris 7 internal syslog support with syslog-ng 1.1.29? > > > > Currently, I get an error saying 'sun-streams support not compiled in > > > > (STREAM=/dev/log)' > > > > Me too. > > > > > The configure script detects whether you have the necessary header files or > > > not. You need strlog.h and stropts.h, and for door support you need door.h. > > > Check the config.log file and configure output why those files were not > > > found. > > > > I don't know usage of configure very well. > > But, I think syslog-ng's configure is not check about strlog.h. > > What does the script 'make_class' require? That also appears to be a > problem for me. make_class requires scheme shell to run, but it's required only for syslog-ng development, nothing else. scsh is available in source at ftp://ftp-swiss.ai.mit.edu/pub/su/scsh/ -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

Re: syslog-ng 1.1.29 and Solaris 7 support
by Balazs Scheidler 02 Aug '99

02 Aug '99

On Mon, Aug 02, 1999 at 01:00:49PM -0400, Mike Wade wrote: > How do I enable Solaris 7 internal syslog support with syslog-ng 1.1.29? > Currently, I get an error saying 'sun-streams support not compiled in > (STREAM=/dev/log)' The configure script detects whether you have the necessary header files or not. You need strlog.h and stropts.h, and for door support you need door.h. Check the config.log file and configure output why those files were not found. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

Re: Syslog-ng: [wishlitst ;)] make it color. :)
by Balazs Scheidler 02 Aug '99

02 Aug '99

On Sat, Jul 31, 1999 at 11:24:11PM +0200, Dawid Kuroczko wrote: > Hello! > > I have a suggestion, a feature I'd really like to see in a syslog > daemon, but I haven't found do far. Please make it use ANSI color > escapes ("\033[31;41;1m") while presenting messages to console, > for example to make important messages red, standard grey and > network green. I think it should be configurable, but I don't > know where. :) Maybe a special color foo { ... } section, or > maybe special additions in destination bar { ... } ? I think > you're the best person to decide. I'm sorry I cannot send you > a patch, but I'm to weak at C, unfortunately. :) Hi, I think this will be possible with the rewrite rules to be introduced in the 1.3.x series, but you'll have to wait for that a bit. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt

1 0

suggestion: format of logline
by Bjorn Andersson 27 Jul '99

27 Jul '99

Here is a feature that I have been missing from other syslog programs as well as syslog-ng: I would like to give as an option the format of the logline. It would, for instance, be nice to see the priority and facilty of the logline in the log. This way I would not need to have a lot of logfiles just so that that I afterwards could find out the priority and facility. This would also give me the possibility not to write out the host information, as this information is redundant if I only have a single host or if each host has its own directory of logfiles. Here's an example of such a line: Jul 27 04:53:10 daemon notice proftpd[7423]: FTP session closed. The configuration option could be something like: log_format("%m %d %t %f %l %m"); where %m = month %d = day %t = time %f = facility %l = level %m = message Please send any comments to me as well as the mailinglist. Regards, Björn -- Björn Andersson <bjorn(a)lifix.fi>

2 1

suggestion: sync in log statement
by Bjorn Andersson 27 Jul '99

27 Jul '99

I just tested syslog-ng. I think it is better than the standard syslogd and will start using it. I have two suggestions. I will post them in separate mails so that the discussion can go on in their own threads. Here's the first one: I would like to be able to put the sync option in log statements, instead of having a global value. This would give me the possibilty to buffer less important messages (for example frequent debug messages) and not buffer more critical messages (such as those with a priority of emerg and alert). Please send any comments to me as well as the mailinglist. Regards, Björn -- Björn Andersson <bjorn(a)lifix.fi>

1 1