Displaying 5 results from an estimated 5 matches for "2830016".
2017 Feb 08
2
Need help troubleshooting TCP thrashing, possible kernel bug?
...f.
------
[global]
server min protocol = NT1
server max protocol = SMB3
interfaces = 127.0.0.1 10.0.0.8
bind interfaces only = yes
encrypt passwords = yes
dns proxy = no
strict locking = no
oplocks = yes
deadtime = 15
max log size = 51200
max open files = 2830016
logging = file
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
getwd cache = yes
guest account = nobody
map to guest = Bad User
obey pam restrictions = yes
directory name cache size = 0
kernel change notify = no
panic...
2017 Feb 08
0
Need help troubleshooting TCP thrashing, possible kernel bug?
...gt; server max protocol = SMB3
> interfaces = 127.0.0.1 10.0.0.8
> bind interfaces only = yes
> encrypt passwords = yes
> dns proxy = no
> strict locking = no
> oplocks = yes
> deadtime = 15
> max log size = 51200
> max open files = 2830016
> logging = file
> load printers = no
> printing = bsd
> printcap name = /dev/null
> disable spoolss = yes
> getwd cache = yes
> guest account = nobody
> map to guest = Bad User
> obey pam restrictions = yes
> directory name cach...
2017 Feb 09
2
Need help troubleshooting TCP thrashing, possible kernel bug?
...interfaces = 127.0.0.1 10.0.0.8
> > bind interfaces only = yes
> > encrypt passwords = yes
> > dns proxy = no
> > strict locking = no
> > oplocks = yes
> > deadtime = 15
> > max log size = 51200
> > max open files = 2830016
> > logging = file
> > load printers = no
> > printing = bsd
> > printcap name = /dev/null
> > disable spoolss = yes
> > getwd cache = yes
> > guest account = nobody
> > map to guest = Bad User
> > obey pam re...
2017 Feb 08
2
Need help troubleshooting TCP thrashing, possible kernel bug?
I have a FreeNAS 9.3 server running Samba Version 4.3.6 and a bunch of
Windows and Linux clients. Everything's been running fine for a while and
nothing changed on the server.
Recently (Jan 27th) some of the Archlinux clients updated from a 4.8.x
kernel to a 4.9.x kernel. Again, things ran fine. Then on Jan 30th around
2am the Archlinux clients using 4.9.x kernels and utilizing mount.cifs to
2017 Feb 09
0
Need help troubleshooting TCP thrashing, possible kernel bug?
...0.8
>> > bind interfaces only = yes
>> > encrypt passwords = yes
>> > dns proxy = no
>> > strict locking = no
>> > oplocks = yes
>> > deadtime = 15
>> > max log size = 51200
>> > max open files = 2830016
>> > logging = file
>> > load printers = no
>> > printing = bsd
>> > printcap name = /dev/null
>> > disable spoolss = yes
>> > getwd cache = yes
>> > guest account = nobody
>> > map to guest = Ba...