| 1 |
On Mon, Mar 23, 2009 at 2:49 PM, Steve <gentoo_sjh@×××××××.uk> wrote: |
| 2 |
> Steve wrote: |
| 3 |
>> |
| 4 |
>> Do others get this behaviour - is this a bug in syslog-ng? |
| 5 |
> |
| 6 |
> Sorry for the multiple posts... a slight error on my part. The sshguard |
| 7 |
> process wasn't running - a /bin/sh process trying to spawn it was running |
| 8 |
> (there was no link from /usr/local... to the binary) and when the binary |
| 9 |
> failed to execute - syslog-ng got itself into a tiz. Everything seems to |
| 10 |
> work fine when I correct the path to the program. |
| 11 |
> |
| 12 |
> Problem solved - but, I guess, this is a flaw in syslog-ng... I'd have hoped |
| 13 |
> it would generate an error message rather than behave as it did. |
| 14 |
|
| 15 |
I had a possibly similar problem a while back with syslog-ng going |
| 16 |
crazy when a certain daemon would crash (in my case it filled up the |
| 17 |
log wit about 60 gigabytes of the same thing repeated over and over, |
| 18 |
in addition to using massive CPU%). I switched to metalog and haven't |
| 19 |
had any problems since. |
Archives