procmail
[Top] [All Lists]

Re: PATH

2004-03-08 07:59:27
On Mon, 08 Mar 2004, 07:49 GMT-06 (14:49 local time) David W. Tamkin
wrote:

The decision of whether to treat the word "test" as a shellmeta is made
at compile time, not at run time.  The question might be whether a test
executable is present in procmail's start-up PATH, or whether it's in
the environmental PATH during compilation, or whether it's in /bin; I
really don't know where the build process looks when it makes that choice.

I also did not find anything about the mechanismn how procmail treats
which PATH. In my tests, I haven't assigned PATH in the global
procmailrc, so it should keep its default one.

Once I have started antivirus.rc out from my $HOME/.procmailrc,
procmail's default PATH holded the following value:

/home/roal/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/X11R6/bin

so '/usr/bin' reads as the third location to look for the 'test'
executable. 'test' in fact resides there and not in one of the first
two directories:

[roal(_at_)ns roal]$ ls -l /home/roal/bin/test
ls: /home/roal/bin/test: No such file or directory

[roal(_at_)ns roal]$ ls -l /bin/test
ls: /bin/test: No such file or directory

[roal(_at_)ns roal]$ ls -l /usr/bin/test
-rwxr-xr-x    1 root     root        16888 Feb  9  2001 /usr/bin/test

Therefore, the logical conclusion for me would be, that just executing
'test' afterwards should be equal to executing '/usr/bin/test', but it
isn't. I still don't understand why.

rob.


_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>