Hello,
While using udpcast, I found out that it may be very verbose on stderr, even if a logfile is specified.
This turns out to be a problem for our embedded application where the stderr is a (slow) serial port.
So here is a patch which replace every occurrence of fprint(sdterr,...) by the flprintf() function defined in log.c.
I thought it might be of some use for people.
(This patch also happen to cleanup the blank spaces at end of lines)
Julien
Hello Julien
On 2010-09-13 11:50, Julien Aube wrote:
Hello,
While using udpcast, I found out that it may be very verbose on stderr, even if a logfile is specified.
This turns out to be a problem for our embedded application where the stderr is a (slow) serial port.
So here is a patch which replace every occurrence of fprint(sdterr,...) by the flprintf() function defined in log.c.
I thought it might be of some use for people.
(This patch also happen to cleanup the blank spaces at end of lines)
Julien
In version 20110710, most messages now go to the log, if one is specified, with 2 notable exception:
- prompts for an action ("Press any key to start sending data.") - progress info.
However, progress info can now be suppressed entirely using the new --no-progress flag
Regards,
Alain
-
Alain Knaff -
Julien Aube