Hi,
so I did a dumb thing - I am trying to get better about it, but I'm fairly upgrade-happy and I'm bad about taking snapshots.
You'd think having both ZFS AND ESXi for my 3 FreeBSD VMs I would stop 5 seconds to take a snapshot before upgrading.
But no, I powered right ahead, added the latest repo to a file in /etc/pkg and ran pkg upgrade -r latest without a further thought.
Then, temperamental things like Samba began acting weird, which I need for domain membership so I can access the files on these file servers. ldb database mismatches were present across all 3 VMs and one is having clock skew issues with kinit even after running down every last form of time configuration on hardware, ESXi host, ntp, date, tzsetup and domain controllers.
So what's up with the latest repository? Is it basically like the -CURRENT branch where we should expect it to be buggy and cause problems? Samba48 sure doesn't like it much.
so I did a dumb thing - I am trying to get better about it, but I'm fairly upgrade-happy and I'm bad about taking snapshots.
You'd think having both ZFS AND ESXi for my 3 FreeBSD VMs I would stop 5 seconds to take a snapshot before upgrading.
But no, I powered right ahead, added the latest repo to a file in /etc/pkg and ran pkg upgrade -r latest without a further thought.
Then, temperamental things like Samba began acting weird, which I need for domain membership so I can access the files on these file servers. ldb database mismatches were present across all 3 VMs and one is having clock skew issues with kinit even after running down every last form of time configuration on hardware, ESXi host, ntp, date, tzsetup and domain controllers.
So what's up with the latest repository? Is it basically like the -CURRENT branch where we should expect it to be buggy and cause problems? Samba48 sure doesn't like it much.