Hi Mark I guess we are getting closer to the problem perhaps...
Seems like it's trying to access directories within /proc [EMAIL PROTECTED] /]# truss -o 0.log f-prot f-prot -dumb -archive -packed /var/amavis/tmp/amavis-20050801T172532-40177 truss: cannot open /proc/82371/mem: No such file or directory truss: cannot open /proc/curproc/mem: No such file or directory [EMAIL PROTECTED] /]# truss -o 0.log f-prot f-prot -dumb -archive -packed /var/amavis/tmp/amavis-20050801T172532-40177 truss: cannot open /proc/84362/mem: No such file or directory truss: cannot open /proc/curproc/mem: No such file or directory [EMAIL PROTECTED] /]# truss -o 0.log f-prot f-prot -dumb -archive -packed /var/amavis/tmp/amavis-20050801T172532-40177 truss: cannot open /proc/84610/mem: No such file or directory truss: cannot open /proc/curproc/mem: No such file or directory I have taken the libirty to create the directory /proc/curproc/mem ,, but I'm not sure about the random /proc/82371/mem directories. Anyway, this is what I then get :- [EMAIL PROTECTED] /]# truss f-prot f-prot -dumb -archive -packed /var/amavis/tmp/amavis-20050801T172532-40177 truss: cannot open /proc/84690/mem: No such file or directory truss: cannot open /proc/curproc/mem: Is a directory [EMAIL PROTECTED] /]# Much apreciated ! GM. -----Original Message----- From: Mark Martinec [mailto:[EMAIL PROTECTED] Sent: Monday, August 01, 2005 2:05 AM To: [EMAIL PROTECTED] Subject: Re: [AMaViS-user] f-prot DIED on signal 11 (008b) GM, > # su vscan -c 'f-prot -dumb -archive -packed > /var/amavis/tmp/amavis-20050731T034318-00618 </dev/null' > Segmentation fault > > # f-prot -dumb -archive -packed > /var/amavis/tmp/amavis-20050731T034318-00618 </dev/null Virus > scanning report - 31 July 2005 @ 3:45 If the program f-prot runs well as root, but fails on SEGV when running as user vscan, I would suspect some problem with its internal files (like virus signatures), or perhaps with its environment or account vscan, triggering a bug in f-prot, unprepared to handle the unexpected situation. Does it run under your ordinary user account? Try running it through truss, both as root and as user vscan, save trace on a file, and compare the two. It may narrow down the problem to a nearby operation that f-prot executed: # truss -o 0.log f-prot f-prot -dumb -archive -packed some-directory # su vscan $ truss -o 1.log f-prot f-prot -dumb -archive -packed some-directory (make sure the truss log file can be created, considering uid) Mark ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
