samba - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2007-10-10	r2022: Add net_copy_fileattr as a separate function to copy just ACLs, attrs	Günther Deschner	1	-101/+198
	and timestamps. This makes net_copy_file less complex. Guenther (This used to be commit 43af9e67dd7c0328f214def4b591041e9b69614a)
2007-10-10	r1966: further work on and cleanup of the net-migration-tool.	Günther Deschner	1	-31/+72
	It's now possible to migrate files preserving dos-attributes and correct timestamps. Also added some small docu- and syntax-fixes. Guenther (This used to be commit 0e990582a0416933a8671ca660d22e980f828402)
2007-10-10	r1698: fix build.	Günther Deschner	1	-2/+3
	guenther (This used to be commit 925e28d0cbd9667bceb0762ef1e429735250c209)
2007-10-10	r1692: first commit :)	Günther Deschner	1	-0/+2185
	* add IA64 to the architecture table of printer-drivers * add new "net"-subcommands: net rpc printer migrate {drivers\|printers\|forms\|security\|settings\|all} [printer] net rpc share migrate {shares\|files\|all} [share] this is the first part of the migration suite. this will will (once feature-complete) allow to do 1:1 server-cloning in the best possible way by making heavy use of samba's rpc_client-functions. all migration-steps are implemented as rpc/smb-client-calls; net communicates via rpc/smb with two servers at the same time (a remote, source server and a destination server that currently defaults to the local smbd). this allows e. g. printer-driver migration including driverfiles, recursive mirroring of file-shares including file-acls, etc. almost any migration step can be called with a migrate-subcommand to provide more flexibility during a migration process (at the cost of quite some redundancy :) ). "net rpc printer migrate settings" is still in a bad condition (many open questions that hopefully can be adressed soon). "net rpc share migrate security" as an isolated call to just migrate share-ACLs will be added later. Before playing with it, make sure to use a test-server. Migration is a serious business and this tool-set can perfectly overwrite your existing file/print-shares. * along with the migration functions had to make I the following changes: - implement setprinter level 3 client-side - implement net_add_share level 502 client-side - allow security descriptor to be set in setprinterdata level 2 serverside guenther (This used to be commit 8f1716a29b7e85baf738bc14df7dabf03762f723)