Re: [Linuxptp-devel] [PATCH RFC 0/3] Optional prefix for ptp4l/phc2sys log messages

2016-11-02 Thread Richard Cochran
On Tue, Oct 18, 2016 at 10:36:54AM +0200, Miroslav Lichvar wrote: > On Mon, Oct 17, 2016 at 08:46:22PM +, Keller, Jacob E wrote: > > 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

Re: [Linuxptp-devel] [PATCH RFC 0/3] Optional prefix for ptp4l/phc2sys log messages

2016-10-18 Thread Miroslav Lichvar
On Mon, Oct 17, 2016 at 08:46:22PM +, Keller, Jacob E wrote: > 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

Re: [Linuxptp-devel] [PATCH RFC 0/3] Optional prefix for ptp4l/phc2sys log messages

2016-10-17 Thread Keller, Jacob E
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

[Linuxptp-devel] [PATCH RFC 0/3] Optional prefix for ptp4l/phc2sys log messages

2016-10-17 Thread Miroslav Lichvar
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