Samba and Application Response Measurement (ARM 4.0)

Sven Kubiak sk at
Mon Mar 17 17:02:59 GMT 2008

Okay, focusing on the calls makes much more sense, than looking for all
functions in the source code which are responsible for a specific samba

To find the right calls we'd like to measure using a sniffer is the less
difficult part. What is more difficult is the right place to start with.
I guess i was wrong looking at source/profile/profile.c which seems to be
responsible (among other things) for handling the user profile. I found the
vfs_* modules in source/modules which i will look into asap, but i didn't
found the "PROFILE stuff" Volker mentioned.

Best regards

Am 16.03.08 18:40 schrieb "Volker Lendecke" unter
<Volker.Lendecke at SerNet.DE>:

> On Sun, Mar 16, 2008 at 03:20:56PM +0100, Sven Kubiak wrote:
>> Well, i found the profile.c, profiles.c and status_profile.c. But i don't
>> know if these are the right files to begin with.
>> As with the callers of (sys_)read, could you name the files to start with.
>> It's difficult to figure out how and where calls are made.
> The theory is that these calls are made upon entry and exit
> of an SMB request. It's not to made to monitor posix-level
> syscalls. To monitor those it would probably be best to
> create a VFS module that wraps all calls, similar to
> vfs_full_audit.
> Volker

More information about the samba-technical mailing list