anchor.diff:    profile: <2>
     - name: "profile1" <3>
       interface: "" <4>
  -    ptp4lOpts: "-s -2" <5>
  +    ptp4lOpts: "-2" <5>
       ptp4lConf: | <6>
         [ens1f0] <7>
         masterOnly 0
  
positive.code: <2> Specify an array of one or more `profile` objects.
  <3> Specify the name of a profile object which uniquely identifies a profile object.
  <4> This field should remain empty for boundary clock.
  <5> Specify system config options for the `ptp4l` service, for example `-s -2`. The options should not include the network interface name `-i <interface>` and service config file `-f /etc/ptp4l.conf` because the network interface name and the service config file are automatically appended.
  <6> Specify the needed configuration to start `ptp4l` as boundary clock. For example, `ens1f0` synchronizes from a grandmaster clock and `ens1f3` synchronizes connected devices.
  <7> The interface name to synchronize from.
  <8> The interface to synchronize devices connected to the interface.
  
negative.code: I1115 09:41:17.117607 4143292 daemon.go:110] ------------------------------------
  I1115 09:41:17.117612 4143292 daemon.go:102] Profile Name: profile1
  I1115 09:41:17.117616 4143292 daemon.go:102] Interface:
  I1115 09:41:17.117620 4143292 daemon.go:102] Ptp4lOpts: -2
  I1115 09:41:17.117623 4143292 daemon.go:102] Phc2sysOpts: -a -r
  I1115 09:41:17.117626 4143292 daemon.go:116] ------------------------------------
  ----
  