On Sat, 22 Jun 2013 23:26:12 +0200, Luca Barbato <[email protected]> wrote: > On 06/22/2013 11:16 PM, Derek Buitenhuis wrote: > > On 2013-06-22 5:11 PM, Luca Barbato wrote: > >> If you are already using syslog for the rest of your process chain comes > >> quite handy. > > > > Polluting the *system* log with the vast amounts of spam from avconv, which > > is a random userland utility, seems a bit Bad™ to me... but I guess to each > > his own. I won't bikeshed ideology. > > Imagine avconv is a daemon or acting as such (yep more about it). >
Well avconv is not a daemon. Experience tells us that attempts to use it as such mostly ends in tears. It's already quite a kitchensink, adding random features quite unrelated to what it's supposed to be doing doesn't strike me as a very good idea. You say the advantage here is that you can extract the logging level. Avconv output or logging levels of anything it prints are not fixed and cannot be relied upon. So I fail to see any way in which this can be used properly. -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
