| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
this is the counterpart to imuxsock, enabling fast local forwarding
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
doc/professional_support.html
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
runtime/conf.c
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | | |
they are now dropped as they always should have been
|
| | | |
|
| | | |
|
|\| | |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | | |
thanks to Anthony Edwards for pointing the problems out
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
replaced atomic operation emulation with new code. The previous code
seemed to have some issue and also limited concurrency severely. The
whole atomic operation emulation has been rewritten.
|
| | |
| | |
| | |
| | | |
startup
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
more cleanup required, but things now basically work
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | |
| | |
| | |
| | | |
testbench
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
tools/omfile.c
tools/syslogd.c
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
tests/Makefile.am
tests/tcpflood.c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This, in default mode, caused buffered writing to be used, what
means that it looked like no output were written or partial
lines. Thanks to Michael Biebl for pointing out this bug.
|
| | | |
| | | |
| | | |
| | | | |
to test robustness
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
...message-induced off-by-one error (potential segfault) (see 4.6.2)
The analysis has been completed and a better fix been crafted and
integrated.
|
| | | |
| | | |
| | | |
| | | | |
32-bit platforms
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this enables us to work with the "usual" environment tweaks (for
debugging and other purposes), without the need for any special
handling in nettester itself
|
| |\| | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
accidently, the time zone information was kept inside some
to-be-checked-for responses
|
| |\| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also made sure that /dev/log will not be processed by imuxsock
when running under Solaris -- otherwise, the module may had
accidently deleted the log socket and cause problems.
|
| |\| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | | |
it permits to specifiy if asynchronous writing should be done or not
|
| |\| |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Some types of malformed messages could trigger an off-by-one error
(for example, \0 or \n as the last character, and generally control
character escaption is questionable). This is due to not strictly
following a the \0 or string counted string paradigm (during the last
optimization on the cstring class). As a temporary fix, we have
introduced a proper recalculation of the size. However, a final
patch is expected in the future. See bug tracker for further details
and when the final patch will be available:
http://bugzilla.adiscon.com/show_bug.cgi?id=184
Note that the current patch is considered sufficient to solve the
situation, but it requires a bit more runtime than desirable.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This bug was triggered by an open failure. The the cache was full and
a new entry needed to be placed inside it, a victim for eviction was
selected. That victim was freed, then the open of the new file tried. If
the open failed, the victim entry was still freed, and the function
exited. However, on next invocation and cache search, the victim entry
was used as if it were populated, most probably resulting in a segfault.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If multiple files try to create a directory at (almost) the same time,
some of them may fail. This is a data race and also exists with other
processes that may create the same directory. We do now check for this
condition and gracefully handle it.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
when dynaCache is enabled, the cache is full, a new entry needs to
be allocated, thus the LRU discarded, then a new entry is opend and that
fails. In that case, it looks like the discarded stream may be reused
improperly (based on code analysis, test case and confirmation pending)
|
| |/ /
| | |
| | |
| | | |
[backport of Stefen Sledz' patch for v5]
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
properly initialized.
However, in practice the loader initializes them with zero, the
desired value, so there were no actual issue in almost all cases.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
currently being accessed buffer could be overwritten with new data.
While this probably did not cause access violations, it could case loss
and/or duplication of some data (definitely a race with no deterministic
outcome)
|
| | |
| | |
| | |
| | |
| | | |
predicate was not properly checked when waiting for the background file
writer
|
| | |
| | |
| | |
| | |
| | | |
Internal data structures were not properly protected due to missing
mutex calls.
|