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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
The userdata is currently unused. It can be used in the future for
passing a context like in samba4 code.
Michael
(This used to be commit 31b31171bd88c41443268d3300c492e2347b9e73)
This is passed to the module init routines.
In case of the registry, this is the path of the
basekey in registry, that is to be used, defaulting
to KEY_SMBCONF (HKLM\software\samba\smbconf), when
NULL is given. This is the only case currently used.
In order to support other keys, registry initialization
for smbconf has to be changed to support different keys.
Michael
(This used to be commit 96434d9dc7a66773e313cc128af57493dee245a1)
..for consistency. Exception: the open/init function, where the smbconf_ctx
is created from the given talloc context.
Michael
(This used to be commit 304dba6cb2184437f3edad065a530d03fb704036)
The former seqnum is hidden inside a struct smbconf_csn.
And the get_seqnum is united with a changed function that
stores the seqnum inside the given csn.
Michael
(This used to be commit 5b6b90900a1a3eab24cb5612d78f9678a363cf73)
Up to the globals had only been fully reset when init_globals() was called
for the first time. But a full restart is needed for use with
"config backend = registry". (And should be with "config file = ...", but
in this case the restart is outsourced to the daemons.) This left
some options (like e.g. "realm") set to values that were set in smb.conf
before the occurence of "config backend = registry".
Now this misbehaviour is fixed with this change.
Michael
(This used to be commit f12259d9c4c34b99f5b655cab4b210159cb0e188)
This makes each entry in the parm table much more comprehensible
at first glance (to me). On the other hand, roughly 9 lines are
used instead of one for each entry which makes the overall list
less clearly laid out, one might argue. But we have 400+ lines
of parameter descriptions anyways...
Michael
(This used to be commit 869a17f1a9ba45d30211c230673c6f4482876b29)
If you create a share on a Windows machine called foo$ then this share is
of the type STYPE_DISKTREE. So it is possible to administrate this kind of
share. Tested on Windows NT and 2003.
In samba we assume that if a share with a $ at the end must be of the type
STYPE_DISKTREE_HIDDEN. This is wrong, so we need a variable in the config
to define if the share should be hidden or not.
(This used to be commit a3da677bf0faed56e6731ee96708a7847a61d118)
warning: ignoring return value of 'asprintf', declared with attribute warn_unused_result
(This used to be commit ad37b7b0aee265a3e4d8b7552610f4b9a105434d)
This replaces the original hand-written tdb code, now that the
linking dependencies have been significantly reduced.
Michael
(This used to be commit d08a3a195718725228bbafa61fd4f0be8aafb43f)
Logging of the ldap libraries appears with a [LDAP] prefix
inside the samba logs. This is controlled by two new parameters:
* "ldap debug level" sets the debug level of the ldap libraries.
It is the bit-field as understood by the openldap server.
* "ldap debug threshold" is the samba debug level at which ldap
logging appears inside the samba logs.
This probably needs some configure tests since it makes
use of the LBER_OPT_LOG_PRINT_FN option to redirect the
debug output of the ldap libraries.
Michael
(This used to be commit 15c25990bd0bfa3145ab3c26d2bdda72993d005c)
I think now that I have changed some substantial logic,
I should confess.... :-)
Michael
(This used to be commit 704ac0ba49134d14dc00769b1cf2d9f55657bdfb)
So external callers can determine if we are running on
registry config without knowing the internals.
Michael
(This used to be commit d8a7c3ec8e2bd548509178f138d00a3b57119d10)
This adds a new config parameter "config backend" that can have
values "file" (default) and "registry". When lp_load() encounters
a "config backend = registry", then all config read up to that
point is discarded and globals are read from registry.
This is done in suche a way that as with "config file",
there is no way back to non-registry config during the
lifetime of a process: The file_list_changed mechanism
does not look at files anymore once config backend is
set to registry. This is modelled after the behaviour
of the "config file" option.
Note that only the global section is read by lp_load().
The shares are handled by the registry shares mechanism,
thus allowing for a smaller memory footprint since
share definitions are read on demand.
This new parameter is intended as a substitute of the
previously installed special semantics of "include = registry"
which allows for messed up mixed configurations.
This parameter (which has not yet been released) will
vanish next.
Michael
(This used to be commit 77b33cf34c2aec6673dfab3962733a60a60d126a)
with Volker. Mostly making sure we have data on the incoming
packet type, not stored in the smb header.
Jeremy.
(This used to be commit c4e5a505043965eec77b5bb9bc60957e8f3b97c8)