IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
This environment uses pdb_samba4 and auth_samba4 to plug these
critical subsystems into a mixed Samba3/Samba4 DC, in a similar way to
the 'Franky' proposal.
Andrew Barltett
This checks that Samba3 joins Samba4 correctly, and allows NTLM and
Kerberos logons from a live Samba4 DC.
This needs the common krb5.conf generation logic, and because we now
override KRB5_CONFIG we must update ktest to have a valid krb5.conf.
Based on an original patch by metze
Andrew Bartlett
This helps ensure that we don't have the Samba3 servers stop before
the full make test is finished.
Andrew Bartlett
Autobuild-User: Andrew Bartlett <abartlet@samba.org>
Autobuild-Date: Tue Apr 19 09:03:07 CEST 2011 on sn-devel-104
This reduces some of the clutter when we have quite so many server
configurations starting.
The one case that actually needs an alias (dc environment for the
test_nmblookup.sh test) will still keep it.
Andrew Bartlett
This will allow a mapping to be made between things like smbtorture4
-> smbtorture that is correct for the different build environments.
Andrew Bartlett
The "rpc_proxy" should behave like "member", just with a different
configuration.
metze
Autobuild-User: Stefan Metzmacher <metze@samba.org>
Autobuild-Date: Thu Apr 7 15:52:25 CEST 2011 on sn-devel-104
the correct setup directory is known at both build time and install
time using dyn_SETUPDIR, so we no longer have any need to override it
Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
this fixes the path assumptions in Samba4 make test to allow it to
work from the top level directory.
Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
this can be used to start a test envioronment in screen windows.
Use:
make testenv SCREEN=1 SELFTEST_TESTENV=dc
to launch just one environment (in this case, "dc")
During 'net vampire', vampired DC adds information in its own
database, se we need to force replicate vampired_dc to the
first DC to be sure everything is in sync prior starting tests