IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
perfectly.
This check in covers the remaining fixes and enhancements to complete the
server. In a subsequent check-in, I need to learn about the new qooxdoo
packaging mechanism. Although it'd be nice to have the whole source tree,
that's huge and needn't be in samba svn. It's now supposed to be very easy to
package qooxdoo, so I'll figure out how that's done and then check in the
relevant small number of files.
Steps after that involve generating the stubs to allow various ejs functions
to be called via JSON-RPC.
Derrell
(This used to be commit 5bfebbda7a5d28d4deb31c54a8feb24c4416cbf6)
* Make sure to check for NULL pointers when dealing with
[out,unique] before assigning valoues
* Detect RPC faults and return immediately
(This used to be commit c96dae478c2fee2fede9c853a71c8079bbb8ba47)
- do not stop NET-API-USERMODIFY test when a single field fails
- add account flags to the fields tested
- separate "cleanup" step from closing domain at the end
rafal
(This used to be commit 16fde3b8e2c93ec10e43bb09334bf460db8ac70b)
strings, but is generally useful for creating ejs variables from object or
array literals, which aren't supported in the old version of ejs that we're
using.
This parser is implemented in C, but is callable from an ejs script via
literal_to_var().
(This used to be commit 82fdcd9339a8ffb1016b96c06f7d6580aa759174)
Attempt to fix the BSD RAW-CHKPATH failures: In Samba3 we rely on opendir
returning ENOTDIR when the file opened is not a directory. Can we merge this
back into Samba4?
This includes the tabs->spaces fix requested by Stefan.
Volker
(This used to be commit 7b9ee1171ddc89537ba3b286f20c722fb70c980b)
ldb_msg_find_attr_as_string() to work correctly.
Thanks to Jim Myers for spotting this!
(This used to be commit b2076c1a7e4b70644b59689ce46952ef940be6b0)
- talloc_free(talloc_autofree_context()); should not result
in a SIGABORT on exit
- add a test for this, but this test can also pass in the standalone build
and samba3, as samba4 uses talloc_autofree_context()
metze
(This used to be commit 2be48c1b033dceb9517826054b8ea97df2c94472)
DB_CONFIG file, we now get reasonable enought performance to pass
'make test' against OpenLDAP.
We do have to double the maximum runtime for the torture client however.
Andrew Bartlett
(This used to be commit 5b3c8cc036c1180c9e96d9aaacd3f2e0a83460e5)
http://www.ee.oulu.fi/research/ouspg/protos/testing/c06/ldapv3/
The issue here is that if the UTF8 conversion fails, because this
isn't actually UTF8 data, then we need to do a binary compare instead.
Andrew Bartlett
(This used to be commit a113e47784157ec6086b014c1fc998e8a23e7382)
ac_cv_gnu_ld_no_default_allow_shlib_undefined
and as -Wl,--allow-shlib-undefined is supported on SuSE 7.3
I don't see a problem is always pass it explicit
metze
(This used to be commit 79db6bddc5fc1b97f0165348f72b6a2489b62be0)
took a _LONG_ time to find.
The problem was that when encoding/decoding password buffers we use
the pull/push string functions, which by default align unicode
strings. But on solaris sparc the buffer is not aligned always (its a
stack variable, an array of uint8_t). That perfectly OK in C, so we
just tell the pull/push functions not to auto-align.
(This used to be commit bb7835eced00607eb6b1725be6d96a6dcb842049)
it contains the ioctl() prototype on some systems
and we need to make sure it gets included before socket_wrapper
defines ioctl swrap_ioctl
metze
(This used to be commit f37b13cbe65404f27d31b8020afb2f542313f4d3)
ldb_set_umask() (which is what we had discussed) as it doesn't
actually set the umask (in effect it sets the inverse of the umask -
the perms to be used for the file)
(This used to be commit 7e2ec875908c112d5c3b0f6d18f9a8bbacf33539)
Samba4 smbd force the umask to 0, which meant we ended up with ldb
being world writable.
This isn't really an ideal fix, as it means ldb no longer honors umask
(as it should do, like all good libraries).
Unfortunately the 'proper' fix is too complex for now
this also merges a tiny code style fix from s4 to s3
(This used to be commit 1a42f38dfdc55d7429a1f8d3e811f3d857195a58)
