/etc/profile — System-Wide Login Shell Configuration

---

What You Will Learn

---

1. Understand the purpose and role of /etc/profile as a system-wide configuration file.
2. Learn how it differs from user-specific files such as ~/.bash_profile and ~/.bashrc.
3. Discover how login shells automatically execute /etc/profile.
4. Understand how environment variables, PATHs, and defaults are set for all users.
5. Apply system-wide configurations that support multiple WordPress users or service accounts.
6. Follow best practices for safe editing, integration, and troubleshooting.

---

1. What is /etc/profile

/etc/profile is a global configuration script executed automatically for every user when they start a login shell (for example, when logging in via SSH or terminal). It defines system-wide environment variables, PATH settings, and other defaults shared by all users on the system. This file acts as the system equivalent of ****~/.bash_profile, providing a central point to define environment behavior for all accounts.

2. When It Runs

Event	/etc/profile Execution
User logs in via SSH	✅ Runs
User logs in through terminal (TTY)	✅ Runs
User runs new interactive subshell (bash)	❌ Skipped
Cron or non-login scripts	❌ Skipped
It is executed before the user’s own files (~/.bash_profile, ~/.bashrc) and provides default settings that can later be overridden by the user.

---

3. Hierarchy of Execution

When a login shell starts, Bash reads configuration files in the following order:

1. /etc/profile
2. The first found among:

• ~/.bash_profile
• ~/.bash_login
• ~/.profile

3. If any of the above files source .bashrc, it runs next. Therefore, /etc/profile runs once per login, providing a system-level base configuration that user-specific files can modify.

---

4. Purpose and Functionality

Function	Description
System-wide PATH setup	Defines executable search paths for all users.
Environment variables	Sets global values like LANG, EDITOR, or HISTSIZE.
Resource limits	Adjusts memory or process limits via ulimit.
Startup messages	Displays global banners or login notices.
Sourcing additional scripts	Loads files from /etc/profile.d/ for modular configurations.

---

5. File Location and Structure

• File Path: /etc/profile
• Ownership: Root (root:root)
• Permissions: Readable by all, writable by root only (rw-r--r--) Directory structure overview:

/etc/
├── bash.bashrc
├── profile
└── profile.d/
├── lang.sh
├── vim.sh
└── wp-tools.sh

/etc/profile Example Snippet

# /etc/profile — Global Login Configuration

# Set PATH for all users
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/wp-tools"
export PATH

# Default editor
export EDITOR=nano

# Language and locale
export LANG=en_US.UTF-8

# History size
export HISTSIZE=5000

# Source additional system scripts
for script in /etc/profile.d/*.sh; do
if [ -r "$script" ]; then
. "$script"
fi
done
unset script

---

6. How /etc/profile Differs from Other Files

File	Scope	Execution Timing	Purpose
/etc/profile	System-wide	Login shell	Global environment for all users
/etc/bash.bashrc	System-wide	Interactive shell	Global aliases/functions for all users
~/.bash_profile	User-specific	Login shell	Custom per-user login setup
~/.bashrc	User-specific	Interactive shell	Aliases, colors, prompt
~/.bash_logout	User-specific	Logout	Cleanup on exit

---

7. How It Integrates with /etc/profile.d/

The directory /etc/profile.d/ contains small modular scripts executed by /etc/profile. This structure allows administrators to add or remove features without editing /etc/profile directly. Example: File: /etc/profile.d/wp-tools.sh

# WordPress VPS global tools
if [ -d /root/wp-tools ]; then
export PATH=$PATH:/root/wp-tools
fi

File: /etc/profile.d/lang.sh

# Language settings
export LANG=en_US.UTF-8
export LC_ALL=en_US.UTF-8

When a user logs in, /etc/profile automatically sources both scripts. ✅ Advantage: You can manage individual system features (e.g., WordPress tools, locale, vim settings) independently.

8. WordPress VPS Use Cases

Use Case	Example	Purpose
Global WP-CLI Path	export PATH=$PATH:/usr/local/bin:/root/wp-tools	Ensures wp is available for all users.
Default Environment Variables	export EDITOR=nano	Simplifies editing for all SSH users.
Server Banner	echo "Welcome to WordPress Performance Server"	Adds custom message on SSH login.
Resource Control	ulimit -n 4096	Limits open files per user session.
Language Settings	export LANG=en_US.UTF-8	Prevents locale-related CLI errors.

---

9. Editing and Applying Changes

To edit:

sudo nano /etc/profile

After saving, apply immediately:

source /etc/profile

Verify applied variables:

echo $PATH
echo $EDITOR

---

10. Best Practices

1. Avoid direct editing for small changes — use /etc/profile.d/*.sh instead.
2. Always backup before modification:

cp /etc/profile /etc/profile.bak

3. Use absolute paths for reliability.
4. Keep commands non-interactive — no prompts or long-running processes.
5. Avoid user-specific logic inside /etc/profile — place those in ~/.bash_profile.
6. Use consistent permissions (root-writable only).
7. Test changes with a new login session to confirm correct behavior.

---

11. Troubleshooting

Problem	Cause	Solution
New PATH not applied	Shell not restarted	Re-login or source /etc/profile
Command not available globally	Script in /etc/profile.d not executable	Ensure script ends with .sh and is readable
Login delay	Heavy or interactive commands in /etc/profile	Remove non-essential logic
User variables overwritten	Conflict with ~/.bash_profile	Adjust user-level overrides

---

12. Quick Lab

Objective: Add a global WordPress maintenance path and verify it applies to all users.

1. Edit /etc/profile:

sudo nano /etc/profile

2. Add:

export PATH=$PATH:/root/wp-tools
export WPCLI="/usr/local/bin/wp"

3. Save and reload:

source /etc/profile

4. Verify as another user:

su - ubuntu
echo $WPCLI
wp --info

✅ All users can now run wp commands globally without editing their individual profiles.

13. Glossary

Term	Definition
Login shell	The first shell that runs after user login (SSH or console).
System-wide	Configuration that applies to all users on the system.
Profile scripts	Bash startup files that define the shell environment.
/etc/profile.d/	Directory containing modular environment scripts.
ulimit	Command for setting resource usage limits.

---

14. Mini-Quiz

1. When is /etc/profile executed?
2. How does /etc/profile differ from .bash_profile?
3. Why is /etc/profile.d/ useful for server management?
4. How can you test new changes without rebooting?
5. Why should you avoid interactive commands in /etc/profile?

---

15. Summary

• /etc/profile defines system-wide login shell settings and runs automatically for all users.
• It sets up environment variables, PATHs, and global configurations shared across accounts.
• It sources modular scripts from /etc/profile.d/ for structured, maintainable management.
• Perfect for WordPress VPS environments where multiple accounts share WP-CLI, Redis, or maintenance tools.
• Always test and back up before modifying to ensure consistent and secure server behavior.

---