Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
However I'm still not clear on what /etc/profile.d role is, what these scripts do, and why they need the permissions they do. No man or info pages for this directory either.
I want to drop the world readable and executable permissions, along with executable for group.
Any ideas or insight?
thanks
Last edited by JockVSJock; 10-27-2017 at 09:33 AM.
Interesting that two of the files are not executable.
I guess that /etc/profile sources them, so there is a need for read but not for execution.
On the other hand, the files do not harm, and are not in the user's path.
--
For each file you can determine the software package, for example
It may break things to remove them, and at a minimum it will change behavior (e.g. ls won't use colors by default, etc.).
They are not in anyone's path, but they are sourced by /etc/profile, so without read access, they will no longer be sourced when loaded, and may cause errors to be displayed on login if the /etc/profile on RHEL 5 doesn't check for readability first (I've seen that on some distributions, especially older ones).
The files are put in /etc/profile.d so that packages don't have to edit /etc/profile to get the proper default setup or have each user manually update their environment. It provides a clean way for packages to provide common aliases, environment variables, and updates to the path.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.