search for: 05t13

...ed the archives and it looks like a common mistake is inconsistent usage of the trailing backslash. My usage looks something like: % rsync -aP --delete --delete-excluded --exclude-from=/home/Nancy/.rsync/exclude --link-dest=/cygdrive/f/macki/current/ Nancy /cygdrive/f/macki/incomplete-back-2012-06-05T13:53:51 I'm running this from "/cygwin/c/Documents and Settings/" directory, and the directory under the symlink "current" is "Nancy". Is there a way to tell if rsync thinks it's found a match and attempting to link? Thanks, -Clint

...> mail.hprs.local.ntp: NTPv3, Client, length 68 Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 7 (128s), precision -23 Root Delay: 0.000000, Root dispersion: 1.000000, Reference-ID: (unspec) Reference Timestamp: 3916127270.315146199 (2024-02-05T13:07:50Z) Originator Timestamp: 0.000000000 Receive Timestamp: 0.000000000 Transmit Timestamp: 3916480949.611151499 (2024-02-09T15:22:29Z) Originator - Receive Timestamp: 0.000000000 Originator - Transmit Timestamp: 3916480949.611151499 (202...

...cal.ntp: NTPv3, Client, length 68 > Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 7 (128s), precision -23 > Root Delay: 0.000000, Root dispersion: 1.000000, Reference-ID: (unspec) > Reference Timestamp: 3916127270.315146199 (2024-02-05T13:07:50Z) > Originator Timestamp: 0.000000000 > Receive Timestamp: 0.000000000 > Transmit Timestamp: 3916480949.611151499 (2024-02-09T15:22:29Z) > Originator - Receive Timestamp: 0.000000000 > Originator - Transmit Timest...

Are your clients talking to the DCs re. Time at all ? This is an example in one of my DCs: Run tcpdump on your DC: root at dwing:~# tcpdump??port 123 -v tcpdump: listening on enp1s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes 10:20:41.655081 IP (tos 0x0, ttl 128, id 32113, offset 0, flags [none], proto UDP (17), length 96) ?? ?192.168.3.52.ntp > dwing.mad.mater.int.ntp: NTPv3,