On Thu, Jun 26, 2014 at 09:32:11AM +0200, Miroslav Lichvar wrote:
>
> BTW, is running two ptp4l instances in the same PTP domain a valid use
> case? Appending the number to the socket name would not help here. It
> looks like we might need a more general approach anyway.
Yes, I think it is a vali
On Wed, Jun 25, 2014 at 05:56:31PM +0200, Miroslav Lichvar wrote:
> On Wed, Jun 25, 2014 at 04:53:26PM +0200, Richard Cochran wrote:
> > Maybe it is better just to leave the uds path as is. After all, the
> > user (and his scripts) can set the names freely, even with .domainName
> > if desired.
>
On Wed, Jun 25, 2014 at 04:57:15PM +0200, Delio Brignoli wrote:
>
> We are running our own pmc client. I do not mind the incompatible change
> mainly
> because it will not catch us by surprise. However, I wonder if this counts as
> “policy” and should go in a shell script instead.
Okay, that is
On Wed, Jun 25, 2014 at 04:53:26PM +0200, Richard Cochran wrote:
> Personally, as an end user, I find it really annoying when these
> sorts of things change for no apparent reason. That is why I suggested
> keeping the default socket name.
I agree, but I think this wouldn't be the first time the p
Hi,
On 25 Jun 2014, at 16:39, Miroslav Lichvar wrote:
> On Wed, Jun 25, 2014 at 06:04:46AM +0200, Richard Cochran wrote:
>> On Mon, Jun 23, 2014 at 06:46:59PM +0200, Miroslav Lichvar wrote:
>>> This allows running phc2sys and pmc in multiple PTP domains at the same
>>> time. It also makes it easi
On Wed, Jun 25, 2014 at 04:39:47PM +0200, Miroslav Lichvar wrote:
> On Wed, Jun 25, 2014 at 06:04:46AM +0200, Richard Cochran wrote:
> > On Mon, Jun 23, 2014 at 06:46:59PM +0200, Miroslav Lichvar wrote:
> > > This allows running phc2sys and pmc in multiple PTP domains at the same
> > > time. It als
On Wed, Jun 25, 2014 at 06:04:46AM +0200, Richard Cochran wrote:
> On Mon, Jun 23, 2014 at 06:46:59PM +0200, Miroslav Lichvar wrote:
> > This allows running phc2sys and pmc in multiple PTP domains at the same
> > time. It also makes it easier to configure ptp4l, the uds_address
> > option doesn't n
On Mon, Jun 23, 2014 at 06:46:59PM +0200, Miroslav Lichvar wrote:
> This allows running phc2sys and pmc in multiple PTP domains at the same
> time. It also makes it easier to configure ptp4l, the uds_address
> option doesn't need to be set if domainNumber is different from other
> instances.
This
This allows running phc2sys and pmc in multiple PTP domains at the same
time. It also makes it easier to configure ptp4l, the uds_address
option doesn't need to be set if domainNumber is different from other
instances.
---
clock.c | 1 +
pmc.8| 3 ++-
pmc_common.c | 3 +++
ptp4l.8
