On Mon, 2016-10-17 at 16:33 +0200, Miroslav Lichvar wrote:
> When there are multiple instances of ptp4l or phc2sys running on the
> system, it's difficult to tell which message belongs to which
> instance. The first patch adds new options to ptp4l and phc2sys which
> can be used to specify a different prefix for each instance, so
> different instances can use different prefixes. One issue is that
> it's
> not possible to set the prefix in ptp4l config to its default value
> (empty string) and the setting can't be included in defaults.cfg.
> 

Is it possible to update configuration somehow to allow passing a
variable as "empty" which will assign it to empty string, and then
update your prefix code flow so that it correctly works and doesn't add
a " " when the string is actually empty? Not sure how easy it would be
to fix that or not.

Thanks,
Jake

> The second patch adds support for this feature to timemaster.
> 
> The third patch is an unrelated improvement in timemaster to exit
> early with an error message when an interface doesn't support neither
> HW nor SW timestamping. (The patch applies only with the second
> patch,
> so it's included here.)
> 
> Miroslav Lichvar (3):
>   Add options to prefix ptp4l and phc2sys log messages.
>   timemaster: prefix ptp4l and phc2sys messages.
>   timemaster: check support for SW time stamping.
> 
>  config.c     |  1 +
>  phc2sys.8    |  4 ++++
>  phc2sys.c    |  9 +++++++--
>  print.c      | 18 ++++++++++++++----
>  print.h      |  1 +
>  ptp4l.8      | 10 ++++++++++
>  ptp4l.c      |  9 ++++++++-
>  timemaster.c | 34 ++++++++++++++++++++++++++--------
>  8 files changed, 71 insertions(+), 15 deletions(-)
> 
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Reply via email to