Displaying 6 results from an estimated 6 matches for "force_group_nam".
Did you mean:
force_group_name
2017 Jan 07
2
frequent core dumps (invalid lock_order?)
...= mkdir rename unlink rmdir pwrite
full_audit:failure = none
full_audit:facility = local7
full_audit:priority = NOTICE
# Example share
[SHARE_NAME]
access based share enum = yes
browseable = yes
comment = <COMMENT>
create mask = 0660
directory mask = 2770
force group = <FORCE_GROUP_NAME>
path = <PATH>
guest ok = no
public = no
writeable = yes
valid users = +GROUP_1 +GROUP_2
vfs objects = full_audit acl_tdb
full_audit:prefix = %u|%I|%m|%S
full_audit:success = mkdir rename unlink rmdir pwrite
full_audit:failure = none
full_audit:facility = local7
full_audit:priority = NOTI...
2017 Jan 07
3
frequent core dumps (invalid lock_order?)
> Lets hold off with logs, do you know that if you remove everything
> that should be in a share from the [global] part of your smb.conf, you
> get left with just '[global]’.
The share actually comes from an include file. I made it look like it’s part of the main config for simplicity.
> It also doesn't help that everything
> that is in [global] is also in the share.
It’s
2017 Jan 07
0
frequent core dumps (invalid lock_order?)
...ure = none
> full_audit:facility = local7
> full_audit:priority = NOTICE
>
> # Example share
> [SHARE_NAME]
> access based share enum = yes
> browseable = yes
> comment = <COMMENT>
> create mask = 0660
> directory mask = 2770
> force group = <FORCE_GROUP_NAME>
> path = <PATH>
> guest ok = no
> public = no
> writeable = yes
> valid users = +GROUP_1 +GROUP_2
> vfs objects = full_audit acl_tdb
> full_audit:prefix = %u|%I|%m|%S
> full_audit:success = mkdir rename unlink rmdir pwrite
> full_audit:failure = none
> full_...
2017 Jan 09
0
frequent core dumps (invalid lock_order?)
...> 2. Example share from /etc/samba/local_shares.conf
> ===================================================
>
> [SHARE_NAME]
> access based share enum = yes
> browseable = yes
> comment = <COMMENT>
> create mask = 0660
> directory mask = 2770
> force group = <FORCE_GROUP_NAME>
> path = <PATH>
> guest ok = no
> public = no
> writeable = yes
> valid users = +GROUP_1 +GROUP_2
> vfs objects = full_audit acl_tdb
> full_audit:prefix = %u|%I|%m|%S
> full_audit:success = mkdir rename unlink rmdir pwrite
> full_audit:failure = none
> full_...
2017 Jan 09
2
frequent core dumps (invalid lock_order?)
..._shares.conf
> > ===================================================
> >
> > [SHARE_NAME]
> > access based share enum = yes
> > browseable = yes
> > comment = <COMMENT>
> > create mask = 0660
> > directory mask = 2770
> > force group = <FORCE_GROUP_NAME>
> > path = <PATH>
> > guest ok = no
> > public = no
> > writeable = yes
> > valid users = +GROUP_1 +GROUP_2
> > vfs objects = full_audit acl_tdb
> > full_audit:prefix = %u|%I|%m|%S
> > full_audit:success = mkdir rename unlink rmdir pwrite
&...
2017 Jan 07
2
frequent core dumps (invalid lock_order?)
Hi,
I'm hoping somebody can point me in the right direction. My samba version
is samba-4.2.10-6.2.el7_2.x86_64. I have lots of daily core dumps (~20 on
each machine daily) and I have no clear idea why. I'm including the stack
trace below. It looks like the problem is related to "invalid lock_order".
Any ideas?
Thanks,
Sergei
#0 0x00007fc5a34945f7 in raise () from