diff options
| author | Rainer Gerhards <rgerhards@adiscon.com> | 2010-03-21 18:52:51 +0100 |
|---|---|---|
| committer | Rainer Gerhards <rgerhards@adiscon.com> | 2010-03-21 18:52:51 +0100 |
| commit | dccadb677c5a6b8379f631e4c1f14c8c4089d4a6 (patch) | |
| tree | 8a1beb0a96dae348762322e5d3917dc5c5c87e80 /tests | |
| parent | 95cde529cc2d2aab2047f5ab2c52d9cd8ba23f31 (diff) | |
| download | rsyslog-dccadb677c5a6b8379f631e4c1f14c8c4089d4a6.tar.gz rsyslog-dccadb677c5a6b8379f631e4c1f14c8c4089d4a6.tar.xz rsyslog-dccadb677c5a6b8379f631e4c1f14c8c4089d4a6.zip | |
exp: made omfile ensure that it is not called twice in parallel on the same file instance
In theory, the rsyslog core should never call in parallel into an output
module for the same instance. However, it looks like this seems to happen
under (strange?) circumstances. I have now enhanced omfile so that it guards
itself against being called in parallel on the same instance data. This is
done to help troubleshooting and may stay as an interim solution if it
proves to solve an anomaly we see in at least one installation (to trigger
this problem, an extremely large traffic volume is needed).
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions