On Wed, 2008-02-27 at 23:59 -0800, Andrew Morton wrote: > On Thu, 28 Feb 2008 10:51:08 +0300 Pavel Emelyanov <xemul@xxxxxxxxxx> wrote: > > > > So, why do we need the uid and gid? When someone walks over an autofs > > > dentry that is meant to cause a mount we send a request packet to the > > > daemon via a pipe which includes the process uid and gid, and as part of > > > the lookup we set macros for several mount map substitution variables, > > > derived from the uid and gid of the process requesting the mount and > > > they can be used within autofs maps. > > > > Why do we need the uid then? Is just pid not enough to uniquely > > identify a task? > > The problem is that the userspace daemon is restarted. ie: it exits > and is re-run. It then needs to pick up various state from its previous > run. Dumb old me, I really only need the uid. The gid can come from the get user info functions of glibc. DOH! - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
