GM wrote:
GM wrote:
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.
Hi,
/proc/82371/mem isn't random. /proc is a virtual file system. 82371 is
a directory containing info about process 82371. mem is a file
containing memory usage info for that process. If the directory/file
doesn't exist. Chances are process 82371 ended before f-prot got to read it.
That or it is not allowed (ie. permissions). If your using Linux, check out
'man proc'.
David
----------------------------------------------------------------------------
------------
Hi David
I have the following permissions on my /proc directory :-
drwxrwxrwx 3 root wheel 512B Aug 1 17:45 proc/
I am using freeBSD 5.3 ad 5.4 and getting the same error on both versions /
releases.
PS: Thanx for the prompt reponse...
GM.
Check the permissions on the directories within /proc. Also, get the pid
of a running process and go into it's directory and check the
permissions there. For example, I did the following as my amavisd user:
(PID 29659 is the pid of the master amavisd on my system.)
$ cd /
$ ls -l | grep proc
dr-xr-xr-x 145 root root 0 Jan 18 2005 proc/
$ cd /proc
$ ls -l | grep 29659
dr-xr-xr-x 3 amavisd amavisd 0 Aug 1 12:40 29659/
$ cd 29659
$ ls -l
$ ls -l
ls: cannot read symbolic link cwd: Permission denied
ls: cannot read symbolic link root: Permission denied
ls: cannot read symbolic link exe: Permission denied
total 0
-r-------- 1 root root 0 Aug 1 13:40 auxv
-r--r--r-- 1 root root 0 Aug 1 13:40 cmdline
lrwxrwxrwx 1 root root 0 Aug 1 13:40 cwd
-r-------- 1 root root 0 Aug 1 13:40 environ
lrwxrwxrwx 1 root root 0 Aug 1 13:40 exe
dr-x------ 2 root root 0 Aug 1 13:40 fd/
-r--r--r-- 1 root root 0 Aug 1 13:40 maps
-rw------- 1 root root 0 Aug 1 13:40 mem <-- file in question
-r--r--r-- 1 root root 0 Aug 1 13:40 mounts
lrwxrwxrwx 1 root root 0 Aug 1 13:40 root
-r--r--r-- 1 root root 0 Aug 1 13:40 stat
-r--r--r-- 1 root root 0 Aug 1 13:40 statm
-r--r--r-- 1 root root 0 Aug 1 13:40 status
dr-xr-xr-x 3 root root 0 Aug 1 13:40 task/
-r--r--r-- 1 root root 0 Aug 1 13:40 wchan
$
As you can see, there are certain file that on root can read. mem is
one of them. So..
$ cat mem
cat: mem: Permission denied
$
f-prot is trying to read a file it does not have access to when it is
not running as root. Looks like the f-prot writers didn't add code to
handle IO errors such as "permission denied".
Now, I did this is on a linux system, try following the same steps on a
*BSD system and see what happens.
HTH
David
-------------------------------------------------------
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/
