> > > [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 > > > > > > Seems like it's trying to access directories within /proc
> According to the original post (unless I misread it) the f-prot was > installed from the ports collection. So it was claimed. > This version is a native FreeBSD > binary, not run under Linux emulation. > > $ file /usr/local/f-prot/f-prot > /usr/local/f-prot/f-prot: ELF 32-bit LSB executable, Intel 80386, > version 1 (FreeBSD), for FreeBSD 4.9, statically linked, stripped Andy, you are right. But then again, the version I install from ports (observed through truss -f) does not attempt to access /proc, yet the version GM runs apparently wants it. Perhaps it wasn't installed from ports after all. > Additionally, it does not need the /proc filesystem mounting, as far as > I can see. Certainly this version is running on my system without a > procfs. Ditto here (FreeBSD 5.4). (I do have a /proc on this test machine, but f-prot does not access it). > The one caveat for running it on FreeBSD 5.x is that the compat4x > libraries need to be in place, either as part of the world build or by > installing the misc/compat4x port. 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/
