On 12/8/2014 10:05 AM, Kevin Lemonnier wrote: > Hi, > > I installed an OpenAfs server on a virtual machine to check a few things, > hoping it'd meet the requirements we have. > The performances are looking good but I can't get an audit log with the > full path of the created / modified files.
You cannot because the file server doesn't the paths as seen by the
clients. The file server responds to requests against FileIDs
{Volume, Vnode, Unique}
In the case of directory operations you get the FID of directory and the
name of the entry.
If your goal is to perform an operation on a particular object, that is
all of the information you need to access it.
> What we do currently is using inotify to perform tasks on created /
> modified files, and I was told that it obviously wouldn't work with
> OpenAFS, but that it was possible to get with the audit log an equivalent.
It will not work with OpenAFS on Linux because of GPL conflicts.
> Is there some way to achieve that ? Some configuration option I missed
> that would allow me to have the full path in the audit log,
The full path is a construct of combining volumes via mount points. Not
all volumes are on one server so even if you wanted to do the work to
construct the paths on each RPC you couldn't.
> or some way
> to get inotify working on the server?
The server doesn't store objects in the same name space viewed by the
clients. AFS is not NFS3 or CIFS.
> I don't need inotify on the
> clients, what I want is some way to get notified when the clients create
> or modify a file on the afs without having to check thousands of files
> at all times like grunt does.
The feature you want is "server side callouts" which is not a feature
that OpenAFS has.
> Sorry if my english is bad.
Your English is good.
> ---
> Kevin Lemonnier
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
