On Thu, Apr 19, 2018 at 1:53 PM, Yichao Yu <[email protected]> wrote: > On Thu, Apr 19, 2018 at 1:42 PM, Martin Braun via USRP-users > <[email protected]> wrote: >> On 04/19/2018 10:39 AM, Marcus D. Leech via USRP-users wrote: >>> On 04/19/2018 01:37 PM, Yichao Yu wrote: >>>> The page still doesn't mention fastpath message though and I though >>>> there was a previous email on this list that mentions such control was >>>> possible when the new logging system was just implemented. >>> Perhaps Martin can say a word or two about how that is handled in the >>> new logging system... >> >> To disable fastpath messages: >> >> cmake -DUHD_LOG_FASTPATH_DISABLE=OFF > > so there's no way to "Suppressing output at runtime"? > >> And as Marcus says, fastpath also goes to stderr, so you can direct it >> /dev/null. > > That's like throw the baby out with the bath water.... The application > is also using `stderr` for useful output.....
Ah, and I finally find that email I was referring to again, http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2017-April/024653.html which mentioned that > - Main reason for customers registering custom message handlers was to > turn off logging to stdout and stderr. This is now a built-in feature; > we can control logging levels and other things at > configure/compile-time, and at runtime both via environment variables > and API calls. Unless it is recommented for everyone to compile their own library instead of using binary packages, I don't think a compile time option is a usable solution to this need. (And if one has to compile the library, why does the ettus uhd PPA exists....) > >> >> -- M >> >> _______________________________________________ >> USRP-users mailing list >> [email protected] >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com _______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
