How to release file descriptors occupied by a process?

To free file descriptors occupied by a process, you need to close the corresponding files or sockets associated with these descriptors.

1. Eliminate descriptor leaks in application code:

   • Ensure all opened files and sockets are properly closed after use. Many programming languages have mechanisms for this (e.g., with open(...) in Python, try-with-resources in Java).
   • Use tools for resource leak analysis.

2. Restart the process:

   • The simplest way that guarantees closing all descriptors occupied by the process. Not always acceptable in production systems.

3. Send a signal to the process:

   • Some applications can handle signals (e.g., SIGUSR1, SIGUSR2) to perform certain actions, including resource release. This depends on the application's implementation.
   • The SIGHUP signal is often used to reload configuration, which may include reopening log files and releasing old descriptors.
   • The SIGTERM signal requests a proper shutdown, during which the process should close all resources.

4. Use debugging and monitoring tools:

   • The command lsof -p <pid> will show a list of open file descriptors for a specific process. This helps identify the source of the problem.
   • The command strace -p <pid> can show system calls of the process, including open, close, read, write, which helps understand how descriptors are used.
   • In some cases, if the problem is related to a malfunctioning kernel or filesystem, a server reboot may be necessary (extreme measure).

Example of using lsof:

# Find the PID of a process (e.g., Nginx)
pgrep nginx

# Show open file descriptors for the process with PID 12345
lsof -p 12345

Example of using strace to analyze system calls related to files:

# Trace system calls of the process with PID 12345, filtering by file operations
strace -p 12345 -e open,close,read,write

It is important to understand that forcibly "freeing" descriptors without the process's involvement (e.g., directly manipulating kernel structures — which is impossible under normal conditions) can lead to instability and application failure. The correct approach is to eliminate the cause of the leak or restart the process.