| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
This is a place where an explicit dmapi_destroy_session would be needed. But we
don't use a destructor for this.
|
|
|
|
|
| |
Same argument as in 997a64f6fb11e19d78c: If tdb_close() was needed at exit
time, we'd have more severe problems by now.
|
|
|
|
|
| |
The dispinfo structs need to survive within a process across pipe opens,
but they don't have a special destructor
|
|
|
|
|
| |
None of the pdb backends have special destructors that need to be run at
program exit.
|
| |
|
|
|
|
|
|
|
| |
Quite a few of our internal routines put stuff on talloc_tos() these days.
In top-level netapi routines, properly allocate a stackframe and clean it
again. Also, don't leak memory in the rpccli_ callers onto the libnetapi
context.
|
|
|
|
|
|
|
|
| |
seen from Win7 clients.
These suffixes and their meaning are not documented (yet).
Guenther
|
| |
|
| |
|
|
|
|
|
|
| |
Even printing once per connection, level 0 was too spammy with
Windows clients frequently sending FSCTL_GET_OBJECT_ID which
is unsupported.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, only one fd handler was being called per main message loop
in all smbd child processes.
In the case where multiple fds are available for reading the fd
corresponding to the event closest to the beginning of the event list
would be run. Obviously this is arbitrary and could cause unfairness.
Usually, the first event fd is the network socket, meaning heavy load
of client requests can starve out other fd events such as oplock
or notify upcalls from the kernel.
In this patch, I have changed the behavior of run_events() to unset
any fd that it has already called a handler function, as well
as decrement the number of fds that were returned from select().
This allows the caller of run_events() to iterate it, until all
available fds have been handled.
I then changed the main loop in smbd child processes to iterate
run_events(). This way, all available fds are handled on each wake
of select, while still checking for timed or signalled events between
each handler function call. I also added an explicit check for
EINTR from select(), which previously was masked by the fact that
run_events() would handle any signal event before the return code
was checked.
This required a signature change to run_events() but all other callers
should have no change in their behavior. I also fixed a bug in
run_events() where it could be called with a selrtn value of -1,
doing unecessary looping through the fd_event list when no fds were
available.
Also, remove the temporary echo handler hack, as all fds should be
treated fairly now.
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
| |
|
| |
|
|
|
|
| |
TDB_INCOMPATIBLE_HASH.
|
|
|
|
|
|
| |
days we moved away from fstrings.
Guenther
|
|
|
|
|
|
| |
not yet published printer.
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
|
|
| |
seen from win7.
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
|
|
|
|
| |
this fails intermittently on sn-devel. Guenther suggested adding it to
knownfail
Autobuild-User: Andrew Tridgell <tridge@samba.org>
Autobuild-Date: Fri Oct 1 04:37:36 UTC 2010 on sn-devel-104
|
|
|
|
|
|
|
|
| |
This is supposed to improve the winbind reconnect time after an ip address
has been moved away from a box. Any kind of HA scenario will benefit from
this, because winbindd does not have to wait for the TCP timeout to kick in
when a local IP address has been dropped and DC replies are not received
anymore.
|
|
|
|
|
| |
Giving the parent pid to reinit_after_fork is not a good idea....
None of the other callers do this, checked it.
|
| |
|
|
|
|
|
|
| |
_spoolss_GetPrinterDriver2.
Guenther
|
|
|
|
|
|
| |
important to get right.
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
|
|
|
|
|
| |
We were creating a new printer (with a very broken name) out of the
lasttimestamp entry all the time.
Simo, please check.
Guenther
|
|
|
|
|
|
|
|
| |
non-developer builds.
This will be removed once we have the rpc modules subsystem in place.
Guenther
|
|
|
|
| |
thanks to ita for this
|
|
|
|
|
|
| |
module by default).
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
|
|
|
|
|
|
|
| |
If select returns -1, we can't rely on the fd sets. The current code might loop
endlessly because when putting an invalid fd (the closed socket?) on the read
set, a select implementation might choose not to touch it but directly return
with EINVAL. Thus run_events will see the socket readable, which leads to a
"return true", and thus a NT_STATUS_RETRY -> same game again.
We should never get into this situation, but to me the logfiles given in bug
7518 do not reveal enough information to understand how this can happen.
|
| |
|
|
|
|
| |
Guenther
|
|
|
|
| |
Guenther
|
|
|
|
|
|
|
|
|
| |
Without this, all security descriptor checks for the winreg spoolss backend fail
and make our spoolss system in its current shape basically unusable.
Andreas, please check.
Guenther
|
|
|
|
| |
Guenther
|
| |
|
| |
|
|
|
|
| |
No destructor needed, so we can as well use the NULL context
|
| |
|
| |
|
| |
|
| |
|