PATCH samba cache and read-ahead

Jelmer Vernooij jelmer at
Fri Jan 11 15:00:39 GMT 2008

Hi Amin,

Am Donnerstag, den 10.01.2008, 17:08 +0000 schrieb Amin Azez:
> * Volker Lendecke wrote, On 04/01/08 13:38:
> > On Fri, Jan 04, 2008 at 01:21:33PM +0000, Amin Azez wrote:
> >   
> >>> Yes, it's exactly that. Your advantage is that you don't
> >>> need to marshall anything on your own, and you don't have to
> >>> ask anybody for name space. Just invent a named pipe name,
> >>> run uuidgen and you're done with your local sandbox. In
> >>> theory you could even ride on one of the existing named
> >>> pipes, but this might be sub-obtimal.
> >>>   
> >>>       
> >> This sounds brillig. Do you have any URLs handy with practical tips, or
> >> any names of suitable existing named pipes for which I can examine the
> >> related source for tips?
> > Not really, sorry. You might look at the rpc-echo pipe and
> > its implementation.
> >   
> I bit the bullet and decided to do rpc. I cloned the rpcecho (OK. I
> think), and I attach a patch of changes apart from proxy.idl and
> rpc_proxy.c (which are just sed s/echo/proxy/ on the original)
> Volker, please could you check the changes in this patch to see if they
> make sense and are all required?
The changes make sense in the patch make sense. Btw, you seem to've
missed one instance of "dcerpc_rpcecho" during search-n-replace.

> The change to rpc_server/ made sense (and it almost looks as if
> a machine could have done it for me) but librpc/ seems a bit
> long winded in comparison, with subsystems RPC_NDR_PROXY and NDR_PROXY
> and RPC_EJS_PROXY not to mention being a dependency of NDR_TABLE. So I'm
> not sure if I needed them all....
NDR_PROXY takes care of the packing/unpacking of the structures and
functions in your IDL file. RPC_NDR_PROXY contains the functions for
making remote requests (RPC_NDR_PROXY uses NDR_PROXY internally). 

NDR_TABLE is used by the "ndrdump" debugging utility.

RPC_EJS_PROXY is for the JavaScript bindings of your RPC interface.

> Finally, is there any tool to derive one of proxy.idl and rpc_proxy.c
> from the other, or keep them in sync (apart from weave, I suppose :-) ),
> or do I do that by hand?
You can use pidl to generate a template for rpc_proxy.c:

$ ./pidl/pidl --template -- librpc/idl/proxy.idl >



Jelmer Vernooij <jelmer at> -
Jabber: jelmer at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url :

More information about the samba-technical mailing list