Hi there, On Fri, 9 Jul 2021, Michael Wang wrote:
I discovered the problem I had was due to the use of the *Universal Naming Convention (UNC) Path*, "\\xx-x411\clamav". Even on the same server where "\\xx-x411\clamav" and "D:\clamav" are the same, the behaviors are different as shown below.
Well, nothing about Windows really surprises me any more. :/
... I wanted to use the UNC path because I want to share the database across the servers. ...
I can see the sense in wanting to use a uniform way to describe the locations of resources, but even if you have several servers accessing the ClamAV database you will only want one of them to run freshclam so the only thing you'll lose with the DOS-style paths is consistency in the various pathnames. Of course this will all be in explained in the site documentation which you will produce. :) Maybe this should get a mention in the ClamAV Bugzilla? -- 73, Ged. _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
