[Samba] classicupgrade migration issues
abartlet at samba.org
Fri Mar 18 20:04:59 UTC 2016
On Fri, 2016-03-18 at 15:48 -0400, Sonic wrote:
> On Fri, Mar 18, 2016 at 2:39 PM, Andrew Bartlett <abartlet at samba.org>
> > Exactly. Think about it a little - how can it determine the group
> > membership, if the users/groups do not exist locally on the host
> > doing
> > the migration?
> To clarify then:
> Do I need both the users and groups on the new host as they are on
> old host, or just the groups? Is there any constraint that the GID's
> and or UID's need to be the same on the new host?
> Once the migration is done can I then remove the added 'nix groups
> and/or users with no ill effects?
The upgrade code assumes you run on the same host. I realise now that
folks doing an upgrade use that an an opportunity to upgrade hardware,
and keep old systems as fallbacks, so the assumptions cause trouble.
Make the new host identical in terms of the data needed to upgrade
(users/groups/samba databases) upgrade and then remove the posix
users/groups and use nss_winbind instead.
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
More information about the samba