diff options
| author | Pavel Levshin <pavel@levshin.spb.ru> | 2013-11-07 12:42:37 +0100 |
|---|---|---|
| committer | Rainer Gerhards <rgerhards@adiscon.com> | 2013-11-07 12:42:37 +0100 |
| commit | ded6957225ae23f096dfa842caf28c0f34e9512c (patch) | |
| tree | 4dc527ce4280ca1445fb7dbd895e40de75e3e48f /tests/daqueue-persist.sh | |
| parent | 248e6bf819312e6ab43df0e46269080a8518a2f9 (diff) | |
| download | rsyslog-ded6957225ae23f096dfa842caf28c0f34e9512c.tar.gz rsyslog-ded6957225ae23f096dfa842caf28c0f34e9512c.tar.bz2 rsyslog-ded6957225ae23f096dfa842caf28c0f34e9512c.zip | |
bugfix: regular workers are no longer started if DA worker is active
form mail:
Look, below, if it is time to activate DA worker, we call it explicitly. But in this case we do not advise regular workers. They are likely already running at this point, but it is not guaranteed. What if, for example, the system is set to start additional workers when the queue is going over high watermark? What if HighWatermark is set to 1? Regular workers will not be started, and DA worker may fail. Thus, it is reasonable to advise regular workers even if we are going DA.
Diffstat (limited to 'tests/daqueue-persist.sh')
0 files changed, 0 insertions, 0 deletions