From: Goswin v. B. <gos...@we...> - 2008-12-11 17:51:00
|
"Lucas C. Villa Real" <lu...@go...> writes: > On Thu, Dec 11, 2008 at 9:16 AM, hce <web...@gm...> wrote: >> On Wed, Dec 10, 2008 at 2:24 PM, Lucas C. Villa Real >> <lu...@go...> wrote: >>> On Tue, Dec 9, 2008 at 8:50 AM, hce <web...@gm...> wrote: >>>> Hi, >>>> >>>> Is there any user information provided by fuse API? I've been thinking >>>> to work on a user privided component to reserve the file descriptor >>>> for reading and writing until a user leave the fuse client connection >>>> or session. >>> >>> Hi, Sean, >>> >>> You can get that information from fuse_get_context()->{uid,gid}. >> >> Thanks Lucas. That works. But if I connect to fuse session from my two >> different terminals which contain the same uid and gid in linux >> machine. The fuse_get_context uid and gid won't be able to tell me >> which requests from. The pid seems varied for every request. Is it >> possible in fuse interface and APIs to get a unique user session >> information to identify all requests from the same user connection >> until the user leaves the session? Can the fuse_session_ops be used >> for that purpose? If so, could you please give an example how to get >> fuse_session information? > > There's no extended process/user information in fuse or fuse_lowlevel. > However, given the PID, you might be able to extract some useful data > from /proc/<pid>, although I don't recall those directories having > information such as ttyname or unique session ids. > > Lucas In fuse_file_info there is /** Lock owner id. Available in locking operations and flush */ uint64_t lock_owner; But as it says only for locking and flush. Maybe you should describe what you actualy want to do instead of asking for what you think you need to do it. Maybe you are just on the wrong track for your idea or maybe fuse just isn't ment for it. Because, at least to me, what you are asking for doesn't seem to make much sense in the context of what fuse does. No offense. Could be just me. MfG Goswin |