diff options
| author | Amitay Isaacs <amitay@gmail.com> | 2011-08-25 17:20:05 +1000 |
|---|---|---|
| committer | Andrew Bartlett <abartlet@samba.org> | 2011-08-26 10:06:33 +1000 |
| commit | d8465f2a918deb9fb94f4dc5ad85bc07c073bd05 (patch) | |
| tree | 0a13ff027cf22607c0a3e3b2d672455a9a2fdd5b /WHATSNEW.txt | |
| parent | d2536b31200106ad0bbea60abd3e654c23540e6d (diff) | |
| download | samba-d8465f2a918deb9fb94f4dc5ad85bc07c073bd05.tar.gz samba-d8465f2a918deb9fb94f4dc5ad85bc07c073bd05.tar.bz2 samba-d8465f2a918deb9fb94f4dc5ad85bc07c073bd05.zip | |
s3_upgrade: Update commandline options and use updated samba3 python module
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>
Diffstat (limited to 'WHATSNEW.txt')
0 files changed, 0 insertions, 0 deletions