Just as with fuser, however, if we’re using vi to edit the file, lsof won’t show it as in use. In this case, we see that the file is opened for reading, with FD = 4r. Let’s look at the output when the less command is accessing the file, instead of vi: $ lsof | The FD field can have three parts: file descriptor ( 4 in our case) is the first, a mode character is the second ( u means the file is accessible for reading and writing), and a lock character is the third.
If the process has threads, we’ll see their identification number, TID, with the task command. If you look at the man page, you will see there are plenty of options available with ps, but in the real world, ps aux is the one that Linux administrators use. The lsof command returns the process name, the PID, and the user who is running the process. Vi 24807 john 4u REG 8,3 12288 3147621 /home/john/. List running processes in Linux Utilizing ps as a command Running the ps command without any options produces an output similar to To show the currently executing processes in a hierarchical order. The lsof CommandĬOMMAND PID TID TASKCMD USER FD TYPE DEVICE SIZE/OFF NODE NAME Example: sh abc.sh & 1 6917 jobs 1+ Running sh abc.sh & Thats mean that the sh abc.sh process started in background is running. Running the command with the -k option may kill all processes that use the pointed file or directory, so use it with care. The right way to check in the current bash session if a process started in background, like sh abc.sh &, is already running or not is to use jobs builtin command. However, that may not always be the case. In this case, the last line of the output is the process we’re looking for. The response is a list of all processes that are accessing files on the same file system. However, we can try finding the process by analyzing and guessing the output of fuser -cv text.txt. The kernel did its job already, so information on the file is not available.
When we run the same command, nothing will be returned because vi opens the file, reads its content to memory, and closes it. Let’s say the same file is being accessed by vi. Let’s give it a try to kill the less process, with SIGKILL, using the PID 24815: $ fuser -k text.txt Running the command with the -k option will kill the process that it finds.
0 kommentar(er)
