I handle this the same way. I agree that it is more extensable for corporate wide system configurations. On a one off system it may be easier to use /etc/profile but maintaining a large number of machines each with a slightly different /etc/profile is just a PITA. -----Original Message----- From: Robert P. J. Day [mailto:rpjday@mindspring.com] Sent: Sat, November 23, 2002 11:16 AM To: psyche mailing list Subject: system-wide configuration for user accounts i'm curious about how people set up system-wide config for user accounts on their hosts, as i'm designing the account admin chapter for my migration web site and i want to make sure i give good advice. once upon a time, an admin would add sys-wide stuff in /etc/profile, to affect everyone. these days, we have the /etc/profile.d/*sh directory structure. while newly-installed RPMs are certainly free to add RPM-specific files here that will be consulted upon login, i also like to throw extra stuff in here related to the app manually; eg., when i added sun's j2sdk package, i manually added a "java.sh" file to that directory which extended the search PATH. is this considered acceptable behavior? to just manually toss extra files in there? it certainly is a cleaner and more modular approach than constantly hacking /etc/profile. rday Robert P. J. Day, RHCE, RHCI Eno River Technologies, Chapel Hill NC Unix, Linux and Open Source corporate training http://www.linux-migration.org -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
