The pic seems missing. Here's the info:
PID Username Group Machine
Protocol Version Encryption Signing
----------------------------------------------------------------------------------------------------------------------------------------
112451 3000243 3000019 8.22.32.200 (ipv4:8.22.32.200:51106)
SMB2_10 - HMAC-SHA256
122045 3000245 3000019 8.22.32.187 (ipv4:8.22.32.187:51657)
SMB2_10 - HMAC-SHA256
122751 3000245 3000019 8.22.32.187 (ipv4:8.22.32.187:52258)
SMB2_10 - HMAC-SHA256
112844 3000243 3000019 8.22.32.200 (ipv4:8.22.32.200:51549)
SMB2_10 - HMAC-SHA256
28794 3000242 3000019 8.22.32.190 (ipv4:8.22.32.190:54824)
SMB2_10 - HMAC-SHA256
Service pid Machine Connected at Encryption
Signing
---------------------------------------------------------------------------------------------
IPC$ 112844 8.22.32.200 Thu Sep 27 02:52:11 PM 2018 CST -
HMAC-SHA256
IPC$ 28794 8.22.32.190 Thu Sep 27 03:06:30 PM 2018 CST -
HMAC-SHA256
IPC$ 122045 8.22.32.187 Thu Sep 27 02:54:42 PM 2018 CST -
HMAC-SHA256
IPC$ 112451 8.22.32.200 Thu Sep 27 02:52:03 PM 2018 CST -
HMAC-SHA256
IPC$ 122751 8.22.32.187 Thu Sep 27 02:54:50 PM 2018 CST -
HMAC-SHA256
No locked files
C9C09AF2_HDC1:/var/lib/dhcp/db # ping 8.22.32.200
PING 8.22.32.200 (8.22.32.200) 56(84) bytes of data.
^C
--- 8.22.32.200 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms
C9C09AF2_HDC1:/var/lib/dhcp/db # ps -ef|grep smbd
root 50238 50225 0 Sep26 ? 00:00:04 /usr/sbin/smbd -D
--option=server role check:inhibit=yes --foreground
root 51078 50238 0 Sep26 ? 00:00:00 /usr/sbin/smbd -D
--option=server role check:inhibit=yes --foreground
root 51079 50238 0 Sep26 ? 00:00:00 /usr/sbin/smbd -D
--option=server role check:inhibit=yes --foreground
root 76594 18795 0 15:20 pts/1 00:00:00 grep smbd
root 112451 50238 0 14:51 ? 00:00:00 /usr/sbin/smbd -D
--option=server role check:inhibit=yes --foreground
root 112844 50238 0 14:52 ? 00:00:00 /usr/sbin/smbd -D
--option=server role check:inhibit=yes --foreground
root 122045 50238 0 14:54 ? 00:00:00 /usr/sbin/smbd -D
--option=server role check:inhibit=yes --foreground
root 122751 50238 0 14:54 ? 00:00:00 /usr/sbin/smbd -D
--option=server role check:inhibit=yes --foreground>
>Recently I find the smbd process does not close itself even it is invalid,
or it close too slow. As the screenshot shows, the connection 112451 and 112844
were created because of the client 8.22.32.200 at Sep 27 02:52:11. And it still
exist now at 15:30. But clearly 8.22.32.200 is not available any more. This VM
was disabled by me early. The samba version is 4.5.16.
>
>Does the smbd process not auto quit? If so, when I have many connections, my
server can’t afford definitely. I find an answer to set auto close connection in
http://www.spectrumscale.org/pipermail/gpfsug-discuss/2017-October/003975.html,
the parameter:
>deadtime=10
>and TCP level:
>TCP_NODELAY SO_KEEPALIVE TCP_KEEPCNT=4 TCP_KEEPIDLE=240 TCP_KEEPINTVL=15
>But I didn’t find any description about these parameters. So I want to ask
which is the right way to prevent this issue? And what is the effect?
>--
>To unsubscribe from this list go to the following URL and read the
>instructions: https://lists.samba.org/mailman/options/samba