search for: tombstoned

On a particular DC, running 'samba-tool dbcheck' produces the following:     NOTICE: found 2 expired tombstones, 'samba' will remove them daily, 'samba-tool domain tombstones expunge' would do that immediately. When I run 'samba-tool domain tombstones expunge' the following is produced:     Removed 0 objects and 0 links successfully Running 'samba-tool

>> Did you think to run 'samba-tool domain tombstones expunge --help' ? No, I didn't, I just assumed that the message "'samba' will remove them daily, 'samba-tool domain tombstones expunge' would do that immediately" would mean exactly that :-). It worked now. Thank you!

On Mon, 8 Apr 2019 22:32:04 +0100 miguel medalha via samba <samba at lists.samba.org> wrote: > On a particular DC, running 'samba-tool dbcheck' produces the > following: > >     NOTICE: found 2 expired tombstones, 'samba' will remove them > daily, 'samba-tool domain tombstones expunge' would do that > immediately. > > When I run

...verse zone (PTR records) We have one zone for VPN clients 8.0.10.in-addr.arpa. I activated the feature in the smb.conf as well as in the Windows DNS manager. Entries are deleted (not visible in DNS manager) after a while. You can still see them in ADSI-Edit. Those that are invisible have "dNSTombstoned: TRUE" set the others have either FALSE or the attribute is not there at all. My problem is this if an entry was deleted and has "dNSTombstoned: TRUE" it still has the same owner and therefore a new computer that got the same IP from our VPN gateway can not set this entry to point t...

Hey all, has anyone done dcdiag against his DC yet? It's made from a windows client on command line: dcdiag /s:<servername> What are your results? With me some of the tests were not successful, e.g. ForestDNSDomain. My dcdiag is German so its output would not be so helpful for the mailing list. So somebody else can do a check to compare? Thanks in advance Tim

Hello, I receive the following when I attempt to expunge deleted tombstone records. I'm attempting to fix several dbcheck 'Not removing dangling forward link' errors. samba-tool domain tombstones expunge ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 'module' object has no attribute 'time' File

Hai, ? After some "strange" pc problems with pc-domain trust i did some digging. Im pretty sure this is a samba bug, if someone can verify this. ? My steps. ? - Setup a win10 pc, static ip. - Join the domain. ? And its shown in AD and DNS. Turn of the pc. ? but, now next, set a new pc, use the same name but a different IP. join the domain. login and turn the pc offf ? Back to

>On Mon, Jul 20, 2020 at 10:32 AM Alexey Lapshin ><alapshin at accesssoftek.com> wrote: >> >> >On Fri, Jul 17, 2020 at 1:55 PM Alexey Lapshin <a.v.lapshin at mail.ru> wrote: >> >> >> >> >Пятница, 17 июля 2020, 19:42 +03:00 от David Blaikie <dblaikie at gmail.com>: >> >> > >> >> >On Fri, Jul 17, 2020 at

Hi All, In general I think we should adopt Dave's plan here. The number of consumers that can (and have) been caught off guard by this change is just too high. At the very least I think we should move this to opt in to the new tombstoning behavior by default and at most migrate to bfd's behavior for both the current release and in the current tree. If we want to make this sort of change

On 10/26/2016 12:11 PM, Rowland Penny via samba wrote: > On Wed, 26 Oct 2016 11:41:23 -0400 > lingpanda101 via samba <samba at lists.samba.org> wrote: > >> Hello, >> >> I receive the following when I attempt to expunge deleted tombstone >> records. I'm attempting to fix several dbcheck 'Not removing dangling >> forward link' errors. >>

Dear list, Does anybody know how to lower the tombstone lifetime in samba 4.5 or later? There used to be a wiki entry, but this has been deleted as it is probably not adequate anymore: https://wiki.samba.org/index.php/Restoring_deleted_AD_objects#Changing_the_defaults_for_msDS-deletedObjectLifetime_and_tombstoneLifetime I used to change the attribute tombstoneLifetime in CN=Directory

On 2020-07-24, Hans Wennborg via llvm-dev wrote: >Sounds good to me from a release perspective. I think we need more input from the triage of https://chromium-review.googlesource.com/c/chromium/src/+/2291352 whether it is just .debug_line or .debug_* >On Fri, Jul 24, 2020 at 7:53 AM Eric Christopher via llvm-dev ><llvm-dev at lists.llvm.org> wrote: >> >> Hi All,

>On Fri, Jul 17, 2020 at 1:55 PM Alexey Lapshin <a.v.lapshin at mail.ru> wrote: >> >> >Пятница, 17 июля 2020, 19:42 +03:00 от David Blaikie <dblaikie at gmail.com>: >> > >> >On Fri, Jul 17, 2020 at 12:03 AM Fangrui Song <maskray at google.com> wrote: >> >> >> >> Thanks for the write-up! >> >> >>

>From my understanding the breakpad bug was also only related to .debug_line and has been fixed by https://chromium-review.googlesource.com/c/breakpad/breakpad/+/2317730 > a) .debug_ranges&.debug_loc => -2, .debug_line => 0, other .debug_* -> -1 > b) .debug_ranges&.debug_loc => -2, other .debug_* => 0 I am still of the opinion that we should just do a), not b).

hi, I have this DC in aws to fulfill the authentication need of our moodle. # samba -V Version 4.17.7-Debian DNS with SAMBA_INTERNAL The replication of the users and groups happens correctly. Some errors in running samba_dnsupdate, but it is ok anyway. When I ran the command samba-tool dbcheck, I got the return below. # samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix --yes

This is almost certainly because of a build artifact. python/samba/netcmd/time.py was renamed to nettime.py but there is likely to be a time.pyc file floating around in your directories. The reason it was renamed was so that the samba tool time command wasn't confused with the python time module, but this necessarily causes issues with existing installs unfortunately. The fix is mostly

> I still think that we do bfd locs with a decent option to change for at least the current release and sources and then, once we're a little more certain we have everything that might want to parse dwarf (say by working with dwarf-discuss), we can change the default. Given what’s been found, I think Eric/Dave are correct, use bfd behavior by default with an option to do the new thing.

>Пятница, 17 июля 2020, 19:42 +03:00 от David Blaikie <dblaikie at gmail.com>: > >On Fri, Jul 17, 2020 at 12:03 AM Fangrui Song < maskray at google.com > wrote: >> >> Thanks for the write-up! >> >> On 2020-07-16, David Blaikie wrote: >> >In short: Perhaps we should switch lld to the bfd-style tombstoning >> >behavior for a release or

On Wed, 26 Oct 2016 11:41:23 -0400 lingpanda101 via samba <samba at lists.samba.org> wrote: > Hello, > > I receive the following when I attempt to expunge deleted tombstone > records. I'm attempting to fix several dbcheck 'Not removing dangling > forward link' errors. > > samba-tool domain tombstones expunge > ERROR(<type

On Wed, 26 Oct 2016 12:47:16 -0400 lingpanda101 via samba <samba at lists.samba.org> wrote: > On 10/26/2016 12:11 PM, Rowland Penny via samba wrote: > > On Wed, 26 Oct 2016 11:41:23 -0400 > > lingpanda101 via samba <samba at lists.samba.org> wrote: > > > >> Hello, > >> > >> I receive the following when I attempt to expunge deleted