anyone else have probs with avast 1.0.3/1.0.8.pet?
when installed, there is no problem-its after updating-that a pop-up error avast engine failed...etc..
is it just me or does avast have a bug with the updates?
any ideas/help welcomed.. Last edited by piteapup on Sat 17 Apr 2010, 15:31; edited 1 time in total

did you read whats on the avast-forum link above?
shm...ect...i think the prob is in the fact that 400.vps is 36mb,
+ we must change values of shm usage???
i read some where that the kernal has probs with anything over 32mb...this was all ubuntu info tho...
i tried asking @ #ubuntu what a waist of space these ppl were!--have a look at the avast forum again...
thanks for the reply any way...#puppylinux was no better source of in fo either...moan,moan....cheers bro.

Sylvander,
I never used the pet, just downloaded the avast4workstation-1.3.0.tar.gz file from http://www.avast.com/linux-home-edition extracted it to / and made a desktop icon for it by dragging /avast4workstation-1.3.0/bin/avastgui to the desktop from Rox. If you decide to uninstall the pet and upgrade make sure you remove /root/.avast and any other files that avast creates on its own.

The fix works for me in Puppy 4.12 with kernel 2.6.21.7. Maybe boxpup has sysctl in another location??

Edit: corrected the file path _________________﻿Last edited by 2byte on Fri 16 Apr 2010, 21:06; edited 1 time in total

5. Used ROX-filer to attempt to drag-n-drop /avast4workstation-1.3.0/lib/avast4workstation/bin/wrapper-script.sh to the desktop, but it refused to go; when dropped the icon just kept gliding gracefully from whence I dragged it.

Sylvander,
First, my apologies for giving the wrong file to drag to the desktop.

Installed BoxPup 413 r1 to sort this out. Here's what I did.
Extracted the avast tar.gz download to /.
Added the line /sbin/sysctl -w kernel/shmmax=200000000 to /etc/rc.d/rc.local
Created this file /usr/share/applications/Avast.desktop

1. Followed your new instructions...
And it appeared to work, except...
When I ran "Menu->Utility->Avast"...
The following errors were displayed:
(a) "An Error occurred in Avast! engine: invalid argument."
Details:
"Deleted stale lock file /root/.avast/lockfile-root"
(b) "Avast engine failed to reinitialise after database upgrade. The application will terminate now."
It will not run and scan.

Well, all I can do is offer a couple of suggestions to try.
Replace these two files with the ones that came in the original tar.gz archive
/root/.avast/400.vps
/avast4workstation-1.3.0/lib/avast4workstation/var/400.vps
and delete the /root/.avast lock file (if it's there), or do a clean and reinstall of avast.

Run this from a terminal
/sbin/sysctl -w kernel/shmmax=200000000
If you have a low memory machine you might try half of that amount.

Then try avast again.

If it works there might be some code that prevents that line from executing in rc.local.

If it doesn't work I'm out of ideas. Low memory? Not running as root? Downloaded the archive as spot and file permissions are wrong?
The only other thing I can think of is it could be some difference in your system from mine. I have an old 1.8 GHZ, 512MB ram machine with a 2GB swap partition and boxpup 413r1 is a fresh frugal install with a 512 MB save file.

Ha, if I had looked and found those .desktop files it would have saved a little time._________________﻿

thanks 2byte-your trick worked.
i used the 1.0.8.pet found here on forum.
updated ok but slow start up-going to drop it down to 128000000
then see if it starts faster.
-Computer-
Processor : Intel(R) Celeron(R) CPU 2.40GHz(northwood.)
Memory : 766MB (278MB used)
Operating System : Puppy Linux
-Processor-
Name : Intel(R) Celeron(R) CPU 2.40GHz
Family, model, stepping : 15, 2, 7 (Pentium 4)
Vendor : Intel
-Configuration-
Cache Size : 128kb
Frequency : 1200.00MHz
BogoMIPS : 4847.61
Byte Order : Little Endian
so it runs on a system like mine-ihave a frugal install of puppy431.
swap of 1gb
i know its only running at 1,2ghz-ram runs at 200mhz-V.stable+fast enough tho.
the is also more posts at the avast-forum on this subject.
thanks to all-been a good learning process all the same.
uptill now i had no probs with avast 4 linux(odd false posatives)
so i stick with it-i use opera-unite so i like to scan everything before i share it.

1. I'm rather confused now.
(a) e.g. You said:
"Replace these two files with the ones that came in the original tar.gz archive"
But one of those 2 files = this one:
"/avast4workstation-1.3.0/lib/avast4workstation/var/400.vps" [19.9MB]
Came in the tar.gz file, so it's impossible to replace it with itself.

(b) The other file = this one:
"/root/.avast/400.vps" [34.1MB]
Is part of the previous Avast installation.
You instructed previously to delete this, which I did, but have now restored it from a backup.
Should this /root/.avast folder now be retained, and the 400.vps file replaced?

2.
(a) You said:
"Run this from a terminal
/sbin/sysctl -w kernel/shmmax=200000000 "
Is this in addition to, or instead of:
"Add the line /sbin/sysctl -w kernel/shmmax=200000000 to /etc/rc.d/rc.local " ?

3. Could you perhaps begin afresh with instructions?
If necessary I can go right back to before I began all of this [by restoring a backup of the contents of sda3].

All I meant was to get rid of any 400.vps files you have in your system and replace them with the ones from your archive. These are the virus definition files and you need to start with the old ones that avast will still run with. The trouble starts when avast updates these to the latest ones, which are larger files and use up more memory.

Running /sbin/sysctl -w kernel/shmmax=200000000 from the terminal is to test the command on your system. If you execute this from the terminal, and no errors are returned, and then avast runs and updates OK, it would indicate that this same command that you put into rc.local is not executing for some reason. Having /sbin/sysctl -w kernel/shmmax=200000000 in rc.local is a way to have the command executed whenever the system starts, as a convenience. By the way, one of the members on the avast forum suggested using a value of 130000000 instead of 200000000, so that is something else you can try.

shmmax specifies system-wide maximum allowable shared memory segment size so you must have enough memory available for the value used, and the value must be big enough for the virus definition files avast uses.

Sorry to have confused you. Restoring sda3 would get you back to a known working configuration, and you could experiment with the /sbin/sysctl command and upgrading from that point._________________﻿

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum