syslog-ng

Download

syslog-ng@lists.balabit.hu

October 2012

23 participants
52 discussions

[PATCH 1/2] json: Include all sources in _SOURCES
by Gergely Nagy 02 Oct '12

02 Oct '12

With the renaming and such the list of sources required to build the plugin got out of sync with reality. This patch corrects that, by adding the two new headers, and removing an old, unused one. Reported-by: Peter Czanik <czanik(a)balabit.hu> Signed-off-by: Gergely Nagy <algernon(a)balabit.hu> --- modules/json/Makefile.am | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/modules/json/Makefile.am b/modules/json/Makefile.am index 110b1b5..3338ff5 100644 --- a/modules/json/Makefile.am +++ b/modules/json/Makefile.am @@ -9,10 +9,11 @@ module_LTLIBRARIES = libjson-plugin.la libjson_plugin_la_SOURCES = \ format-json.c \ + format-json.h \ jsonparser.c \ + jsonparser.h \ jsonparser-grammar.y \ jsonparser-parser.c jsonparser-parser.h \ - json-plugin.h \ json-plugin.c libjson_plugin_la_CPPFLAGS = $(AM_CPPFLAGS) -- 1.7.9

1 1

Re: [syslog-ng] Syslog_NG
by Munh-Erdene E 02 Oct '12

02 Oct '12

Dears,,, Tnx for your quickly reply. :) I've 1 syslog-ng server and 8 clients in my network. Syslog-Ng server collecting all log of that clients. But syslog-ng can collecting only bash & sh shell logs. Can't collect all command log off csh, tcsh ... etc. other shells... BR--- Munkh-Erdene On Mon, Oct 1, 2012 at 10:47 PM, Gergely Nagy <algernon(a)balabit.hu> wrote: > Hi! > > I would like to ask you to write to the syslog-ng mailing list > (https://lists.balabit.hu/mailman/listinfo/syslog-ng) with syslog-ng > questions instead of contacting me directly. > > However, I will try to answer your mail here now, since I'm a little > confused about what you're trying to accomplish. > > Munh-Erdene E <munhluu(a)gmail.com> writes: > > > Syslog_NG works fine with bash & sh shells &&& writing clientlogs on > > server. > > > > But not working other shells, example: csh, ksh, tscsh ... > > > > In Client side: > > Add some config on *Vi /etc/bashrc * > > > > # log to syslog > > > > declare ME > > > > ME=$(awk -v val=$UID -F ":" '$3==val{print $1}' /etc/passwd) > > > > export PROMPT_COMMAND='{ msg=$(history 1 | { read x y; echo $y; }); > logger > > -p local5.info "CMDLOG PWD=$PWD ; USER=$ME ; COMMAND=$msg"; }' > > > > > > > > *2. Vi /etc/rsyslog.conf* > > > > > > > > *.info;mail.none;authpriv.none;cron.none @192.168.0.1 > > > > authpriv.* @192.168.0.1 > > > > Can you help me? pls > > I don't really see where syslog-ng comes into play here? Neither logger > nor rsyslog have much to do with syslog-ng itself. Nor should any shell > or whatsoever affect syslog-ng, as it's a daemon that should be started > at boot time, the shell you use need not have any effect on its > behaviour. > > -- > |8] > >

2 1