Never mind ... now that I go to add the code I see the "uds_address" option
already there.
Regards,
russ.
On Tue, May 27, 2014 at 5:11 PM, Russ Smith <russe...@google.com> wrote:
> Hi linuxptp people,
>
> I propose adding a feature (and submitting a patch) to allow uds_path to
> be set (the unix domain socket used for ptp4l management, currently defined
> in uds.c to "/var/run/ptp4l"). This will allow multiple instances of ptp4l
> to run on the same system, so that e.g. an instance of phc2sys can be
> configured to talk to just one of them. This will be a flag or config file
> option to ptp4l, and a flag to phc2sys. Any thoughts or objections, before
> I start?
>
> The reason: we have a system "A" with a high jitter clock that knows TAI,
> and systems "B" and "C" with very stable clocks, that need to be very well
> synchronized but that don't know TAI. We want to deliver TAI from A to B,
> then slave C to B, like this:
> * A runs ptp4l, domain 0, priority 128
> * B runs ptp4l, domain 0, priority 200 (A slaved to B to get TAI to B).
> * B runs an extra ptp4l instance, domain 1, priority 128 (grand master
> for domain 1).
> * C runs ptp4l, domain 1, priority 200.
> Running two instances of ptp4l on "B" is the only way I've found to have
> two different domains on the same machine, as domainNumber is not a port
> option. However since the uds_path is fixed, the instance that phc2sys
> communicates with depends on which starts last. Hence my proposal.
>
> Alternatively, if you tell me that I'm "doing it wrong" I can also live
> with that :)
>
> Regards,
>
> Russ.
>
>
------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
