Bug 36165 - samba/max_open_files doesn't apply.
samba/max_open_files doesn't apply.
Status: RESOLVED DUPLICATE of bug 34514
Product: UCS
Classification: Unclassified
Component: Samba
UCS 3.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-13 18:40 CEST by Arvid Requate
Modified: 2014-10-14 09:29 CEST (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2014-10-13 18:40:27 CEST
The UCR settings for

 security/limits/user/*/soft/nofile and security/limits/user/*/hard/nofile

are not applied to the root user (see Bug 27618).

This causes issues in Samba where the samba/max_open_files setting cannot go beyond the system limits.

We should also set

ucr set security/limits/user/root/soft/nofile=32828 \
        security/limits/user/root/hard/nofile=32828


I don't know if this in enough, in my samba4 UCS 4.0MS2 Master the main process still was limited to 1024, but the forked smbds showed 32828. Maybe we need to put something like  "ulimit -n $samba_max_open_files"  into the init scripts.

We may also want to consider Bug 34514 when putting this one on the agenda.
Comment 1 Stefan Gohmann univentionstaff 2014-10-14 08:59:51 CEST

*** This bug has been marked as a duplicate of bug 34514 ***