Title: Signature
Robert Steinmetz wrote:

Responding to my own post with new information.
I think I've confirmed that the problem is the $PATH, or the perl equivalent.
I added the full path name where the specific commands were called and that removed that error. Some of the commands seem to be called from other perl scrips so the problem seems to be my perl set up.
But I'm not clear how perl actually sets the path.
The users login shell is /bin/sh
I often sudo bash if I am doing a lot of admin work, rather that typing sudo for each command
The script begins with #!/usr/bin/perl -T -w which invokes perl
when I invoke sudo sh I get the same results although every interactive shell I have tried includes /bin /sbin /usr/bin and /usr/sbin
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
Some have a couple more options.

BTW, plain text (not HTML) would be appreciated.
I wasn't sure of the protocol here but I thought I had. I'll try to remember.


--
Robert Steinmetz, AIA
Principal
Steinmetz & Associates

Reply via email to