We've updated from 3.0.24 to 3.0.25 and we've noticed some minor problems such as some clients had to reboot in order to mount the share. And the log is now showing this warning all the time: WARNING: Winbindd not running, mapping ids with legacy code [2007/05/17 08:57:37, 2] passdb/lookup_sid.c:sid_to_gid(1435) We are thinking to revert to the previous version 3.0.24 which works correctly. What could be happening? Thanks Emilio C.
On Thu, May 17, 2007 at 09:04:47AM +0200, Emilio Casbas wrote:> We've updated from 3.0.24 to 3.0.25 and we've noticed some minor > problems such as some clients had to reboot in order to mount the share.That's due to the msdfs root = no parameter change. It was listed in the release notes.> And the log is now showing this warning all the time: > WARNING: Winbindd not running, mapping ids with legacy code > [2007/05/17 08:57:37, 2] passdb/lookup_sid.c:sid_to_gid(1435) > > We are thinking to revert to the previous version 3.0.24 which works > correctly.What specificly is not working, or is it just this debug message that is concerning you ? Jeremy.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Emilio Casbas wrote:> We've updated from 3.0.24 to 3.0.25 and we've noticed some minor > problems such as some clients had to reboot in order to mount the share. > And the log is now showing this warning all the time: > > WARNING: Winbindd not running, mapping ids with legacy code > [2007/05/17 08:57:37, 2] passdb/lookup_sid.c:sid_to_gid(1435)I'll raise these to a level 8 rather than level 2 msg and reword it to be less alarming. They may be complete normal in some environments. jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGTLDsIR7qMdg1EfYRAifvAKCBkKrdxPLKVea5np48FANU0a/bJQCghZ5i aBNikyHKpJx5L4YhZWyPaDc=YAH7 -----END PGP SIGNATURE-----