You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
MSVSphere Packaging Team
89d44735de
|
3 months ago | |
---|---|---|
.. | ||
README.downgrade | 2 years ago | |
pam_winbind.conf | 2 years ago | |
redhat-4.20.2.patch | 3 months ago | |
samba-4.20.2.tar.asc | 3 months ago | |
samba-systemd-sysusers.conf | 2 years ago | |
samba-usershares-systemd-sysusers.conf | 2 years ago | |
samba-winbind-systemd-sysusers.conf | 9 months ago | |
samba.abignore | 2 years ago | |
samba.logrotate | 2 years ago | |
samba.pamd | 2 years ago | |
smb.conf.example | 2 years ago | |
smb.conf.vendor | 2 years ago | |
usershares.conf.vendor | 2 years ago |
README.downgrade
Downgrading Samba ================= Short version: data-preserving downgrades between Samba versions are not supported Long version: With Samba development there are cases when on-disk database format evolves. In general, Samba Team attempts to maintain forward compatibility and automatically upgrade databases during runtime when requires. However, when downgrade is required Samba will not perform downgrade to existing databases. It may be impossible if new features that caused database upgrade are in use. Thus, one needs to consider a downgrade procedure before actually downgrading Samba setup. Please always perform back up prior both upgrading and downgrading across major version changes. Restoring database files is easiest and simplest way to get to previously working setup. Easiest way to downgrade is to remove all created databases and start from scratch. This means losing all authentication and domain relationship data, as well as user databases (in case of tdb storage), printers, registry settings, and winbindd caches. Remove databases in following locations: /var/lib/samba/*.tdb /var/lib/samba/private/*.tdb In particular, registry settings are known to prevent running downgraded versions (Samba 4 to Samba 3) as registry format has changed between Samba 3 and Samba 4.