If the user or sysadmin did not kill the program the kernel may have. The kernel would only kill a process under exceptional circumstances such as extreme resource starvation (think mem+swap exhaustion).
More Related Contents:
- What’s the best way to send a signal to all members of a process group?
- How can I measure the actual memory usage of an application or process?
- How to prevent a background process from being stopped after closing SSH client in Linux
- Get exit code of a background process
- Threads vs Processes in Linux [closed]
- How do I set the working directory of the parent process?
- Maximum number of processes in linux [closed]
- The difference between fork(), vfork(), exec() and clone()
- How can I kill a process by name instead of PID, on Linux? [duplicate]
- Handling multiple SIGCHLD
- How to write data to existing process’s STDIN from external process?
- Linux Script to check if process is running and act on the result
- Why can’t capture SIGSEGV using signalfd?
- linux: kill background task
- How Linux handles threads and process scheduling
- Programmatically get parent pid of another process?
- Linux/Unix command to determine if process is running?
- SIGKILL signal Handler
- How to get child process from parent process
- How do I get the path of a process in Unix / Linux?
- Does linux schedule a process or a thread?
- Faster forking of large processes on Linux?
- How to get the start time of a long-running Linux process?
- Start script after another one (already running) finishes
- Linux: process into a service
- How to set process group of a shell script
- How to set process ID in Linux for a specific program
- kill process with python
- How can I tell in Linux which process sent my process a signal
- “Max open files” for working process