I've been installing the debian package (kav4fs_5.7-17_i386.deb) on Ubuntu Server 6.10 LTS and thought I would post my findings here and ask a few questions:

To install the package I did the following:
* Installed the linux-headers package for kernel module compilation
sudo apt-get install linux-headers

* Installed the basic compiling tools
sudo apt-get install build-essential

* Installed the Debian program package
sudo dpkg -i <package>.deb
- Enter the directory of the licence file (e.g /home/admin)
- Set the proxy (none for me)
- Download the updates (DO THIS otherwise the service won't start)
- Webmin (skipped)
- Kernel module: enter "# /opt/kaspersky/kav4fs/src/kavmon.pl -b /usr/src/linux-headers-2.6.15-29-server" or replace kernel version number


* Installed the Debian networkagent package
sudo dpkg -i <package>.deb
- Followed the prompts

Now, heres where the problems started. The kav4fs service and kavmidware service wouldn't start until I manually created the folder /var/run/kav4fs. If I stopped the the services kav4fs, kavmidware, klnagent but they didn't seem to delete the folder either, but every time I reboot the service doesn't start automatically because the folder gets deleted somewhere (I guess they are all purged at startup)

So there seems to be a bug with the package not creating or not having the right to create the folder /var/run/kav4fs. I'm thinking of adding a command to create the folder in the init.d scripts but haven't tested this yet, or updating the conf file /etc/opt/kaspersky/kav4fs.conf to remove the /var/run/kav4fs folder to just be /var/run

Can anyone help with some clarification on this?


More Info: The logs generated if the folder isn't created are as follows
admin@ubuntu:/var/run$ sudo /etc/init.d/kavmidware start
Failed to bin unix socket to /var/run/kav4fs/kavmidware.socket
kavmidware not started
admin@ubuntu:/var/run$ sudo /etc/init.d/kav4fs start
Cannot create pid file: /var/run/kav4fs/kavmonitor.pid: No such file or directory
kavmonitor not started: system error
admin@ubuntu:/var/run$
[08/10/07 14:21:08 I] Kaspersky Anti-Virus On-Access Scanner for Linux. Version 5.7.14/RELEASE build #22, compiled Apr 20 2007, 20:14:33
[08/10/07 14:21:08 I] Copyright © Kaspersky Lab, 1997-2007.
[08/10/07 14:21:08 I] Portions Copyright © Lan Crypto
[08/10/07 14:21:08 I] Config file /etc/opt/kaspersky/kav4fs.conf
[08/10/07 14:21:08 F] Cannot create pid file: /var/run/kav4fs/kavmonitor.pid: No such file or directory
[08/10/07 14:21:08 E] Cannot connect to: /var/run/kav4fs/kavmidware.socket :connect(): No such file or directory
[08/10/07 14:21:08 I] Kavmonitor is finished
[08/10/07 14:50:07 I] Kaspersky Anti-Virus On-Access Scanner for Linux. Version 5.7.14/RELEASE build #22, compiled Apr 20 2007, 20:14:33
[08/10/07 14:50:07 I] Copyright © Kaspersky Lab, 1997-2007.
[08/10/07 14:50:07 I] Portions Copyright © Lan Crypto
[08/10/07 14:50:07 I] Config file /etc/opt/kaspersky/kav4fs.conf
[08/10/07 14:50:07 F] Cannot create pid file: /var/run/kav4fs/kavmonitor.pid: No such file or directory
[08/10/07 14:50:07 E] Cannot connect to: /var/run/kav4fs/kavmidware.socket :connect(): No such file or directory
[08/10/07 14:50:07 I] Kavmonitor is finished

There is no support for Ubuntu Linux at this moment

Just so you know, everything worked fine as long as you change the kav4fs.conf as follows in :/etc/opt/kaspersky/kav4fs.conf

[network]
#MiddlewareAddress=/var/run/kav4fs/kavmidware.socket
MiddlewareAddress=/var/run/kavmidware.socket
...
[monitor.path]
BackupPath=
#PidFile=/var/run/kav4fs/kavmonitor.pid
PidFile=/var/run/kavmonitor.pid

And make sure you install a license file and get the initial program updates on installation.

If you re-run the configuration for the package (sudo dpkg-reconfigure kav4fs) then you need to complete all steps again including module compilation otherwise it won't work.