search for: privateshares

Displaying 11 results from an estimated 11 matches for "privateshares".

Did you mean: privateshare
2024 Jan 16
1
Share access permission errors after upgrade from 4.12.14
On Tuesday, 16 January 2024 at 09:46, Rowland Penny via samba <samba at lists.samba.org> wrote: > As far as I can see, unraid is based on slackware, so it should work. > Is it possible to check the ownership & permissions set on > /mnt/user/PrivateShare ? > > Is either apparmor or selinux running ? > > Rowland Thanks for the reply, I have included some responses
2024 Jan 19
1
Share access permission errors after upgrade from 4.12.14
On Tue, 16 Jan 2024 23:28:24 +0000 unraidster via samba <samba at lists.samba.org> wrote: > On Tuesday, 16 January 2024 at 09:46, Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > As far as I can see, unraid is based on slackware, so it should > > work. Is it possible to check the ownership & permissions set on > > /mnt/user/PrivateShare
2024 Jan 11
1
Share access permission errors after upgrade from 4.12.14
Hello, Issue Description After the upgrade of the Unraid server OS (unraid.net) from v6.9.2 to v6.12.6 (which upgrades the version of Samba from 4.12.14 to 4.17.12) access to shares stops working. Error Summary: [2024/01/07 21:52:43.357676, 0, pid=93992, effective(1278739538, 1278738945), real(1278739538, 0)] ../../source3/smbd/smb2_service.c:168(chdir_current_service) chdir_current_service:
2024 Jan 11
1
Share access permission errors after upgrade from 4.12.14
On Thu, 11 Jan 2024 08:53:38 +0000 unraidster via samba <samba at lists.samba.org> wrote: > Hello, > > Issue Description > After the upgrade of the Unraid server OS (unraid.net) from v6.9.2 to > v6.12.6 (which upgrades the version of Samba from 4.12.14 to 4.17.12) > access to shares stops working. > > Error Summary: > [2024/01/07 21:52:43.357676, 0, pid=93992,
2024 Jan 25
1
Share access permission errors after upgrade from 4.12.14
On Wednesday, 24 January 2024 at 20:45, Rowland Penny via samba <samba at lists.samba.org> wrote: > That is what I was looking for, the default 'idmap config' is set to > 'hash', which shouldn't be used. Especially as it says 'idmap_hash - DO > NOT USE THIS BACKEND' at the top of 'man idmap_hash'. I can understand > using it for existing
2024 Jan 19
1
Share access permission errors after upgrade from 4.12.14
On Fri, 19 Jan 2024 10:12:12 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Tue, 16 Jan 2024 23:28:24 +0000 > unraidster via samba <samba at lists.samba.org> wrote: > > > On Tuesday, 16 January 2024 at 09:46, Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > As far as I can see, unraid is based on
2024 Jan 24
1
Share access permission errors after upgrade from 4.12.14
On Wed, 24 Jan 2024 17:31:46 +0000 unraidster via samba <samba at lists.samba.org> wrote: > Hi, > > I assumed that the rearranged config you provided was for feedback, Yes, they were just comments, but unraid should really fix their Samba setup. > I > haven't made any changes to the configuration based on those > comments. I'll send a message to the Unraid
2007 Oct 24
1
setuid question
I've got a problem I hope someone can help with. We have a directory on a redhat box where we want anyone who creates a file (usually done with samba access) to have that file be created as if by a special "user" and group.. Now in the smb.privateshares config file we specify force user and force group.. However when we create a file in this directory it shows it being owned by the actual person who created it rather than the user specified in the force user = line of the configuration... I've tried to use chmod u+s but that doesn't seem t...
2010 Feb 06
2
(no subject)
Hi I Have a problem: I'm sharing ~600 folders on my samba server: [SHARE 192.168.0.20] comment = Private share for host 192.168.0.20 browseable = yes writable = yes path = /var/archives/USERS/192.168.0.20 public=yes hosts deny = 192.168. EXCEPT 192.168.0.20 [SHARE 192.168.0.21] comment = Private share for host 192.168.0.21 browseable = yes writable = yes path =
2024 Jan 23
1
Share access permission errors after upgrade from 4.12.14
Hi Rowland, Thanks for getting back to me, appreciate your time and help. Apologies for the long response, I have tried to include as much information as possible. On Friday, 19 January 2024 at 10:12, Rowland Penny via samba <samba at lists.samba.org> wrote: > Sorry to be so long in replying to this, but life got in the way. > > You initially had an incorrect smb.conf and you
2024 Jan 24
1
Share access permission errors after upgrade from 4.12.14
On Tue, 23 Jan 2024 21:47:27 +0000 unraidster via samba <samba at lists.samba.org> wrote: > Hi Rowland, > > Thanks for getting back to me, appreciate your time and help. > Apologies for the long response, I have tried to include as much > information as possible. > > On Friday, 19 January 2024 at 10:12, Rowland Penny via samba > <samba at lists.samba.org>