Release notes for Symantec AntiVirus for Linux 1.0x

Article:TECH103599  |  Created: 2007-01-03  |  Updated: 2012-09-12  |  Article URL http://www.symantec.com/docs/TECH103599
Article Type
Technical Solution



Issue



This article documents the changes and fixes in each update to Symantec AntiVirus for Linux 1.0x (SAV for Linux, or SAVFL).

 


Solution



As updates to Symantec AntiVirus for Linux are released, they are added to this document. The sections are added in chronological order, with the most recent additions at the top.

 

Symantec AntiVirus for Linux 1.0 Maintenance Release 14 (MR14)

Symantec AntiVirus for Linux 1.0 MR14 adds support for a number of kernels. For the complete list of added kernels, please refer to the System requirements for Symantec AntiVirus for Linux 1.0.

Symantec AntiVirus for Linux 1.0 MR14 also includes the following changes:

Scheduled scan exclusions not removed when using GRC.DAT
Fix ID:  2674753
Symptom: Scheduled scan exclusions not removed from registry after removing from GRC.DAT
Solution:   We will remove all of the Scheduled Scans settings every time when input GRC.DAT files which contain Scheduled Scans setting information.
 
Scan engine version displays "0.0.0.0" after May15 
Fix ID:  2796660
Symptom: GUI and `sav info –e’ display wrong version of scan engine
Solution:   In the AV engine we uses a 32bit long type to hold the version information, but when the version number has increased beyond 255, for example, from 121.1.0.254 to 121.1.0.263. SAV can no longer display the version number because the algorithm only supports up to 255. So extend the version type from 32bit to 64bit.
 
Segfault in Optio label printing software when SAV for Linux AP modules are loaded
Fix ID:  2688115
Symptom: Segmentation fault while executing /h/silverstream/optio/bin/ocserver with AP enabled
Solution:   The mmap system call has changed the parameter, so our kernel module function should also be changed.

 Additional Notes:

Improved support for Japanese versions of Linux
Details: SAVFL is now supported in English on the Japanese versions of supported Linux operating systems.

The shield icon is not transparent in Ubuntu 11.x
Details: The background of the SAVFL shield icon in the notification area is not transparent in Ubuntu 11.x. 

The shield icon does not show up after upgrading
Details: If you upgrade the SAVUI package from MR9 or earlier releases, the shield icon may not appear in the notification area.  To work around this issue, run the following command: 
/path/to/symantec_antivirus/savtray & 
This step only needs to be performed once.  Upgrades from MR10 will not have this issue.

Uninstall SAVFL first on Novell/SUSE series
Details: In MR8, we made some changes to the startup/shutdown sequence of the SAV daemons (symcfgd and rtvscand). These changes will not take effect if you upgrade from an older release instead of performing a fresh installation.  To make these changes to the startup and shutdown sequence after upgrading from a previous release, run the following command as root:  
# insserv -d symcfgd  rtvscand

Auto-Protect is not supported for use on SUSE Linux Enterprise Server 11 (x86_64) with the kernel version 2.6.27.19-5
Details: Loading the Auto-Protect kernel module (symev) on SUSE Linux Enterprise Server 11 (x86_64) with the kernel version 2.6.27.19-5 causes the operating system to hang (stop responding) due to an operating system defect. If you want to use the Auto-Protect feature on SUSE Linux Enterprise Server 11 (x86_64), you must upgrade your kernel to version 2.6.27.21-0.1.2 or later. For more information, please refer to bug 439348 in the Novell Bugzilla.

 

Symantec AntiVirus for Linux 1.0 Maintenance Release 13 (MR13)
Symantec AntiVirus for Linux 1.0 MR13 adds support for a number of kernels. For the complete list of added kernels, please refer to the System requirements for Symantec AntiVirus for Linux 1.0.

Symantec AntiVirus for Linux 1.0 MR13 also includes the following changes:

SAVFL delete the files other than us under /tmp
Fix ID
:  2117425, 2283044
Symptom: Java Liveupdate deletes files under /tmp which don’t belong to itself.
Solution:   Exclude those files from the list to delete.

`antivirus scan start` could cause node hang when antivirus decomposes certain zip structure such as nesting zip/tar-z etc
Fix ID
:  2298820
Symptom: Scanning big compressed file cause system hang
Solution:  Change the priority of read-write lock from write-first to read-first, that hold by scan threads when scanning files.

Scheduled scan exclusions are not removed from when GRC.DAT to administer clients
Fix ID
:  2586840
Symptom: Omission of a previous scheduled scan exclusion is not being honored by the SAVFL client.
Solution:  Check the exclusion item information every time when trying to handle the scheduled scan.

Java LiveUpdate is not honoring missed events
Fix ID
:  2102785
Symptom: JLU does not honor missed events when the scheduled liveupdate has missed events enabled.
Solution:  Change the program logic to check the missed events.

Adding message for liveupdate running in GUI
Fix ID
:  2616468
Symptom: The Liveupdate button is grayed, and some users think it's an error. A message like "Liveupdate is running" would be helpful.
Solution:  The Liveupdate button is grayed with text “Liveupdate is running” while live updating.

 

Symantec AntiVirus for Linux 1.0 Maintenance Release 12 (MR12)
Symantec AntiVirus for Linux 1.0 MR12 adds support for a number of kernels, including Red Hat 5.7 and 6.1. For the full list of added kernels, read the section on MR12 in System requirements for Symantec AntiVirus for Linux 1.0.

Symantec AntiVirus for Linux 1.0 MR12 also includes the following changes:

New command line options:

1. 'sav scheduledscan -p|--stop scan_id' stops a scheduled scan that is in progress.

2. 'sav manualscan -c|--clscan [pathname|-]' initiates a synchronous manual scan that does not return control to the command prompt until the scan is complete.

3. 'sav quarantine -d|--delete/-r|--restore/-p|--repair/-i|--info "*"' deletes, restores, repairs, or provides detailed information about all of the quarantined items, respectively.

Change to default logging levels
The default logging level of the daemons has been changed from DEBUG to INFO to enhance performance. To change the logging levels, refer to the rtvscand(8) man page.


Symantec AntiVirus for Linux 1.0 Maintenance Release 11 (MR11)
Symantec AntiVirus for Linux 1.0 MR11 adds support for a number of kernels. For the full list of added kernels, read the section on MR11 in System requirements for Symantec AntiVirus for Linux 1.0.

Symantec AntiVirus for Linux 1.0 MR11 also includes the following fixes:

System hang on Novell OES2
Fix ID: 2199981
Symptom: The system went into a hang status with SAVFL running for some time.
Solution: Add reference number process to avoid system hang. Expand the protected range of spinlock when more than one process synchronously accesses the kernel module scan list.

Unexpected reboot by RTVSCAND
Fix ID: 2333486
Symptom: Unexpected reboot occurred on Red Hat Enterprise Linux 5.
Solution: Add reference number checking process to avoid system hang.

SAV for Linux Reporter is now included in MR11
Details: The Reporter was first released as an add-on to MR10. It is now included in MR11. For more information, read this knowledge base article: http://www.symantec.com/business/support/index?page=content&id=DOC3474


Symantec AntiVirus for Linux 1.0 Maintenance Release 10 (MR10)
Symantec AntiVirus for Linux 1.0 MR10 adds support for a number of kernels. For the full list of added kernels, read the section on MR10 in System requirements for Symantec AntiVirus for Linux 1.0.

Symantec AntiVirus for Linux 1.0 MR10 also includes the following fixes:

The /etc/symantec directory is not removed on uninstall
Fix ID: 1988507
Symptom: Customers reported that the /etc/symantec directory (where the configuration database is stored) was not removed during the uninstall process. This could cause a problem with reinstall.
Solution: The contents of the /etc/symantec directory are now removed with the exception of the NLS subdirectory. By design, /etc/symantec/NLS is not removed.

Repair from quarantine failed when using an asterisk in quotes
Fix ID: 2067752
Symptom: The command sav quarantine –p “*” failed with the error “Unable to repair file.”
Solution: This command now works correctly.

Add support for Fedora 13
Fix ID: 2003639
Symptom: Fedora 13 was not supported.
Solution: Added support for Fedora 13 (both 32-bit and 64-bit).

Add support for RedHat Enterprise Linux 5.5
Fix ID: 1959100
Symptom: RedHat Enterprise Linux 5.5 was not supported.
Solution: Added support for RHEL 5.5 (both 32-bit and 64-bit).

Add support for SuSE Linux Enterprise Server / Desktop 11 SP1
Fix ID: 1959111
Symptom: SuSE Linux Enterprise Server / Desktop 11 SP1 was not supported.
Solution: Added support for SuSE Linux Enterprise Server / Desktop 11 SP1 (both 32-bit and 64-bit).

Add support for Ubuntu 10.04 Desktop / Server
Fix ID: 2003645
Symptom: Ubuntu 10.04 Desktop / Server was not supported.
Solution: Added support for Ubuntu 10.04 Desktop / Server (32-bit only).

Additional Notes:

Improved support for Japanese versions of Linux
Details: SAV for Linux is now supported in English on the Japanese versions of supported Linux operating systems.

New Knowledge Base Articles
Details: Two Symantec Knowledge Base articles have been added for this release.

SAV for Linux Installation Checklist:
http://service1.symantec.com/support/ent-security.nsf/docid/2010062217010148

Will SAV for Linux work with my kernel version?
http://service1.symantec.com/support/ent-security.nsf/docid/2010052514055548

Red Hat Enterprise Linux version 6
Details: At the time of the MR10 release, Red Hat Enterprise Linux version 6 was still in beta form. There is no kernel module for RHEL version 6 in the MR10 release, but the open source code package has been updated to be compatible with RHEL version 6 beta 2.

The shield icon is not transparent in Ubuntu 10.04
Details: The background of the SAV for Linux shield icon in the notification area is not transparent in Ubuntu 10.04. In other Ubuntu versions, it is transparent.

The shield icon does not show up after upgrading
Details: If you upgrade the SAVUI package from MR9 or earlier releases, the shield icon may not appear in the notification area. To work around this issue, run the following command:

/path/to/symantec_antivirus/savtray& 

This step only needs to be performed once. Upgrades from MR10 will not have this issue.

Uninstall SAVFL first on Novell/SUSE series
Details: In MR8, we made some changes to the startup/shutdown sequence of the SAV daemons (symcfgd and rtvscand). These changes will not take effect if you upgrade from an older release instead of performing a fresh installation. To make these changes to the startup and shutdown sequence after upgrading from a previous release, run the following command as root:

# insserv -d symcfgd rtvscand

Auto-Protect is not supported for use on SUSE Linux Enterprise Server 11 (x86_64) with the kernel version 2.6.27.19-5
Details: Loading the Auto-Protect kernel module (symev) on SUSE Linux Enterprise Server 11 (x86_64) with the kernel version 2.6.27.19-5 causes the operating system to hang (stop responding) due to an operating system defect. If you want to use the Auto-Protect feature on SUSE Linux Enterprise Server 11 (x86_64), you must upgrade your kernel to version 2.6.27.21-0.1.2 or later. For more information, please refer to bug 439348 in the Novell Bugzilla.


Symantec AntiVirus for Linux 1.0 Maintenance Release 9 (MR9)
Symantec AntiVirus for Linux 1.0 MR9 adds support for a number of kernels. For the full list of added kernels, read the section on MR9 in System requirements for Symantec AntiVirus for Linux 1.0.

Symantec AntiVirus for Linux 1.0 MR9 also includes the following fixes:

Lines that are too long in the /etc/group file cause the installation process to fail
Fix ID: 1637025
Symptom: Customers reported that lines that are too long in the /etc/group file cause the navdefutil tool to fail to work properly.
Solution: Changed the way that the /etc/group file is handled.

Scanning a symbolic link to a file four levels above causes SAVFL to exhaust CPU
Fix ID: 1780312
Symptom: Customers reported that scanning a symbolic link to a file four levels above causes SAV for Linux to exhaust CPU.
Solution: Changed the way that the scan path is handled.

Add support for RedHat Enterprise Linux 5 Update 4
Fix ID: 1505387
Symptom: RedHat Enterprise Linux 5 Update 4 was not supported.
Solution: Added support for both 32-bit and 64-bit versions of RedHat Enterprise Linux 5 Update 4.

Add support for Fedora 12
Fix ID: 1885418
Symptom: Fedora 12 was not supported.
Solution: Added support for Fedora 12 (32-bit kernel only).

Add support for RedHat Enterprise Linux 4 Update 8
Fix ID: 1885411
Symptom: RedHat Enterprise Linux 4 Update 8 was not supported.
Solution: Added support for both 32-bit and 64-bit versions of RedHat Enterprise Linux 4 Update 8.

Add support for SuSE Linux Enterprise Server 9 Service pack 4
Fix ID: 1505380
Symptom: The latest kernels of SuSE Linux Enterprise Server 9 Service pack 4 were not supported.
Solution: Added support for both 32-bit and 64-bit versions of the latest kernels of SuSE Linux Enterprise Server 9 Service pack 4.

Add support for SuSE Linux Enterprise Server / Desktop 10 Service pack 3
Fix ID: 1505379
Symptom: SuSE Linux Enterprise Server / Desktop 10 Service pack 3 was not supported.
Solution: Added support for both 32-bit and 64-bit versions of SuSE Linux Enterprise Server / Desktop 10 Service pack 3.

Add support for SuSE Linux Enterprise Server / Desktop 11
Fix ID: 1505377
Symptom: SuSE Linux Enterprise Server / Desktop 11 was not supported.
Solution: Added support for both 32-bit and 64-bit versions of SuSE Linux Enterprise Server / Desktop 11.

Add support for Ubuntu 9.10 Desktop / Server
Fix ID: 1885420
Symptom: Ubuntu 9.10 Desktop / Server was not supported.
Solution: Added support for Ubuntu 9.10 Desktop / Server (32-bit kernel only).

Add support for Debian 5.0.3
Fix ID: 1715970
Symptom: Debian 5.0.3 was not supported.
Solution: Added support for both 32-bit and 64-bit versions of Debian 5.0.3.

Additional Notes:

Uninstall SAVFL first on Novell/SUSE series
Details: In MR8, we made some changes to the startup/shutdown sequence of the SAV daemons (symcfgd and rtvscand). These changes will not take effect if you upgrade from an older release instead of performing a fresh installation. To affect these changes to the startup and shutdown sequence after having upgraded from a previous release, run the following command as root:

# insserv -d symcfgd rtvscand

Auto-Protect is not supported for use on SUSE Linux Enterprise Server 11 (x86_64) with the kernel version 2.6.27.19-5
Details: Loading the Auto-Protect kernel module (symev) on SUSE Linux Enterprise Server 11 (x86_64) with kernel version 2.6.27.19-5 causes the operating system to hang (stop responding) due to an operating system defect. If you want to use the Auto-Protect feature on SUSE Linux Enterprise Server 11 (x86_64), you must upgrade your kernel to version 2.6.27.21-0.1.2 or later. For more information, please refer to bug 439348 in the Novell Bugzilla.

Savtray icon does not show up after upgrading
Details: If you perform an upgrade on the SAVUI package instead of a clean installation, the Savtray icon may not appear after the upgrade. It can be started manually with the command "/path/to/symantec_antivirus/savtray&". This step only needs to be performed once.


Symantec AntiVirus for Linux 1.0 Maintenance Release 8 (MR8)
Symantec AntiVirus for Linux 1.0 MR8 adds support for a number of kernels. For the full list of added kernels, read the section on MR 8 in System requirements for Symantec AntiVirus for Linux 1.0.

Symantec AntiVirus for Linux 1.0 MR8 also includes the following fixes:

Partially open the Auto-Protect kernel modules source
Fix ID: 1505397
Symptom: The Auto-Protect kernel modules source is not open.
Solution: Based on requests from customers, Symantec is partially opening the Auto-Protect kernel modules source code. Symantec will provide the relevant library files so that customers can compile the Auto-Protect kernel modules themselves. For more information refer to README file in the source tarball.

Change all the qt_*path configurations to /usr/lib
Fix ID: 1664496
Symptom: Customers reported that SAV for Linux is looking for mount point of a /home directory.
Solution: Recompiled the source and moved the QT configuration path to /usr/lib.

OES2 SP1 server in cluster environment hangs at boot
Fix ID: 1544883
Symptom: Customers reported that OES2 SP1 server in cluster environment hangs at boot after installation of SAVFL.
Solution: Adjusted the startup order of Symantec AntiVirus for Linux daemons to fix this issue.

Add support to RedHat Enterprise Linux 5 Update 3
Fix ID: 1505386
Symptom: RedHat Enterprise Linux 5 Update 3 was not supported.
Solution: Added the support for both 32-bit and 64-bit of RedHat Enterprise Linux 5 Update 3.

Add support for Fedora 10
Fix ID: 1505400
Symptom: Fedora 10 was not supported.
Solution: Added support for Fedora 10 (32-bit kernel only). The supported kernel version for Fedora 10 is 2.6.27.5-117.

Memory leak issue
Fix ID: 1404268
Symptom: Symantec AntiVirus for Linux exhausted system memory after long-term running.
Solution: Fixed the AV daemon memory leaks and the slab-32 memory leak in the autoprotect kernel module.

Additional Notes:

Supported kernel version of Fedora 10
Details: The only supported kernel version for Fedora 10 is 2.6.27.5-117. If you need to use Symantec AntiVirus for Linux on some other kernel versions, please try to compile with ap-kernelmodule tarball.

Uninstall Symantec AntiVirus for Linux first on Novell/SUSE series
Details: In MR8, we made some changes to the startup/shutdown sequence of the Symantec AntiVirus daemons (symcfgd and rtvscand). These changes will not take effect if you upgrade from an older release instead of performing a fresh installation. To affect these changes to the startup and shutdown sequence after having upgraded from a previous release, run the following command as root:

# insserv -d symcfgd rtvscand


Symantec AntiVirus for Linux 1.0 Maintenance Release 7 (MR7)
Symantec AntiVirus for Linux 1.0 MR7 adds support for a number of kernels. For the full list of added kernels, read the section on MR7 in System requirements for Symantec AntiVirus for Linux 1.0.

Customized installation path for .rpm package
Fix ID: 1301696
Symptom: Symantec AntiVirus for Linux installation path is hardcoded to "/opt/Symantec" and cannot be customized.
Solution: Default installation path can be changed by 'rpm -i --prefix <custom path>sav*.rpm'. Make sure that all .rpm packages use the same path. Note that .deb packages and legacy .rpm packages do not support this feature.

Xen Compatibility
Fix ID: 1380107
Symptom: Symantec AntiVirus for Linux is not compatible with –xenU kernels
Solution: Symantec AntiVirus for Linux supports -xen kernels of fully virtualized and paravirtualized guest operating systems. It does not need any specific configurations to install or load autoprotect modules. The supported -xen kernels are explicitly listed in System requirements for Symantec AntiVirus for Linux 1.0. Other variants, such as -xenU, are not supported by the product.

Issues enabling SELinux
Fix ID: 1380113
Symptom: Some error information will be recorded when SELinux is enabled during the installation.
Solution: Resolved error logging issues when SELinux is enabled during the installation.

Update to Trolltech Qt Library
Fix ID: 839072
Symptom: N/A
Solution: Updated the Trolltech Qt Library


Symantec AntiVirus for Linux 1.0 Maintenance Release 6 (MR6)
Symantec AntiVirus for Linux 1.0 MR6 adds support for a number of kernels. For the full list of added kernels, read the section on MR6 in System requirements for Symantec AntiVirus for Linux 1.0.

Symantec Anti-Virus for Linux fixes:

Need ability to stop scheduled scans
Fix ID: 492362
Symptom: Only manual scans can be stopped. The mechanism needs to be generalized to be able to stop any type of walker scan, including scheduled scans.
Solution: Command added: "sav -p | --stop <ID>" to stop scheduled scan. By "sav -n <ID>" or "sav -l", status is "Aborted".

Auto-Protect needs to protect files when accessed via NFSv4
Fix ID: 1041591
Symptom: Symantec AntiVirus for Linux does not hook the NFSv4 service, so it does not protect file accesses by NFSv4 clients.
Solution: Add NFSv4 Auto-Protect support.

Adding Synchronous command line / manual scan option
Fix ID: 1165752
Symptom: Symantec AntiVirus for Linux manual scan is asynchronous. To determine if a manual scan is finished, customers can only check the log records.
Solution: Add synchronous verbose manual scan option: sav –c | --clscan to prevent command prompt from returning.

Ubuntu normal users should be able to do manual scan and to get Auto-Protect scan alert
Fix ID: 1194858
Symptom: Ubuntu normal users cannot launch manual scans or get Auto-Protect alert windows; only root has the privileges.
Solution: Ubuntu normal users scan manually with the "sudo" command, and can get Auto-Protect alert windows.

Default CustomTaskDefaults settings
Fix ID: 1194859
Symptom: Default CustomTaskDefaults registry settings for manual scan and Auto-Protect are not aligned.
Solution: Keep the default CustomTaskDefaults registry settings the same.

Symantec AntiVirus for Linux quarantine command wildcard enhancement
Fix ID: 1216590
Symptom: sav quarantine command only deletes one ID item each time.
Solution: Add enhancement to support wildcard, e.g. sav quarantine -d "*" to delete all quarantined items.

Intelligent savap and savap- x64 rpm installation enhancement
Fix ID: 1301689
Symptom: No prejudgment on 64bit OS for savap and savap-x64 rpm packages.
Solution: 32bit savap rpm package will not be installed on x86_64 architecture with prompt errors.


Symantec AntiVirus for Linux 1.0 Maintenance Release 5

Symantec AntiVirus for Linux 1.0 MR5 adds support for a number of kernels. For the full list of added kernels, read the section on MR5 in System requirements for Symantec AntiVirus for Linux 1.0.

Symantec AntiVirus for Linux 1.0 MR5 also adds Novell Yes certification on SuSE Linux.


Symantec AntiVirus for Linux 1.0 Maintenance Release 4 build 39

Symantec AntiVirus for Linux 1.0 MR4 build 39 adds support for a number of kernels. For the full list of added kernels, read the section on MR4 build 39 in System requirements for Symantec AntiVirus for Linux 1.0.

Symantec AntiVirus for Linux 1.0 MR4 build 39 also includes the following fixes:
 

 

 

    Scheduling LiveUpdate fails to update virus definitions
    Fix ID: 842683
    Symptom: Schedule LiveUpdate to run daily. Virus definitions are not updated, but Symantec AntiVirus reports "Virus definitions are current."
    Solution: Problem fixed. LiveUpdate now updates the virus definitions to the latest version.

    Symantec AntiVirus for Linux crashes or fails to scan on NFS server
    Fix ID: 998104
    Symptom: When a remote system attempts to create a file on a read-only export, the write succeeds but the file is never scanned. The computer may stop responding.
    Solution: NFS server scans now work correctly.

    Java LiveUpdate does not work correctly when run from within Symantec AntiVirus
    Fix ID: 842686
    Symptom: When you run Java LiveUpdate from within Symantec AntiVirus on Red Hat Enterprise Linux 3, the definitions are downloaded but are not applied.
    Solution: Definitions are now applied correctly.

    Symantec AntiVirus does not apply new definitions from Java LiveUpdate on Red Hat Enterprise Linux 4
    Fix ID: 1000736
    Symptom: When you run Java LiveUpdate on Red Hat Enterprise Linux 4, the definitions are downloaded but are not always applied.
    Solution: Definitions are now applied correctly.

    Scan changes ctime of scanned files
    Fix ID: 1116255
    Symptom: A manual or scheduled scan modifies the ctime of the files it scans, which triggers an unwanted backup.
    Solution: Scans no longer modify the ctime on files.

    Change default logging setting for RTVSCAND from "DEBUG" to "INFO"
    Fix ID: 1162311
    Symptom: The default logging parameter for RTVSCAND, which is "DEBUG," may be resource intensive.
    Solution: Changed the default to "INFO". RTVSCAND default logging parameter now starts with arguments '-l info'.

    Command-line installation does not support wildcards
    Fix ID: 1166476
    Symptom: Command-line installation of Symantec AntiVirus for Linux does not support wildcards.
    Solution: Wildcard support added to install the product via the command line using RPM command.

    Touching ClearCase dynamic view objects causes a kernel trap/machine hang
    Fix ID: 1173960
    Symptom: When the Symantec kernel module is in place and active, touching ClearCase dynamic view objects causes a kernel trap/machine hang.
    Solution: Corrected code to prevent the problem.



Symantec AntiVirus for Linux 1.0 Maintenance Release 4

Symantec AntiVirus for Linux 1.0 MR4 adds support for 64bit kernels and corrects the following problems:
 

  • Touching ClearCase dynamic view objects caused a kernel trap/machine hang.
  • RHEL 4 - SAVL wasn't applying new definitions from Java LiveUpdate.
  • Red Hat Desktop release 4 (Nahant Update 4) 2.6.9-42.EL - Symev unable to load kernel support.


Symantec AntiVirus for Linux 1.0 Maintenance Release 3

Add support for SLES10SP1 kernel 2.6.16.53-0.8 and 2.6.16.53-0.16
Fix ID: 1149729
Symptom: After installing Symantec AntiVirus for Linux on SLES10SP1 with kernel 2.6.16.53-0.8 and 2.6.16.53-0.16, modules symap and symev failed to load.
Solution: Support for kernel 2.6.16.53-0.8 and 2.6.16.53-0.16 added.

Auto-Protect is disabled on reboot after running up2date to update non-kernel packages
Fix ID: 1095503
Symptom: After using up2date in Red Hat AS 3, Auto-Protect fails to load after reboot.
Solution: Auto-Protect now gives the [Pass] status and loads successfully.

Although Auto-Protect loads correctly, it reports errors
Fix ID: 1115748
Symptom: Auto-Protect kernel module loads correctly, but reports errors when it attempts to insmod the other "matching" kernel modules:
/opt/Symantec/autoprotect/symev-rh-ES-5-2.6.18-8.el5-PAE-i686.ko
/opt/Symantec/autoprotect/symev-rh-ES-5-2.6.18-8.el5-xen-i686.ko
Solution: Corrected. Auto-Protect no longer produces errors.

Add support for Red Hat Enterprise Linux 4.0 Update 5
Fix ID: 1110790
Symptom: Updates needed for Red Hat Enterprise Linux4 Update 5, kernel 2.6.9-55.EL, kernel-2.6.9-55.0.2.EL.i686.rpm, and kernel-smp-2.6.9-55.0.2.EL.i686.rpm.
Solution: Added Red Hat Enterprise Linux 4 Update 5 support.

Add support for SuSE Linux Enterprise 10-2.6.16.27-0.9
Fix ID: 1110799
Symptom: Symantec AntiVirus for Linux fails to load on SuSE Linux Enterprise 10-2.6.16.27-0.9.
Solution: Support for new Kernel added.

Add Symantec AntiVirus for Linux documents to the release package
Fix ID: 1151699
Symptom: Symantec AntiVirus for Linux documents need to be directly incorporated into the RPM package.
Solution: Added documents in .pdf format to new /opt/Symantec/symantec_antivirus/docs folder.

Make sadiag.sh easily accessible
Fix ID: 1151702
Solution: The sadiag.sh tool is now available after install in the following location: /opt/Symantec/symantec_antivirus/sadiag.sh


Symantec AntiVirus for Linux 1.0 Maintenance Release 2

Installation warnings when installing to ESX servers
Fix ID:
936024
Symptom:
When installing sav.rpm on VMware ESX 2.5.3, a series of warning messages appear, beginning with: "/bin/sed: invalid option -- i"
Solution:
Changed the installation process to fix the problem.

Symantec AntiVirus status does not show newly installed definitions
Fix ID:
935993
Symptom:
After updating virus definitions, either using the Intelligent Updater or by dropping the definitions manually, Symantec AntiVirus reports that it is still using the old definition set.
Solution:
Enabled new definition polling.

CIFS filesystem is not recognized as a "remote" (network) filesystem
Fix ID:
992206
Symptom:
The CIFS filesystem is not recognized as a remote (network) filesystem and is available for remote scanning configuration.
Solution:
Added CIFS to the list of remote file system types.

Symantec AntiVirus for Linux 1.0 Maintenance Release 1

Symantec AntiVirus for Linux Maintenance Release 1 did not include fixes, but instead added support for additional kernels. For details, read System Requirements for Symantec AntiVirus for Linux 1.0.



 

 




Legacy ID



2007864478170998


Article URL http://www.symantec.com/docs/TECH103599


Terms of use for this information are found in Legal Notices