and I just tried removing /sbin and /bin from the PATH. No joy. PATH="/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin" drwxr-xr-x 2 root root 20480 Jun 25 16:23 /usr/sbin drwxr-xr-x 2 root root 4096 Sep 25 2014 /usr/local/sbin drwxr-xr-x 2 root root 4096 Dec 8 2023 /root/bin drwxr-xr-x 2 root root 4096 Jun 10 20:49 /usr/local/bin dr-xr-xr-x 2 root root 81920 Jun 23 16:08 /usr/bin / # amavisd Insecure directory in $ENV{PATH} while running with -T switch at /usr/lib/perl5/5.38.2/Net/Domain.pm line 173. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.38.2/Amavis/Conf.pm line 1038. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.38.2/Amavis.pm line 27. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.38.2/Amavis.pm line 27. On 6/25/24 18:40, Curtis J Blank wrote:
Thanks.
I thought of removing /sbin and /bin from the path but without the links what if something is looking for /sbin/ProgramA or /bin/ProgramB it's not going to find them.
And, I would have to do that and how would I do that so that /sbin and /bin are not in the PATH at boot? Done globally that could brick the boot and if I were to how wouId do that for only amavisd and then some update could reverse it.
I don't get this, if this is a bug i.e. it's kinda like WoW!
-Curt
On 6/25/24 17:17, Bob Rogers wrote:
From: Curtis J Blank <curt@curtronics.com> Date: Tue, 25 Jun 2024 16:46:17 -0500
Here's the PATH and each of directories in the PATH's permissions. I wonder if it choking on the permissions of the links?
It shouldn't, because link permissions can only revoke bits (IIRC), rather than grant additional ones.
PATH="/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin"
lrwxrwxrwx 1 root root 8 Dec 8 2023 /sbin -> usr/sbin . . . lrwxrwxrwx 1 root root 7 Dec 8 2023 /bin -> usr/bin
Odd that /bin and /sbin are symbolic links; odder still that they are links to other standard program directories, since both pairs ought to exist. Oddest of all that they are expressed as relative pathnames.
Which might be the case because on the server that is working /sbin and /bin are *not* links . . .
On the off chance that it's choking on the fact that they are relative links, you could try using a PATH without /bin and /sbin, since (as you've shown) these two directories are redundant. Really, that shouldn't matter, since relative link targets are interpreted with respect to the link directory. So if it works, that would have to be a bug in that version of Perl. But since it's a real difference you've found between the two installations, it could be worth a try.
-- Bob