Age | Commit message (Collapse) | Author | Files | Lines |
|
variable at the correct point just before the write
call is scheduled.
Jeremy.
(This used to be commit e076dc16462a3ce11105bf9a729ec59ddd9bdc75)
|
|
(This used to be commit 8f6cf4b8c2568c737fa31494b844ae021a42a4fc)
|
|
Michael
(This used to be commit 235a5ae4cdf3ea238728c2e89a4318c18257426a)
|
|
on the lists :-).
Jeremy.
(This used to be commit f075620d2071aaecb72e93cbda32c4f624f23d86)
|
|
communication failures. Set timeout to 5 mins. Ensure that
we're terminating the correct child (the one we thought we
were talking to). Still setting up my testing environment
but I have high hopes for this being the fix for the 3.0.25b
showstopper.
Jeremy.
(This used to be commit c366df2fe7f1aa1e8fd9bca35bc3b029d76b3abc)
|
|
based on patch from MORIYAMA Masayuki <moriyama@miraclelinux.com>.
Jeremy.
(This used to be commit 0f10d2ed312115998d5ce1dc88a8d9207c9e4959)
|
|
Thanks to SATOH Fumiyasu
Fixes 4720
Jerry,
this is a showstopper for 3.0.25b, please grab it into
SAMBA_3_0_RELEASE before cuting the tarballs.
Simo.
(This used to be commit d2846e6b90e8774a729e6cf3a0c809aa8ff4a93a)
|
|
Guenther
(This used to be commit 27fdf995d13611ebc9e57895f886c184e9027c4d)
|
|
where a
torture test would be much more appropriate). Fix #4408.
Guenther
(This used to be commit 7514a370cae9c6fdacffd2b885fd93cb1230ce96)
|
|
(This used to be commit f2050f5a3af382ad88071a5d5f6b172af4143e0f)
|
|
Michael
(This used to be commit 4b5d9b2ba773e6ce57c38e3c0d5af72ad5a98b51)
|
|
Guenther
(This used to be commit 5456ea59ba12593b0aac9745b41cdd0f5ec0a559)
|
|
Guenther
(This used to be commit 2592e68a43a73474e1bb53f83642c864fd159b45)
|
|
Guenther
(This used to be commit 0d956a8e45cd4421cddb8e077e1960dafac3a4d0)
|
|
Guenther
(This used to be commit 4e1e697ac48513719bd3a2152f17871bc00df796)
|
|
<nakabayashi@miraclelinux.com>.
Jeremy.
(This used to be commit 3f70c1b10589965ee95ef7497ff6fb7c39475569)
|
|
Jeremy
(This used to be commit dc287adff249e45a5584ec5fb9177e62152a7403)
|
|
Long overdue fix....
Jeremy.
(This used to be commit 073fdc5a58139796dbaa7ea9833dca5308f11282)
|
|
Michael
(This used to be commit 3695a66166c6aa88051b21ad40a19f1cc8b87c7b)
|
|
Michael
(This used to be commit a4714b34284f9e205556166166f41ce9dad4d3da)
|
|
Jeremy.
(This used to be commit 1e66a8340e7db9c42507d93d67ad33abadabd2a1)
|
|
This simplifies the usage of this command from
"net conf setparm <section> <param> <type> <value>"
to
"net conf setparm <section> <param> <value>".
Micheal
(This used to be commit 41a8f8ec5f5361f536d047c4ca5d90203b16ff06)
|
|
Michael
(This used to be commit 73e41c1d0a7af7488b35b54182ea532103b51fd4)
|
|
Michael
(This used to be commit f0992c0d79bb6a5810c84a9eac208d83390bb047)
|
|
(This used to be commit ec22c30581f0809b6a008982abceb97b4f9cd12e)
|
|
(This used to be commit 1d941961e0739c22d32720bac4ecd6beef6d74c5)
|
|
(This used to be commit 13c6eacff02b55b9fd6201406802f271dcf13e8e)
|
|
CloseDir.
(This used to be commit 48cdafc10a0eb615d79057ec9e235ffe9a85e016)
|
|
make test
to break. The Solaris CC put the static char InBuffer[TOTAL_BUFFER_SIZE] on an
odd address, the malloc'ed one is always aligned. The problem showed up in
pull_ucs2, ucs2_align uses the address of InBuffer as an indication whether to
bump up the src of the string by one. Unfortunately in the trans calls the
data portion is malloced and thus has different alignment guarantees than a
static variable. This one is bigger....
Volker
(This used to be commit 6affd7818f6981be2a9f44fcf302e7fddb468347)
|
|
Michael
(This used to be commit d90aa8368af624761a19cd1e55ed9f18bc64f45d)
|
|
In make_server_info_pw() we assign a user SID in our
authoritative SAM, even though this may be from a
pure "Unix User" that doesn't exist in the SAM.
This causes lookups on "[in]valid users" to fail as they
will lookup this name as a "Unix User" SID to check against
the user token. Fix this by adding the "Unix User"\unix_username
SID to the sid array. The correct fix should probably be
changing the server_info->sam_account user SID to be a
S-1-22 Unix SID, but this might break old configs where
plaintext passwords were used with no SAM backend.
Jeremy
(This used to be commit 80d1da7e6cce451d3934751feaa6ad60a337e3db)
|
|
Remove the allocated inbuf/output. In async I/O we copy the buffers
explicitly now, so NewInBuffer is called exactly once. This does not
reduce memory footprint, but removes one of the larger chunks that
clobber the rest of the massif output
In getgroups_unix_user on Linux 2.6 we allocated 64k groups x 4 bytes
per group x 2 (once in the routine itself and once in libc) = 512k just
to throw it away directly again. This reduces it do a more typical limit
of 32 groups per user. We certainly cope with overflow fine if 32 is not
enough. Not 100% sure about this one, a DEVELOPER only thing?
(This used to be commit 009af0909944e0f303c5d496b56fb65ca40a41d5)
|
|
(This used to be commit 9dcbef9615aec7cfe8f72e6f21f01af4e4fcc90e)
|
|
This closes #4624 for me.
(This used to be commit 3635b304155299ac93fda57e5e9ece0acd605e77)
|
|
Got report this is all ok form a tester. Close a loong
standing bug preventing people to freely use any character
in their password when printing via cups were involved.
(This used to be commit 54ca011212982cf1d94a76ca9d39c391783da04f)
|
|
that....
Volker
(This used to be commit 1a45ea28ced3775acd6127e05e844873ed23d40b)
|
|
why check_path_syntax should not be able to run in-line. The destination
pointer either walks side by side with the source pointer or is
decremented. So as far as I can see s>=d is true throughout the whole
routine.
Jeremy, I'm checking this only into 3_0 for now. Please review and ack
or directly merge this to 3_0_26.
Thanks,
Volker
(This used to be commit 34a13c82a3b72d6900614b57c58fbaefeeca8fa7)
|
|
Jeremy, I am always very confused about the different length arguments
in convert_string and friends. Can you take a look at the change in
string_replace and verify it's ok? Thanks!
While at it, remove the pstring limit for strhasupper and strhaslower.
(This used to be commit e6e5703658aeaeb0cca5d7281095e17553001d4b)
|
|
Change rename_internals to open the file/directory and then call
rename_internals_fsp. Two reasons: Remove code duplication and remove a
race condition. The race condition was due to the fact that in
can_rename the share mode check closed the file and then after that did
the rename.
(This used to be commit aa16d8a649d1a38593edd5ca94ed2c7d4291911b)
|
|
- when cleaning up invalid locks make sure we mark the lck
struct as modified so it'll get saved back correctly (that
was the original intent).
Jeremy.
(This used to be commit cbf0829abcc3689edd7ab225054dfc79d43c6309)
|
|
Jeremy.
(This used to be commit 5b2836e2d5f9081b5e39637538d8f2d19e1115c4)
|
|
Jeremy.
(This used to be commit 03763bc5287fef5f100c911041668e23d4305f8d)
|
|
Jeremy.
(This used to be commit fca5637dc6c91a57c4e087670068688557e5bf32)
|
|
reg #defines use "REG_" prefix. Michael - please check
gcc warnings on compiles.
Jeremy.
(This used to be commit 7885b68bb5df0ebe290feca0e74b4a20ef59e718)
|
|
failed expression in SMB_ASSERT.
(This used to be commit 171dc060e2a576d724eed1ca65636bdafffd7713)
|
|
The global options are stored as values in the subkey "global"
of the SMBCONF registry key.
The activation is accomplished in smb.conf though a new special
semantic of the "include" parameter: "include = registry" triggers
the processing of the registry global options exactly at the
position of the include statement. Options read from the registry
take the same precedence as parameters loaded from a file via
include. Need to reload the registry globals is detected by
watching the tdb sequence number.
Registry shares are automatically activated when the registry
globals are processed.
So a "registry only" configuration can be realized by an
smb.conf that looks as follows:
================================
[global]
include = registry
================================
The global options and registry shares can be conveniently
edited with the "net conf" utility.
Caveat:
A possible pitfall consists in using "include = registry"
together with the "lock directory" directive in the registry.
This problem will be addressed in the next time.
Note on the code:
Processing of the registry options is accomplished by a function
process_registry_globals() in loadparm.c The current version is
only an interim solution: It is handcoded instead of using the
infrastructure of reg_api.c. The reason for this is that using
reg_api still has too large linker dependencies, bloating virtually
all targets by PASSDB_OBJ, SMBLDAP_OBJ, GROUPDB_OBJ and LDB stuff.
A version of process_registry_globals that uses reg_api is
included but commented out. The goal is to eventually refactor
and restructure the registry code so that one can use the reg_api
to access only the registry tdb and not link all the dynamic
backends with all their linking implications.
(This used to be commit 24b0cbcb3741dd14b04728448a85cc04a057e7d0)
|
|
on failure in the write path.
Jeremy.
(This used to be commit cd3f7dbee809fb40194af0e7509142166e02b252)
|
|
(To be used in other place in subsequent commit.)
Michael
(This used to be commit 6fd71140499e30b8fd0f083301512db7b8c2f236)
|
|
This eliminates the need of maintaining reg_db's own
reference counter for the tdb. Maybe as a next step...
Michael
(This used to be commit 31d64767fc8a73be1f6b81e2712d687897f812a0)
|
|
we are idle and we timed out waiting for something to do.
(This used to be commit b4ab1a0cd992cf9e966b8edb9796d1eae53db744)
|