In this lesson, you will learn how the Linux kernel allows you to impose strict boundaries on the resources a process can consume to ensure system stability.
The Concept of Resource Limits
When you launch a process, it exists within a sandbox defined by the operating system. If a process accidentally attempts to consume all available memory or create thousands of files simultaneously, it could bring your entire system to a crawl. To prevent this, Linux implements "Resource Limits" (often called ulimits).
These limits act as a "ceiling" for each process and the children it spawns. By setting these boundaries, you ensure that a single misbehaving program cannot starve the rest of the system of vital resources.
Viewing and Setting Limits
In your shell, you can inspect your current process environment limits using the ulimit command. Typing ulimit -a will display a list of all current constraints, such as the maximum number of open files, the maximum stack size, and the maximum CPU time allowed.
To modify these limits for your current shell session, you use the same command with a specific flag. For example, if you want to prevent a process from creating a core dump file (which can take up massive disk space when a program crashes), you can set the limit to zero:
# Check the current core file size limit
ulimit -c
# Set the core file size limit to 0
ulimit -c 0
Inheritance and Scoping
Just like the environment variables we discussed in previous lessons, these resource limits are inherited. When your shell forks a new process, the child process starts with the same resource constraints as the parent. This creates a "limit chain," where a restrictive setting applied at the start of a user session propagates down to every command or script executed within that session.
While these limits can be tuned, they are ultimately subject to the "Hard" and "Soft" limit rule. A soft limit is the value the kernel enforces, while a hard limit is the absolute maximum that a process can increase its own soft limit to. Only the superuser can increase a hard limit.
Key Takeaway: Resource limits are kernel-enforced ceilings inherited by child processes that prevent individual programs from exhausting system-wide memory, file descriptors, or CPU time.