search for: vdc4

Hi, I have a new Centos 7.6 VM that I self compiled 4.10.3 and joined it to an existing samba AD domain that has 2 existing DCs. One of the existing DCs is running 4.8.7 and the other is running 4.7.7. Everything looks OK except that when I run samba-tool drs showrepl on the new DC (VDC4) I get the following output: (vdc4 pts4) # samba-tool drs showrepl Default-First-Site-Name\VDC4 DSA Options: 0x00000001 DSA object GUID: a57c74ed-3343-4497-965d-e7e50a1f84ae DSA invocationId: 1f0384bb-1f0b-4d8f-a498-d7b02ae53930 ==== INBOUND NEIGHBORS ==== CN=Configuration,DC=kmg,DC=mydomain,DC=...

...I self compiled 4.10.3 and joined it to an >>>> existing samba AD domain that has 2 existing DCs. One of the existing DCs is >>>> running 4.8.7 and the other is running 4.7.7. Everything looks OK except >>>> that when I run samba-tool drs showrepl on the new DC (VDC4) I get the >>>> following output: >>> >>> "self-compiled" can include a lot of sins, especially if trying to >>> place it alongside *or* in place of the provided libraries for tevent, >>> ldb, tdb, and talloc. Let me point you to my git repo...

...a new Centos 7.6 VM that I self compiled 4.10.3 and joined it to an >> existing samba AD domain that has 2 existing DCs. One of the existing DCs is >> running 4.8.7 and the other is running 4.7.7. Everything looks OK except >> that when I run samba-tool drs showrepl on the new DC (VDC4) I get the >> following output: > > "self-compiled" can include a lot of sins, especially if trying to > place it alongside *or* in place of the provided libraries for tevent, > ldb, tdb, and talloc. Let me point you to my git repo, Well OK maybe I should have said self...

...> I have a new Centos 7.6 VM that I self compiled 4.10.3 and joined it to an > existing samba AD domain that has 2 existing DCs. One of the existing DCs is > running 4.8.7 and the other is running 4.7.7. Everything looks OK except > that when I run samba-tool drs showrepl on the new DC (VDC4) I get the > following output: "self-compiled" can include a lot of sins, especially if trying to place it alongside *or* in place of the provided libraries for tevent, ldb, tdb, and talloc. Let me point you to my git repo, https:/github.com/nkadel/samba4repo/, with submodules for sam...

...>> existing samba AD domain that has 2 existing DCs. One of the >>>>> existing DCs is >>>>> running 4.8.7 and the other is running 4.7.7. Everything looks OK >>>>> except >>>>> that when I run samba-tool drs showrepl on the new DC (VDC4) I get >>>>> the >>>>> following output: >>>> >>>> "self-compiled" can include a lot of sins, especially if trying to >>>> place it alongside *or* in place of the provided libraries for tevent, >>>> ldb, tdb, a...

...6 VM that I self compiled 4.10.3 and joined it to an > >> existing samba AD domain that has 2 existing DCs. One of the existing DCs is > >> running 4.8.7 and the other is running 4.7.7. Everything looks OK except > >> that when I run samba-tool drs showrepl on the new DC (VDC4) I get the > >> following output: > > > > "self-compiled" can include a lot of sins, especially if trying to > > place it alongside *or* in place of the provided libraries for tevent, > > ldb, tdb, and talloc. Let me point you to my git repo, > > Wel...

[Cross-posting to ldoms-discuss] We are occasionally seeing massive time-to-completions for I/O requests on ZFS file systems on a Sun T5220 attached to a Sun StorageTek 2540 and a Sun J4200, and using a SSD drive as a ZIL device. Primary access to this system is via NFS, and with NFS COMMITs blocking until the request has been sent to disk, performance has been deplorable. The NFS server is a