Am Mon, 15 Mar 2021 15:15:48 +1030 schrieb Simon Lees :

move to /usr/etc/

How would that change anything for the OP? The OP should use 'unalias' and 'unset' in his private .profile, .bashrc, .whatever to declare the desired environment. Olaf

On 3/15/21 3:30 PM, Andrei Borzenkov wrote:

On 15.03.2021 07:58, Olaf Hering wrote:

...

Am Mon, 15 Mar 2021 15:15:48 +1030 schrieb Simon Lees :

...

move to /usr/etc/

How would that change anything for the OP?

The whole idea is that files in /etc will then override files in /usr/etc so OP could simply eliminate unwanted scripts by creating empty files in /etc.

No they will probably supplement them, so his files will need to overwrite the distro ones, but atleast it would have guaranteed execution order which i'm not sure /etc/profile.d does. It would also make it easier to patch out loading them. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

On 15/03/2021 11.04, David T-G wrote: ...

script that grepped the `basename $0 .off` file for definitions and undid each one. That's a pain, though, and by no means guaranteed.

Since files I add to /etc/profile.d remain, curiously enough, I can simply wait until I create a shell and see the unwanted behavior, swear once or twice at such stupidity, and manually remove all of the .off basename files. That's also a pain, though :-)

Cronjob. Or add entries to /etc/permissions.local to deny read permission to each file. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)

On 16.03.2021 05:29, Neil Rickert wrote:

On 3/14/21 8:34 PM, David T-G wrote:

...

Is there any way to keep them from being dropped again so that I don't have to deal with this over and over? *sigh*

You probably cannot prevent it -- or not easily.

You can create ".bash.expert" to prevent or undo some of what you don't want.

It only skips completion settings.

I am currently using:

---- .bash.expert ---- unalias -a unset HISTFILE PS1='\u@\h \$ ' ---- end of .bash.expert ----

Any reason to put it in .bash.expert instead of (at least, documented) .bashrc?

Hi, all! My, how time flies ... It's been a year since I last wrestled with this! ...and then davidtg-robot@justpickone.org said... % % ...and then L A Walsh said... % % % % On 2021/03/14 18:34, David T-G wrote: % % >Is there any way to keep them from being dropped again so that I don't % % >have to deal with this over and over? *sigh* % ... % % % % So...I set the immutable bit on the problematic files. % % So far, that's kept them intact. % [snip] % ... % % Time to go learn something :-) So I went and learned and played and eventually played davidtg@jpo:~> lsattr /etc/profile.d/ls.bash ----i-------------- /etc/profile.d/ls.bash with some of these keep-coming-back files. They were empty and stayed that way; yay. Except that I actually stood at the keyboard in the closet and paid attention to updates one day and found that various ones threw failures because they couldn't tweak these files. Dang it! No, I don't want failing updates; it's hard enough to make sure things stay current. I guess we're back to adding ls.bash.off that figures out what's in the original file and undoes it as part of the login process *sigh* There really oughta be a better way. Maybe in Leap 16, I heard in the old thread ... Have a great day! :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt