On Fri, Dec 18, 2020 at 16:23:47 -0500, Gene Heskett wrote:
> On Friday 18 December 2020 15:06:14 Nathan Stratton Treadway wrote:
>
> > On Fri, Dec 18, 2020 at 14:44:07 -0500, Gene Heskett wrote:
> > > On Friday 18 December 2020 14:33:03 Nathan Stratton Treadway wrote:
> > > > ls -l /etc/login.defs /etc/defaults/su
> > >
> > > ls: cannot access '/etc/defaults/su': No such file or directory
> > > -rw-r--r-- 1 root root 10496 Aug 7 2019 /etc/login.defs
> >
> > (Sorry, obviously I mispelled "default" in that command; see my other
> > email for the new batch of commands.)
> -rw-r--r-- 1 root root 20 Dec 17 10:27 /etc/default/su
> -rw-r--r-- 1 root root 10496 Aug 7 2019 /etc/login.defs
Did you manually edit the /etc/default/su file yesterday?
If so, I take it that you added the ALWAYS_SET_PATH line to it at that
point?
On _Stretch_, you do NOT want any ALWAYS_SET_PATH line at all. The
point of that line is to make the "su" command _on Buster_ act like the
Stretch version used to act. As the warning message indicates, your
current version of "su" does not recognize that parameter.
So, if you added that line to /etc/default/su yesterday, you can just go
ahead and delete that line again. (Actually at 20 bytes I guess the
file only contains that one line, so probably the file didn't exist
before yesterday; if that's true, you can just delete it again....)
Meanwhile, the error message you have been getting for the past hear
would appear to be coming from the line with that parameter in found in
the login.defs file.
I would say you could just go ahead and delete/comment out that line
from that file as well -- but login.defs is shared across multiple
commands in the shadow password suit, so there is a chance that some
other command will be affected when you edit it. That's why I sent the
commands to try to figure out where the current version of the file
originally came from.
However, off hand it seems like the warning message you were getting is
an indication that the paremeter is just not implemented yet in your
version of the shadow utilties, so if you don't want to investigate that
side of things it's probably safe for you to go ahead and comment out
the line in the login.defs file. That should fix the warning messages,
and you can then keep an eye out for any cron jobs or whatever that
suddenly stop working because the PATH is no longer set as expected....
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
