| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
Conflicts:
tests/Makefile.am
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
is detected.
This change is considered important but small enough
to apply it directly to the stable version. [But it is a border case,
the change requires more code than I had hoped. Thus I have NOT tried
to actually catch all cases, this is left for the current devel
releases, if necessary]
|
| | |
| | |
| | |
| | |
| | |
| | | |
...when rsyslogd ran in forked mode (as usual!)
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | |
| | | |
which enables to talk to the rsyslog core at runtime. The current
implementation is only a beginning, but can be expanded over time
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Well, actually this and a lot of related things. I improved the
testbench so that the new capabilities are automatically tested and
also did some general cleanup. The current multiple tcp listener
solution will probably receive some further cleanup, too, but looks
quite OK so far. I also reviewed the way tcpsrv et all work, in
preparation of using this code for imdiag. I need to document the
findings, especially as the code is rather complicated "thanks" to
the combination of plain tcp and gssapi transport modes.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- added $GenerateConfigGraph configuration command which can be used
to generate nice-looking (and very informative) rsyslog configuration
graphs.
- added $ActionName configuration directive (currently only used for
graph generation, but may find other uses)
|
| | |
| | |
| | |
| | | |
... to utilize it. This work is not yet fully verified to be correct.
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | |
| | |
| | | |
There was a subtle bug that made all messages fill their HOSTNAME from
the source IP (which may be wrong in a long chain of relays) and not
by reading the message. This fixes it.
|
|/ /
| |
| |
| |
| |
| |
| | |
- building the necessary plumbing to support more functions with
decent runtime performance. This is also necessary towards the
long-term goal of loadable library modules.
- added new RainerScript function "tolower"
|
| |
| |
| |
| |
| | |
Now have removed the previous method, as really nobody should call
it any longer (and now nobody does ;)). Also did some other cleanup.
|
| |
| |
| |
| |
| |
| | |
- abided to code conventions
- fixed a potential segfault when regex library can not
be loaded
|
| |
| |
| |
| | |
Thanks to Arnaud Cornet for providing the idea and initial patch.
|
| |
| |
| |
| |
| |
| |
| |
| | |
to make sure only the minimum number of file handles is left open
during a exec call. This is not a 100% solution, as there are also
some fopen() calls and, more importantly, file descriptors opened
by libraries. But it is better than nothing (and it was quick, at
least until we run into platform hell, what we will for sure ;)).
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
tests/Makefile.am
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
worked on ways to provide a better test suite:
- added -T rsyslogd command line option, enables to specify a directory
where to chroot() into on startup. This is NOT a security feature but
introduced to support testing. Thus, -T does not make sure chroot()
is used in a secure way. (may be removed later)
- added omstdout module for testing purposes. Spits out all messages to
stdout - no config option, no other features
- modified $ModLoad statement so that for modules whom's name starts with
a dot, no path is prepended (this enables relative-pathes and should
not break any valid current config)
|
|/ /
| |
| |
| | |
where vsprintf() does not check for NULL pointers
|
|\ \ |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Unfortunatley, I do not have the full list of contributors
available. The patch set was compiled by Ben Taylor, and I made
some further changes to adopt it to the news rsyslog branch. Others
provided much of the base work, but I can not find the names of the
original authors. If you happen to be one of them, please let me
know so that I can give proper credits.
|
| |
| |
| |
| | |
new comparison operation "ereregex"
|
|\| |
|
| | |
|
|\| |
|
| |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
runtime/msg.c
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
net.h
plugins/imtcp/imtcp.c
plugins/imudp/imudp.c
runtime/net.c
runtime/rsyslog.h
tcps_sess.c
tcpsrv.c
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This was subtle, because getPRI is called as part of the debugging code
(always executed) in syslogd.c:logmsg.
|
|\ \ \ \
| |/ / /
|/| / /
| |/ /
| | | |
Conflicts:
tools/omfile.c
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
|
|\| | |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Added $PrivDropToGroup, $PrivDropToUser, $PrivDropToGroupID,
$PrivDropToUserID config directives to enable dropping privileges.
This is an effort to provide a security enhancement. For the limits of this
approach, see http://wiki.rsyslog.com/index.php/Security
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
... which permits to drop root privileges. This is not a completely
secure way of dropping permissions, e.g. the group permissions need
to be dropped, too. Also, there are several vulnerability Windows (see
code comments). Finally, at least the imklog module on linux does
not work when privileges are dropped. This code may still be a
valuable addition, and so I have created an experimental branch so
that people can check it out.
|
| | |
| | |
| | |
| | |
| | | |
...which enables to configure HUP to be either a full restart
or "just" a leightweight way to close open files
|
| | |
| | |
| | |
| | |
| | |
| | | |
This enables us to use more efficient calling conventions and
also helps us keep the on-disk structure of a msg object more
consistent in future releases.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Message parsing is now done as part of main message queue worker
processing (was part of the input thread) This should also improve
performance, as potentially more work is done in parallel.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This enhances performance and, as some have pointed out, is
probably also more consistent with what users expect how
the various output-timestamp related function should work. This
commit needs some more testing.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
...which enables to work with
less acurate timestamps in favor of performance. This enables querying
of the time only every n-th time if imudp is running in the tight
receive loop (aka receiving messsages at a high rate)
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | |
| | |
| | | |
...this improves performance and consistency and also fixes
a bug where subsecond time properties generated by imfile, imklog and
internal messages could be slightly inconsistent.
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/debug.c
|
| | |
| | |
| | |
| | | |
multi-threading
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There was a wrong order of mutex lock operations. It is hard to
believe that really caused problems, but in theory it could and with
threading we often see that theory becomes practice if something is only
used long enough on a fast enough machine with enough CPUs ;)
|