Colm MacCarthaigh wrote:
Looks useful, but file://|/bin/foo would be very non-intuitive for piped
loggers, balancing the backwards compatibility might need a bit more, I
guess "pipe://" or "cmd://" schemes might make sense also.
True. I just used uri's as they seemed to just "fit." I'm not
particularly tied to the configuration interface. Any interest in me
changing it to use "cmd://"?
Also, since the default is file://, |/some/command would behave just as
it does now.
I would like to be able to use multiple custom loggers, rather than only
get one.
--
Brian Akins
Lead Systems Engineer
CNN Internet Technologies
