Re: [fuse-devel] fuse_entry_param

[Nikolaus R. <Nik...@ra...>]

Hi,

Is there really no one able to answer this (and my other mail about the
arguments to fuse_mount and fuse_lowlevel_new) at the moment? I'm sure
there are some other people here who use the low-level API... or are
they all on their (deserved) holidays? *g*

Best,
Nikolaus


Nikolaus Rath <Nik...@ra...> writes:
> Hello,
>
> I have some questions about the fuse_entry_param structure:
>
> How do I have to use the "generation" attribute? The documentation in
> fuse_lowlevel.h says that "The ino/generation pair should be unique for
> the filesystem's lifetime". But what exactly does unique mean here? If I
> have a file with inode 2, and then delete that file and later I create a
> new file that occupies the same inode, do I have to increase the
> generation?
>
>
> Entries and attributes in my file systems are only changed in response
> to requests from the FUSE kernel module. Does that mean that I can
> effectively set attr_timeout and entry_timeout to infinity? If not, what
> value should I use?
>
>
> Thanks!
>
>    -Nikolaus


   -Nikolaus

-- 
 »Time flies like an arrow, fruit flies like a Banana.«

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C