Age | Commit message (Collapse) | Author | Files | Lines |
|
This reverts commit 8532faffd08bbbcfaac60fd866fa5ab255913d4a.
swat needs zlib through ../librpc/ndr/ndr_compression.c, function
ndr_pull_compression_mszip_chunk(). This fails to link at least
on our build farm bsd boxes.
Michael
|
|
This reverts commit 1f265548e7d17a4ed83705149dd944fcdd31134d.
smbd needs zlib through ../librpc/ndr/ndr_compression.c, function
ndr_pull_compression_mszip_chunk(). This fails to link at least
on our build farm bsd boxes.
Michael
|
|
Signed-off-by: Michael Adam <obnox@samba.org>
|
|
the mount helpers don't use any popt symbols
Signed-off-by: Michael Adam <obnox@samba.org>
|
|
swat doesn't use any zlib symbolѕ
Signed-off-by: Michael Adam <obnox@samba.org>
|
|
smbd doesn't use any zlib symbolѕ
Signed-off-by: Michael Adam <obnox@samba.org>
|
|
pam_smbpass doesn't use the krb5 stuff
Signed-off-by: Michael Adam <obnox@samba.org>
|
|
Guenther
|
|
|
|
Guenther
|
|
Michael
|
|
|
|
|
|
we can provide the path to ctdb via the --with-ctdb=... configure flag like we
do it with other packageѕ, too. There is no need for another redundnant
Makefile hack to point the ctdb header location
Signed-off-by: Michael Adam <obnox@samba.org>
|
|
We keep the seqnum/mid mapping in the smb_request structure.
This also moves one global variable into the
smbd_server_connection struct.
metze
|
|
It's the job of the caller to maintain the seqnum/mid mapping.
Hopefully we can use this code in s4 later too.
metze
|
|
This prepares a large simplification of the smb_signing code
metze
|
|
|
|
This is to allow for testing samba_version_string() without
the need to compile any of the larger binaries like smbd or net...
Michael
|
|
metze
|
|
correctly.
This is a really nasty one to fix as in order to successfully update the
passdb.tdb we must do the equivalent of a tdbbackup to move to the new hash
values before we do the upgrade.
Jeremy.
|
|
Guenther
|
|
Good-Bye, last hand-marshalled rpc functions, rest in peace.
Guenther
|
|
Guenther
|
|
|
|
|
|
password talloc'ed strings within the cli_struct.
Jeremy.
|
|
|
|
|
|
merged.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
auth_onefs_wb.c -> auth_wbc.c
pdb_onefs_sam.c -> pdb_wbc_sam.c
No changes to functionality
|
|
|
|
metze
|
|
This fixes a bug in 116ce19b, where we didn't clear the pid cache in
become_daemon() and thus the /var/run/smbd.pid didn't match the actual
pid of the parent process.
Currently S4 will clear the pid cache on fork but doesn't yet take
advantage of the pid cache by using sys_pid() instead of the direct
get_pid().
|
|
All of the spoolss change notify code uses pidl generated functions now.
Guenther
|
|
|
|
Implements a custom backend for onefs that exclusively uses the wbclient
interface for all passdb calls.
It lacks some features of a standard passdb.
In particular it's a read only interface and doesn't implement privileges.
|
|
This new backend is custom tailored to onefs' unique requirements:
1) No fallback logic
2) Does not validate the domain of the user
3) Handles unencrypted passwords
|
|
|
|
The OneFS Samba implementation of change notify is modeled after the
usage of Linux's inotify kernel subsystem. A single call is made
into the onefs.so VFS module to initialize kernel tracking of certain
file change events. When these events occur a kernel notification is
sent to smbd and the notification event is translated and given to the
general Samba Change Notify layer through a callback function.
The most difficult aspect is converting an SMB CompletionFilter to
a matching ifs_event mask, and then back to an appropriate change
notify action. Currently, not all possible cases are handled by the
this module, but the most prevalent ones, which are tested by
smbtorture, are implemented.
|
|
|
|
Add 'perfcount module = pc_test' to exercise this module. Results are
logged into smb.log every 50 operations (configurable via smb.conf).
|
|
* Much of the beginning should look familiar, as I re-used the OneFS oplock
callback record concept. This was necessary to keep our own state around - it
really only consists of a lock state, per asynchronous lock that is currently
unsatisfied. The onefs_cbrl_callback_records map to BLRs by the id.
* There are 4 states an async lock can be in. NONE means there is no async
currently out for the lock, as opposed to ASYNC. DONE means we've locked
*every* lock (keep in mind a request can ask for multiple locks at a time.)
ERROR is an error.
* onefs_cbrl_async_success: The lock_num is incremented, and the state changed,
so that when process_blocking_lock_queue is run, we will try the *next* lock,
rather than the same one again.
* onefs_brl_lock_windows() has some complicated logic:
* We do a no-op if we're passed a BLR and the matching state is ASYNC --
this means Samba is trying to get the same lock twice, and we just need
to wait longer, so we return an error.
* PENDING lock calls happen when the lock is being queued on the BLQ -- we
do async in this case.
* We also do async in the case that we're passed a BLR, but the lock is not
pending. This is an async lock being probed by process_blocking_lock_queue.
* We do a sync lock for any normal first request of a lock.
* Failure is returned, but it doesn't go to the client unless the lock has
actually timed out.
|
|
|