Age | Commit message (Collapse) | Author | Files | Lines |
|
descriptors in smbd on all build farm machines. I suspect we have a fd
leak somewhere, but its hard to track down.
I know part of the problem is the number of (fake) network interfaces
we define in the build farm tests, with each of them listening on a
whole bunch of different protocol ports. That chews up around 48 file
descriptors just to startup. I don't think thats the real problem
though, and I suspect something else is leaking file descriptors on
some hosts.
(This used to be commit 83bf458ec98d9f2a21b3748802f41abcbcc1e0b2)
|
|
filesystems and the tests are taking more than 1.5 hours. We will
still be testing the sync code paths, as the ldb tests still run
synchronous, but doing all of our other tests synchronously just costs
too much time.
(This used to be commit ce2baf7385e019383ffb292bd30e77c31eecbbef)
|
|
static function
(This used to be commit 024ca6a91cdf2c0f8999c220b4459a72c45bfd32)
|
|
NT_STATUS_ACCESS_DENIED in the access mask checks
(This used to be commit ceffc34f3e9f47a8a44dad52054688f9855eeb37)
|
|
sizeof(BOOL) != sizeof(int)
this broke with the conversion to a real BOOL type
(This used to be commit 75dab73ac603968ce49c605e07d43051dbfa7398)
|
|
(This used to be commit fea75d2c9732f91cb79e178ef6c57c3945e4f52e)
|
|
completes in a minute on my laptop (the benchmark I usually use).
Simo, I removed th ldb tests, as ldb is pretty well tested by lots of
the other tests, and its a pretty slow test. We could instead add a
"ldb-testquick.sh" which does only minimal testing. The full tests
will of course be run with 'make test' and in the build farm.
(This used to be commit 3cee6a7863bba61c92f94087df5c6442f02a2da7)
|
|
when I changed the test output to be easier to read, I also broke it
so that it always gives a zero exit status. Fix now, and unfortunately
I expect to see some more red in the farm as a result :(
(This used to be commit c2fc3471023b613571089cb018638a40091d08ab)
|
|
- don't display the "(NN tests failed so far)" message unless a test
has failed
(This used to be commit da37e963cef065bb1c50543596e352c78e712ddc)
|
|
accidental part of commit in the recent echo.idl changes (in r18565)
(This used to be commit 5e143267d7ae18536f1a1be8966dc5e783ea867e)
|
|
has failed. The output was too subtle for people who aren't used to
it.
(This used to be commit a57decb96aee05d3238b64d50a136c8b8001f811)
|
|
tiny quick test for torture for them
(This used to be commit 64062d16a2cc215af320eb30827887eb2531e3b0)
|
|
when it breaks. It isn't much good as a template for developers to use
unless it works :-)
(This used to be commit 262bee07dcb140b413d5ae5a8a754b3e57235323)
|
|
module to handle euid
(This used to be commit 6784058923ef532da882830296f9bb5f58cddb43)
|
|
When changing a field name in idl, please remember to check for use of
those functions in any js code as well.
(This used to be commit 7005806aa6842ffc3d5ed98682f2aefc59759580)
|
|
Jerry, there is a big difference on the wire between these two:
[out] uint32 x;
and
[out] uint32 *x;
if you change from
[out] uint32 x;
then you need to change to:
[out,ref] uint32 *x;
otherwise it changes the format on the wire, which means we are no
longer compatible with MS servers.
but be aware that even if you change to a ref ptr, you also need to
change all the client code to set all the return variables in the out
part of the structure. That's why I don't like the MIDL restriction of
forcing the use of ref pointers for output variables - it makes life
much harder when writing client code, and makes the code much more
error prone (just look at all the extra code needed to make this work
again).
I know we could auto-allocate these variables in the generated client
side NDR code, but if we did that then we would have no way of doing a
_real_ ref out pointer, which we really wanted to set to some already
allocated variable.
So please hold off on changing our idl to use the MIDL convention for
output variables until Jelmer and I have had a good "chat" about this :-)
(This used to be commit 555aed43ba3c08360ca7fa921622b80732a7f657)
|
|
(This used to be commit ab0a798c57564901f0adcd8aedc1ef0928e79edd)
|
|
beginnings of smbtorture test for it
(This used to be commit 57f56957176ca04f3abb579b557aade71f8d361d)
|
|
- change the test for net/if.h to do a full compile, not just an
existance test. net/if.h is completely broken on hpux, and can never
compile (it uses stuff before it defines it), so by using a
AC_TRY_COMPILE() test we avoid using net/if.h on hpux, which should
fix the build
(This used to be commit bde18f3d5ce837f600bae8d63f31d92a579fe1f2)
|
|
(This used to be commit 694677dafefdd94fa0a9bed93efab70c528dcb26)
|
|
(This used to be commit 86b4624226d6e72645221cadb8669b0f1aba0903)
|
|
Also cope with the fact that we define the FSTYPE as NTFS by default.
We never use this anywhere else, so we may just change it, but just
detect the fact and return DISK in share_classic for now.
(This used to be commit 4daf5f7764ce69c14066f7320961c90141f0863a)
|
|
metze
(This used to be commit d9137edbdb61f2847453357b94050e5afc2fe68b)
|
|
(This used to be commit caac6cf817b09c864554e992f89437f6205b948b)
|
|
include them explicit
- undefine _XOPEN_SOURCE_EXTENDED for the AIX interface detection test
#define _XOPEN_SOURCE_EXTENDED 1 brings in sa_len to sockaddr on Tru64
which means the AIX code compiles...
metze
(This used to be commit 04a0a5144a249e12a9dcb327c5b6055e6a6135db)
|
|
(This used to be commit 60076fa87d6c68295ebedc28cdbbd4556cfd0ae7)
|
|
for nicer output
metze
(This used to be commit 888a769af557d050d99df703ce5f651688c837c5)
|
|
defined
try to find the problem on Tru64...where configure says the AIX method finds 1 interface
but later can't compile netif.c. (revision 18486 was the last that detects ifconf with 2 interfaces)
metze
(This used to be commit 8fa9852160680054ddb5316c4ee03a03f8553a37)
|
|
to prevent rebuilding.
we do
make everything
make everything
make bin/smbtorture
make test
in the buildfarm and rebuilding parts isn't that nice
metze
(This used to be commit 212fa7977d514f81ce4301902a8038869ee02b4e)
|
|
- to get the ordering right we need to specify AC_CANONICAL_BUILD explicit
- add AC_CANONICAL_TARGET
metze
(This used to be commit 1ea52d75849f004752cdbe11a3dddd10b4afe47d)
|
|
Now we can add and remove a share from the "Computer Management"
console (not yet modify!) usinf share backend = ldb
(This used to be commit ae2f6d4a5a372a37b9783a02bb8e7f16588b21f0)
|
|
systems. drop to 50
(This used to be commit ce5d5a187264af2b87e2919bdcc5f478cce02df9)
|
|
showing on test failure and showing all the smbd output each time.
(This used to be commit 1dfac4666423d7e0565795e3eae72da7e25a5b54)
|
|
(This used to be commit 5a8becb1be1b41b4fecf9f9f47a60eed5f77c264)
|
|
also fix cn name for this record, and ensure tests/tmp is created
(This used to be commit 588c91f06b90467279600fe6a1222273b5d53915)
|
|
the external popt (this affects hpisgr8)
(This used to be commit 9afbd60f91bca84dd645372ed7139e42f712384d)
|
|
(This used to be commit fbe13ed83e2f3508db6d77f4bd65a913ef12ff02)
|
|
libreplace. This should fix the standalone build of tdb on HPUX, where
we need to blacklist mmap.
Unfortunately this requires that we have a copy of config.guess and
config.sub in each of our project subdirectories. I tried to find a
way to use something like AC_CONFIG_AUX_DIR($libreplacedir) and just
put config.{guess,sub} in the lib/replace/ directory, but I couldn't
figure out how to do that in a way that kept autoconf happy for each
of our separate builds. Any autoconf guru out there see a way to do
this?
(This used to be commit 823cd3ab35456769dcefee17bdaca21f01ba0f63)
|
|
caused the RPC-SECRETS test to crash smbd in an inlined version of
this memcmp() call. This patch should have absolutely no effect at
all, but in fact it prevents the crash.
Disassembling at the point of the crash, it shows that gcc is inlining
the memcmp(). I don't know enough MIPS assembler to actually spot the
bug. In case anyone reading this does know MIPS assembler, here is the
gcc generated code that crashes:
0x105e0218 <gssapi_krb5_verify_header+168>: lw $t1,52($sp)
0x105e021c <gssapi_krb5_verify_header+172>: lw $t1,0($t1)
0x105e0220 <gssapi_krb5_verify_header+176>: lhu $t1,0($t1)
0x105e0224 <gssapi_krb5_verify_header+180>: lw $t2,68($sp)
0x105e0228 <gssapi_krb5_verify_header+184>: lhu $t2,0($t2)
0x105e022c <gssapi_krb5_verify_header+188>: subu $t1,$t1,$t2
it gets a segv at 0x105e0220.
lha, what do you think of this? The change should be innocuous on all
other platforms, apart from making the code harder to read :(
(This used to be commit 95455b57893c99d6d2dc20c4f75042ae4c1cfe85)
|
|
(This used to be commit 0ee42669d3a5ec062ec14ecda94342b0df519964)
|
|
(This used to be commit f67b4d58acd2c3746e5ffeffa804e888ca3c49a5)
|
|
function name for _all_ RPC servers...
(This used to be commit 234272e39d7dc79f5e7e0399aebf5681a92981b2)
|
|
(This used to be commit 9b9f058edb033c999c4430add4f05459ac43c9e2)
|
|
(This used to be commit 7a2afc3e0c0e8c0e9360805e8b4326e257b1e9dc)
|
|
prototype in that case
(This used to be commit 64b5ff171d04bd93bd41309edfbe532c01a46e4f)
|
|
added.
(This used to be commit 3e1844b2b229d6e84436d6c455bef707d0efcafc)
|
|
(This used to be commit 46aa8a5e8914184575fa6b9ec9edced8dd615eab)
|
|
causing this test to fail.
(This used to be commit fc3f41a4ab38fd32386c5bdb1979cc26892afcf8)
|
|
metze
(This used to be commit 8e49dc69e7d588c85c9e9e7b24b595c61c1da95a)
|
|
telldir() is different on older OpenBSD versions
seekdir() is different Tru64
tridge: OpenBSD seems to like this replacement:-)
while MAC OS 10 gets 134 runtime error:-(
lets wait what Tru64 will give
metze
(This used to be commit 1f4e602ff239b7feabb2dd1d6938dedf91bde5cd)
|