Am Dienstag, 10. Januar 2012 schrieb Trond Myklebust: > On Tue, 2012-01-10 at 01:49 +0100, Wolfgang Walter wrote: > > On Monday 09 January 2012, Trond Myklebust wrote: > > > On Mon, 2012-01-09 at 14:28 -0800, Myklebust, Trond wrote: > > > > > -----Original Message----- > > > > > > > > Please read the changelog and documentation: > > > > > > > > If your server doesn’t support numeric uids/gids, then you will see > > > > _no_ change in behaviour. > > > > Hmm, what does that mean exactly? Does a linux nfs4-server support > > numeric uids/gids? If yes, by default or do I need do set an option? > > The patch requires no changes to a configuration that is already > working. That's the whole point I've been trying to get across. So if user foo has uid 500 on the server and uid 600 on the client that will still work with AUTH_SYS: client: uid 500 => foo@REALM server: foo@REALM => uid 600 and vice-versa? > > I always thought that the idmapper with its translation were exactly for > > that case. If I have a homogenous uid/gid name space why would I want to > > use names and translate anyway? > > For RPCSEC_GSS authentication. That's the only case that the original > RFC3530 cared about. The problems arise when people use AUTH_SYS, and > this protocol change+patch is the solution. Regards, -- Wolfgang Walter Studentenwerk München Anstalt des öffentlichen Rechts Abteilungsleiter IT Leopoldstraße 15 80802 München Tel: +49 89 38196 276 Fax: +49 89 38196 150 Email: wolfgang.walter@xxxxxxx http://www.studentenwerk-muenchen.de/ -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
