| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
large commit. I thought this was worthwhile to get done for
consistency.
(This used to be commit ec32b22ed5ec224f6324f5e069d15e92e38e15c0)
|
|
metze
(This used to be commit 18bbe40fe1e400546ff3750213f6c0505895e357)
|
|
W_ERROR_HAVE_NO_MEMORY() macro
- add parameters for
server_info:platform_id = 500 /* this is PLATFORM_ID_NT */
server_info:version_major = 5
server_info:version_minor = 2
- implmented srvsvc_NetSrvGetInfo level 101
- make dcesrv_common_get_server_name() match w2k3
metze
(This used to be commit 16f43207704397c6e3c0132e9f17c8a1a846ddca)
|
|
(This used to be commit 729e0026e4408f74f140375537d4fe48c1fc3242)
|
|
The thing that finally convinced me that minimal includes was worth
pursuing for rpc was a compiler (tcc) that failed to build Samba due
to reaching internal limits of the size of include files. Also the
fact that includes.h.gch was 16MB, which really seems excessive. This
patch brings it back to 12M, which is still too large, but
better. Note that this patch speeds up compile times for both the pch
and non-pch case.
This change also includes the addition iof a "depends()" option in our
IDL files, allowing you to specify that one IDL file depends on
another. This capability was needed for the auto-includes generation.
(This used to be commit b8f5fa8ac8e8725f3d321004f0aedf4246fc6b49)
|
|
functions we don't implement yet so that we don't put uninitialised
result data on the wire (found with valgrind)
(This used to be commit abe90bc7ba8d38d1f7c641494463236b0fd3f41f)
|
|
servers. Previously the server pipe code needed to return the RPC
level status (nearly always "OK") and separately set the function call
return using r->out.result. All the programmers writing servers
(metze, jelmer and me) were often getting this wrong, by doing things
like "return NT_STATUS_NO_MEMORY" which was really quite meaningless
as there is no code like that at the dcerpc level.
I have now modified pidl to generate the necessary boilerplate so that
just returning the status you want from the function will work. So for
a NTSTATUS function you return NT_STATUS_XXX and from a WERROR
function you return WERR_XXX. If you really want to generate a DCERPC
level fault rather than just a return value in your function then you
should use the DCESRV_FAULT() macro which will correctly generate a
fault for you.
As a side effect, this also adds automatic type checking of all of our
server side rpc functions, which was impossible with the old API. When
I changed the API I found and fixed quite a few functions with the
wrong type information, so this is definately useful.
I have also changed the server side template generation to generate a
DCERPC "operation range error" by default when you have not yet filled
in a server side function. This allows us to correctly implement
functions in any order in our rpc pipe servers and give the client the
right information about the fault.
(This used to be commit a4df5c7cf88891a78d82c8d6d7f058d8485e73f0)
|
|
add some more WERR_NOT_SUPPORTED stubs to pass our torture tests
(wkssvc and srvsvc)
metze
(This used to be commit f8605b39ab58f8db22358122eafccc8a1cc60004)
|
|
and return WERR_ACCESS_DENIED for level 102, 502 so does my winXP box
for a non-admin user
metze
(This used to be commit 975bf13f17e0bd95ec37af3534e5209c1de99252)
|
|
- we know can browse the server via the Windows Explorer
- some little fixes to the winreg server pipe
metze
(This used to be commit 6f213a3494d3b5ab629944394b20a84075a04438)
|
