omprog: support spawning multiple instances

[rsyslog]

omprog: support spawning multiple instances

[radu-gheorghe]

Why would one spawn multiple instances of the same program and only use a single instance at once?

I'm not being ironic, I'm genuinely interested in whether this actually makes sense.

[rgerhards]

As i said... conversion aid to v8. so omprog works with v8 interface. If it
wouldn't support multiple instances, it wouldn't work.

For omfile it makes sense, as you really can't write concurrently.

Rainer

Sent from phone, thus brief.
Am 24.01.2014 13:01 schrieb "Radu Gheorghe" [email protected]:

Why would one spawn multiple instances of the same program and only use a
single instance at once?

I'm not being ironic, I'm genuinely interested in whether this actually
makes sense.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-33217398
.

[radu-gheorghe]

OK, then.

+1 to making multiple instances work in parallel by default.

[Ralnoc]

I think as long as you have the ability to use a single instance then it would work. I have a program I'm working on getting to work with omprog that would not handle multiple instances do to the nature of how it was designed by the original writers.

[rgerhards]

@radu-gheorghe Sorry... I was a bit confused about which conversation I was replying to ;) In the context of this issue, there are indeed some valid reasons (as @Ralnoc noted) to run in single thread-mode only. One of them is that the script connects to a destination that requires strict sequence (e.g. from a single IP).

It's notworthy that the rsyslog engine starts up workers for rulesets. So it is not possible to restrict a single action to just one worker (except if you create a dedicated ruleset for it, of course, but that's ugly). As such, we must be able to support "non-threadable" plugins in a way that prevents them from being executed concurrently.

[rgerhards]

This is now done, to be released with v8.1.6. It's a series of two commits, this is the last one: f753951

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.