Dear alpha-osf-managers,
we are using Network Associates' Virus Scan for Windows NT 3.2.0 (also
the hot fix upgrading the scanning engine to 3.2.1) on a Windows NT 4.0
SP3 machine to scan files on shares offered by a machine running Digital
UNIX 4.0D and Advanced Server for Digital UNIX (ASDU) 4.0A.
We are observing the following interoperability problem:
All files scanned by Vscan NT not only get their "date of last access"
updated (as seen by "ls -ltu") but also their "date of last inode
modification" (as seen by "ls -ltc").
The "date of last file modification" (as seen by "ls -lt") is -as
expected- unaffected.
Why should I bother? Because the "date of last inode modification" makes
files elibigle for backup, so that incremental backups "blow up".
Although we have the workaround to create special shares with R/O access
for Administrators, virus scans still make the alerter service nervous,
reporting thousands of access-denied errors in the audit trail.
The problem doesn't exist with Win95 and Vscan for Win95 V3.1.9
I wonder if others observe similar problems.
Regards,
Thomas Meyer, EDV-Systemadministrator
email: Thomas.Meyer at dla-marbach.de
smail: Deutsches Literaturarchiv Marbach
Schillerhoehe 8-10
D-71672 Marbach
Telefon: +49-7144-848-141
Fax: ...-387
WWW:
http://www.dla-marbach.de
Received on Wed Nov 25 1998 - 09:14:16 NZDT