Video Screencast Help
Search Video Help Close Back
to help

Check client version in Linux

Created: 22 Feb 2011 | 13 comments
subu_11_1's picture
0 0 Votes
Login to vote

Hello,

 

We have installed SEP client on linux machine and it is working fine.

But how can we check the client version i.e whether it is 32bit client or 64bit client?

 

Regards,

Subodh

Comments 13 CommentsJump to latest comment

Rafeeq's picture

 

.SAV /SEP are native 32 bit applications, it depends on your OS, if you have installed on 32 bit OS then its 32 bit, if on 64 then its a 64...

coz you cannot install 64 bit on a 32 bit OS and vice versa..

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

+1
Login to vote
  • Actions
Rafeeq's picture

You installed SEP on LInux? 

I dont see even the latest version supporting it, which version of SEP u you have it installed?

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

0
Login to vote
  • Actions
subu_11_1's picture

hi

 

OK. If we have 32bit OS sep client will be 32bit and if 64bit OS the 64bit client.

 

But is there any way to check the same. Because my seniors are asking that show the version that you have installed from the machine where you have installed.

I want to show them the same. Is there any way i check it from some command?

 

Regards,

Subodh

Regards,

Subodh R. Dangat

0
Login to vote
  • Actions
Rafeeq's picture

:) you can create a report from SEPM

monitors-logs - computer status, here you will get OS info, u can show that report..

is that SEP you have installed on linux?

if you find a folder called program files ( x86) then its 64 bit OS sep is also 64 bit...

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

0
Login to vote
  • Actions
subu_11_1's picture

hi

 

We have installed client in Linux machine.

It is not managed by SEPM.

How to find the same in linux?

Regards,

Subodh R. Dangat

0
Login to vote
  • Actions
subu_11_1's picture

Some1 please help.

 

Regards

Subodh

Regards,

Subodh R. Dangat

0
Login to vote
  • Actions
Rafeeq's picture

can you post a screen shot of the sep client on linux, all this time I was under impression that only sav can be installe on Linux, may the screen shot can be an eye opener for me :) 

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

0
Login to vote
  • Actions
thatdude's picture

Are you an invited 12.1 beta tester? SEP 12.1 is supposed to manage Linux SEP from what I understand

0
Login to vote
  • Actions
dschrader's picture

SEP 12.1 will not manage Linux. 

0
Login to vote
  • Actions
sandra.g's picture

There is no SEP for Linux. There is SAV for Linux (SAVFL) which is included on the SEP disk download. I think that's where the confusion is coming from.

The opt/Symantec/symantec_info/sav info --version command doesn't specify kernel type--neither does the Windows version, IIRC. I think Rafeeq is correct: if it's a 64-bit OS, then the 64-bit version would have been installed.

sandra

Symantec, Information Development, IMDP
Symantec Endpoint Protection / Core Security Engineering Group

Don't forget to mark your thread as 'solved' with the answer that best helped you!
 

0
Login to vote
  • Actions
thomas_m's picture

 

There is currently no SEP for Linux, nor is there SEP for Linux planned for 12.1. For Linux, use the SAVFL client. The SAVFL client cannot be managed by the SEPM, although it can report logs back to the SEPM by using SAV Reporter, which was released after SAVFL 1.0.10, but can be downloaded from the following KB article.
 
Symantec AntiVirus for Linux (SAVFL) Reporter 1.0.10 Release Notes 
 
The SAVFL client is 32-bit only. If you take a look at the RPM packaging you will see that the only package that has a 64-bit version is the savap package (AutoProtect), which understandably needs it as it has to hook into the kernel. While the deb packaging has separate 64-bit packages for each one, there binaries are still 32-bit. You'll notice this if you've tried to install and use SAV on a 64-bit debian based system without ia32-libs installed.
 
If you really need to confirm that the binary is 32-bit, you can use the file command.
 file /opt/Symantec/symantec_antivirus/sav 

and it should produce an output such as this (note this is from my Ubuntu 10.10 64-bit machine and is showing a 32-bit executable)

 

 /opt/Symantec/symantec_antivirus/sav: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.3, stripped 

Symantec Technical Support Engineer, SEP, SAV for Linux<

+1
Login to vote
  • Actions
subu_11_1's picture

Thomas,

After executing the command :  file /opt/Symantec/symantec_antivirus/sav , I got bekow output :

 

/opt/Symantec/symantec_antivirus/sav: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.4.3, dynamically linked (uses shared libs), for GNU/Linux 2.4.3, stripped

 

But my OS is 64bit and we have installed 32bit Linux client.

We need to install 64bit SAVFL can you let us know how to do the same ?

 

Regards,

 

Subodh

Regards,

Subodh R. Dangat

0
Login to vote
  • Actions
thomas_m's picture

That command shows you information on the sav binary. There is no 64-bit sav binary. The 64-bit packaging includes a 32-bit sav binary as the client portion is architecture independent. 

This may be better illustrated if you look at the rpm packaging. You will notice there is a single sav package. 

 sav-1.0.10-26.i386.rpm 

Also notice that there is no sav package with amd64 in the name. That is because this package is architecture independent, so it works on both 32-bit and 64-bit machines. The binary contained inside was built on a 32-bit machine, but can work on either architecture. This is true for all of the SAVFL packages except the savap (AutoProtect) package, due to the fact that AP needs to hook into the kernel, making it architecture dependent.

If you look at the deb packages, there are separate packages for i386 and amd64. However this distinction doesn't need to be made either, as the binaries inside are the same.

 

Symantec Technical Support Engineer, SEP, SAV for Linux<

0
Login to vote
  • Actions