similar to: inherit group on new files/directories

Hello! Please look at this log entry: [2018/10/30 15:26:04.013132, 0] ../source3/param/loadparm.c:3358(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/share failed. Permission denied I don't know why this message is spamming my log, my version of samba is 4.9.1 from fedora 29, but problem existed long time ago with older versions. here is usershares

sorry for opening this thread again, but it looks like there is some bug in samba usershares. I successfully reproduced this bug in OpenBSD and in Fedora. Steps to reproduce: 1) Use default samba config. 2) Add options: usershare max shares = 5 (or else number) usershare allow guests = Yes 3) create usershares directory (personally i use directory path from testparm -v) 4) create group usershare

Mandi! Rowland Penny via samba In chel di` si favelave... > I think you need to post your smb.conf, I (at least) am struggling to > understand why you have moved 'sysvol' from /var/lib/samba/ > to /var/lib/samba/usershare/, it isn't a usershare! I've not done that! root at vdcsv1:/home# samba-tool testparm Press enter to see a dump of your service definitions #

Mandi! Rowland Penny via samba In chel di` si favelave... > Is there a file that starts 'sysvo' in /var/lib/samba/usershares ? root at vdcsv1:~# ls -la /var/lib/samba/usershares/ totale 8 drwxrwx--T 2 root sambashare 4096 set 19 2017 . drwxr-xr-x 8 root root 4096 mar 19 11:58 .. No. > > I can disable 'usershares'? > You shouldn't have to, by

Hello all, I want to set up a share for a project (enseign) First thing I did is to create a group for that project (with smbldap-groupadd) and add project members to that group. Then I created a test_smb directory on my linux server with the following access rights: drwxrwx--- 2 gbayard enseign 4096 avr 29 15:03 /test_smb Note: the idea is that only group members should be able to

root:usershare пн, 5 нояб. 2018 г. в 14:44, Rowland Penny via samba <samba at lists.samba.org >: > On Mon, 5 Nov 2018 14:03:54 +0300 > Илья Коскин via samba <samba at lists.samba.org> wrote: > > > sorry for opening this thread again, but it looks like there is some > > bug in samba usershares. > > I successfully reproduced this bug in OpenBSD and in Fedora.

Dear all I have upgraded my Samba from 3.5.x to a newest 3.6.0 version. My Samba is connected to an Active Directory 2008 R2 the "getent passwd" did not display any ActiveDirectoy Domains users. the "net ads group" display correctly the ActiveDirectory groups : net ads group Administrateurs Utilisateurs Invit?s Op?rateurs d?impression Op?rateurs de sauvegarde Duplicateurs

Dear Have connected SAMBA to an Active Directory server The getent did not show any user and winbindd claim : [2011/09/07 11:33:29.417355, 1] libsmb/cliconnect.c:1769(cli_negprot_done) cli_negprot: SMB signing is mandatory and the server doesn't support it. [2011/09/07 11:33:29.417444, 1] winbindd/winbindd_cm.c:856(cm_prepare_connection) cli_negprot failed: NT_STATUS_ACCESS_DENIED

Hi! I've got Debian 4.0 on an NSLU2 with Samba. The system is on an USB-Stick, the Samba share is on an USB-Disk. Copying files to the samba share make some problems here. I get a large delay before the transfer starts and I get timeouts with files larger than 150MB. I found out, that samba is writing a dump file on the disc before the transfer starts, which causes the delay/timeout. This

oh sorry, of course i have a typo in 6. The user usershare dir depends on system where samba was build. For example in fedora it is /var/lib/samba/usershares, and in openbsd it is /var/samba/usershares. I am sure i am doing everything right. пн, 5 нояб. 2018 г. в 19:10, Rowland Penny via samba <samba at lists.samba.org >: > On Mon, 5 Nov 2018 18:05:09 +0300 > Илья Коскин via samba

Hi all, I am having a very strange issue with Samba, users who are not the owner of files but are in the same group cannot delete or rename files via Windows. For example the user ?sean? in the ?storage.access? group CANNOT delete or rename a folder called temp via windows but CAN delete or rename via terminal session. The folling three folders have the folling permissions: /storage/

Hello, I notice if I simply comment out a share or remove entirely. I receive errors such as theses. Is there a proper protocol to follow when removing a share? process_usershare_file: stat of /var/lib/samba/usershares/myshare failed. No such file or directory ../source3/param/loadparm.c:4366(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/myshare failed.

Hello Everyone, Good evening! Here a Background: I am moving from samba47 to samba48 - I am keeping my existing scripts and config files. The messages below are now appearing while executing some tasks in samba48 only - samba47 is not showing it: #Unknown parameter encountered: "use spnego" #Ignoring unknown parameter "use spnego" #Unknown parameter encountered:

Hi, after upgrading Samba 3.0.24 to Samba 3.5.4 a strange problem occurs: Users cannot anymore save files in MS Office (Word/Excel) on Samba shares. More precisely: Save as Office 2007 documents or RTF-Files works fine, but *.doc ist avoided with Error Message "Not enough memory". Of course there are lots of memory/space and ACL/Permissions should be ok since other file operations

Sirs: We are a Vinyl window manufacturing plant in central Washington State, USA. We have been running linux with samba for file and print services for eight or ten years now. Much of our production software is in house, and built on CA clipper 5.2, using dbf files as the primary data store. The clipper dbf file format supports both record locking and file locking along with shared file

Hi all, I sometime have a strange behavior when using MS Office and saving files. First things first: - OS CentOS 6.7 x86_64 - SAMBA version 3.6.23, configured as member server (see [1] for full configuration) - inotifywait watching my shares to replicate them off-site - about 100 W7/W8 clients with MS Office 2010 Using inotifywait, I tracked how MS Office file save function works. Basically,

I set up two usershares to share my music and photos read-only a while ago. I recently decided to remove the usershares and recreate the shares in my smb.conf with read/write access to some users. If the shares have the same names that the usershares originally had, it seems that the original read-only permissions still apply; however, if I change only the names of the shares, I gain read/write

A couple of things possible, from 4.8.0 winbind must be running and your smb.conf is, to be blunt, rubbish. You need to set the workgroup, you need to have idmap config lines for the workgroup, the 'winbind enum' lines only slow things down and 'map untrusted to domain' has been removed. Winbind is running and the workgroup was set as well. I omitted some lines from the smb.conf

Hi Samba-Gurus out there! Ive got some strange problem here i already tried to track down searching the net and reading tons of manuals. no luck yet. So now ill give the Mailing list a try. The Situation: ############ We run a virtual (VM) Debian Lenny Server as LDAP (OpenLDAP) and Samba Domaincontroller/Fileserver. The Server also does NFS Exports of the same Volumes to other Debian Etch

Hello, Server-Side Copy Offload wiki page states in Limitations section that - Both source and destination files must reside on the same Samba share! I was able to copy file between different shares located on the same zfs Pool without generating network traffic. Shares were created on Debian 8 with zfs filesystem and client was Windows Server 2016 machine mapping shares as separate drives.