summaryrefslogtreecommitdiff
path: root/source4/setup/upgrade_from_s3
AgeCommit message (Collapse)AuthorFilesLines
2011-09-12s4-s3-upgrade Remove upgrade_from_s3 script, use samba-tool domain samba3upgradeAndrew Bartlett1-132/+0
2011-09-05s4-provision Use ProvisioningError and the eadbAndrew Bartlett1-1/+22
The eadb flag tells us to avoid using system extended attributes, typcially if we are not running as root (ie, in a test environment). The ProvisioningError class allows us to return failures to the upgrade_from_s3 script which can then be detected correctly by the selftest framework. Andrew Bartlett
2011-08-26s3_upgrade: Set lock directory to correct directoryAmitay Isaacs1-1/+2
Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2011-08-26s3_upgrade: Update commandline options and use updated samba3 python moduleAmitay Isaacs1-20/+63
upgrade_from_s3 script now requires samba3 configuration file and target directory for samba4 database. In addition, it either uses --libdir option or --testparm option to correctly guess the paths for samba3 databases (private dir and state directory). Usage: upgrade_from_s3 [options] <configuration_file> <targetdir> Input arguments are: <configuration_file> - path to existing smb.conf <targetdir> - directory in which samba4 database will be created In addition, specify either samba3 database directory (with --libdir) or samba3 testparm utility (with --testparm). Before using passdb interface, initialize s3 loadparm context using correct path settings for private dir and state directory. Export account policy from s3 to s4. Signed-off-by: Andrew Bartlett <abartlet@samba.org>
2011-08-13upgrade: Add missing bits for the s3 to s4 upgrade scriptAmitay Isaacs1-17/+6
Use passdb backend to import/export users Remove unused options for upgrade_from_s3 command (--blank) and credentials options Config file is specified with -s/--configfile option and no need to specify as an argument. Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
2011-08-13s4-scripting Rename passdb upgrade routine to avoid conflict with ↵Andrew Bartlett1-4/+4
upgradeprovision
2011-02-07s4-provision Remove setup_path, setup_dir and find_setup_dirAndrew Bartlett1-9/+1
We now have a reliable way to know the current location of the templates: dyn_SETUPDIR, which is updated for both the in-build and installed binaries. This replaces the function arguments and the distributed resolution of the setup directory with one 'global' function (imported as required). This also removes the ability to specify an alternate setup directory on the command line, as this was rarely if ever used and never tested. Andrew Bartlett
2010-10-01selftest: Let selftest provide the tempdir, rather than creating it as ↵Jelmer Vernooij1-1/+0
sideeffect of tests.py.
2010-06-13upgradeprovision: Use logging infrastructure.Jelmer Vernooij1-7/+11
2010-04-21s4-upgradeprovision: fixed --realm option duplicate in upgrade_from_s3Andrew Tridgell1-1/+0
2010-03-25python: use '#!/usr/bin/env python' to cope with varying install locationsAndrew Tridgell1-1/+1
this should be much more portable
2010-01-25upgrade_from_s3: Remove unused imports.Jelmer Vernooij1-2/+0
2009-11-28s4:upgrade_from_s3 - Move it back to "setup"Matthias Dieter Wallnöfer1-0/+86
Suggested by Jelmer