Web lists-archives.com

Re: [Samba] No write access on new shares until smbd is restarted




Here's the revised config:

[global]
log file=/var/log/samba/log.%m
log level=8
load printers=no
printing=bsd
printcap name=/dev/null

[2430_ram]
path=/data/fs/2430-ram
create mask=0775
directory mask=0775
read only=no
valid users=man_dude

Possibly relevant: the /data/fs/2430-ram folder has its mode set to 2775,
with the intent of children inheriting the group ownership. The folder's
group is a local group that also includes man_dude (the smb.conf valid
user).

Sorry for reposting - at this time, archives
<https://lists.samba.org/archive/samba/2018-June/thread.html> are showing
both my mails as replies to myself, not Rowland and I wasn't sure whether
he'll be notified. This is my first time using a mailing list.

On Fri, Jun 15, 2018 at 12:49 PM john doe via samba <samba@xxxxxxxxxxxxxxx>
wrote:

> On 6/15/2018 12:07 PM, Eugene Pankov via samba wrote:
> > [my previous mail didn't register as an answer in the list it seems]
> >
> > Yep - that's a standalone server. We're running the same configuration
> > (generated from a template) on over a hundred of servers, and just a few
> > manifest this "readonly until restart" behaviour.
> > I'm struggling to isolate any specific conditions that cause this at the
> > moment.
> > The users are added as Samba users.
> >
> >
> > On Thu, Jun 14, 2018 at 10:06 PM Rowland Penny via samba <
> > samba@xxxxxxxxxxxxxxx> wrote:
> >
> >> On Thu, 14 Jun 2018 20:14:13 +0200
> >> Eugene Pankov <e@xxxxxxxxxx> wrote:
> >>
> >>> Rowland,
> >>>
> >>> Sorry - here are the globals and share config:
> >>>
> >>> [global]
> >>> template shell=/bin/bash
> >>> log file=/var/log/samba/log.%m
> >>> log level=8
> >>> max log size=5000
> >>> passdb backend=tdbsam
> >>> load printers=no
> >>> printing=bsd
> >>> printcap name=/dev/null
> >>> map to guest=bad user
> >>>
> >>> [2430_ram]
> >>> path=/data/fs/2430-ram
> >>> guest ok=no
> >>> browseable=yes
> >>> create mask=0775
> >>> directory mask=0775
> >>> read only=no
> >>> follow symlinks=yes
> >>> wide links=no
> >>> valid users=man_dude
> >>> oplocks=yes
> >>> locking=yes
> >>>
> >>> The log from my first message is a user attempting and failing to
> >>> create a folder in the root of the share. The user is the one
> >>> specified in valid_users.
> >>>
> >>> The OS level permissions are correct - i.e. I can log in locally as
> >>> man_dude and create that folder on the FS.
> >>>
> >>
> >> OK, if I remove all the default lines, I am left with this:
> >>
> >> [global]
> >> template shell=/bin/bash
> >> log file=/var/log/samba/log.%m
> >> log level=8
> >> load printers=no
> >> printing=bsd
> >> printcap name=/dev/null
> >> map to guest=bad user
> >>
> >> [2430_ram]
> >> path=/data/fs/2430-ram
> >> create mask=0775
> >> directory mask=0775
> >> read only=no
> >> valid users=man_dude
> >>
> >> And you can probably remove 'map to guest=bad user' as well, because
> >> you do not have 'guest ok = yes' in the share.
> >>
> >> You could probably remove 'template shell=/bin/bash' as well, it isn't
> >> needed, your Unix has it own shell.
> >>
> >>  From your smb.conf, you are running samba as a standalone server, is
> >> this what you require ?
> >> If it is, have you added the Unix users as Samba users ?
> >> For more info, see here:
> >>
> >>
> https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server
> >>
>
> If you are resending your perfectly registered answer, it would be wise
> to also resend a revised copy of your smb.conf (see above rowland's
> answer).
>
> --
> John Doe
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba