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). And imagine you are using metalog or similarly nice logging daemon so you have your /var/log/avconv/current and such to track it. Yep I'm one of those people even using the syslog for their webserver when they can. > My only question is: How portable is this code? syslog stuff seems > intrinsically > unportable to me, but it *is* POSIX after all. The code as-is works on linux, bsd and brothers including macosx and had the vsyslog shortcut that might make it not build on certain systems w/out adding #define _BSD_SOURCE. Basically anything but windows should be able to use it. lu _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
