I have now submitted a pull request to merge the "pseudofile" destination, I've now skipped the support for destination file templates, but that can be added later on when a more concrete usecase shows up. It already solves Valentijn's use-case, so it is useful as it is. I wanted to close some of my open branches :) -- Bazsi On Mon, Dec 16, 2013 at 1:20 PM, Gergely Nagy <algernon@balabit.hu> wrote:
Balazs Scheidler <bazsi@balabit.hu> writes:
- no template in the name of the file
Would it be possible to have templates in the filename? I can imagine cases where I'd write to a different file based on message properties.
Like, if I start to see alerts that stuff is timing out, I'd spin up my second CPU core (in a laptop setting, where I can't be bothered with proper monitoring, and want to (ab)use syslog-ng for that task).
- name of the driver, right now it is called procfile as it was the original use-case, however it works with stuff in /dev too, and might work with simple named pipes.
It also works with stuff in /sys, so procfile() is not a good name. I would suggest oneshot-file() or simply oneshot().
- right now the file must exist and is not created (e.g. it really requires an existing file); do we need that?
I do not think file creation is important in this case.
- do we need append mode in some cases - whether we need append mode (if we think of general files, this would probably be needed)
I don't think we do.
-- |8]
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
-- Bazsi