Displaying 3 results from an estimated 3 matches for "lp_widelinks".
Did you mean:
lp_wide_links
2008 Dec 23
0
[jra@samba.org: Patch to improve Samba write speeds on Linux ext3 with 3.2.x]
....ptr = &sDefault.bStrictAllocate,
+ .ptr = &sDefault.iStrictAllocate,
.special = NULL,
- .enum_list = NULL,
+ .enum_list = enum_strict_allocate,
.flags = FLAG_ADVANCED | FLAG_SHARE,
},
{
@@ -5274,7 +5289,7 @@ FN_LOCAL_PARM_BOOL(lp_manglednames, bMangledNames)
FN_LOCAL_BOOL(lp_widelinks, bWidelinks)
FN_LOCAL_BOOL(lp_symlinks, bSymlinks)
FN_LOCAL_BOOL(lp_syncalways, bSyncAlways)
-FN_LOCAL_BOOL(lp_strict_allocate, bStrictAllocate)
+FN_LOCAL_INTEGER(lp_strict_allocate, iStrictAllocate)
FN_LOCAL_BOOL(lp_strict_sync, bStrictSync)
FN_LOCAL_BOOL(lp_map_system, bMap_system)
FN_LOCAL_...
2010 Mar 03
1
unix exts / wide links / symlinks
Hi!
How can I let recent smbd versions let unix clients access and resolve 'wide'
symlinks locally? My goal is that clients may use any kind of symlink (internal
and external to a mounted share) like on any other unix-style file system
without smbd interfering.
My understanding is that since version 3.4.6, smbd effectively denies access of
clients to 'wide' symlinks, i.e. out of
2011 Jun 11
0
RFE: Proposed fix for incompat introduced with 'unix extensions' and 'wide links'....in 3.4(?)..
...&Globals.bUseSpnego)
FN_GLOBAL_BOOL(lp_client_use_spnego, &Globals.bClientUseSpnego)
FN_GLOBAL_BOOL(lp_hostname_lookups, &Globals.bHostnameLookups)
@@ -9905,6 +9917,7 @@
void widelinks_warning(int snum)
{
+ if (lp_client_managed_widelinks()) return;
if (lp_unix_extensions() && lp_widelinks_internal(snum)) {
DEBUG(0,("Share '%s' has wide links and unix extensions enabled. "
"These parameters are incompatible. "
@@ -9915,10 +9928,9 @@
bool lp_widelinks(int snum)
{
- /* wide links is always incompatible with unix extensions */
- if (lp_unix_extensions()...