TCP socket vs. local Unix socket

I have a few questions about TCP sockets and local sockets.

FYI, I am using ClamAV 1.0.7 packages provided by el9 EPEL.

If clamd is configured with both a TCP socket and a local Unix socket, 
which does clamdscan choose first?

Which does clamonacc choose first?

Are there clamd commands that only apply to TCP socket connections?  If 
yes, what are they?  This is particularly important for me to know (to 
help me understand client/server communications) with regards to 
clamdscan and clamonacc accessing a remote (centralized) clamd.

Are there clamd commands that only apply to local Unix socket 
connections?  If yes, what are they?

In brief, I am planning a large ClamAV deployment with varying 
requirements.  A few of the file servers will have their own instance of 
clamd running locally.  The remaining file servers will utilize (via 
clamdscan and/or clamonacc) a remote TCP clamd daemon.

_______________________________________________

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat