A readlink(2) call on this fileįor example, socket: will be a socket and its inode is 2248868. Whose content is the file type with the inode. Thus, 0 is standard input, 1 standard output, 2 standard error, etc.įor file descriptors for pipes and sockets, the entries will be symbolic links Open, named by its file descriptor, and which is a symbolic link to the actualįile. This is a subdirectory containing one entry for each file which the process has Linux 2.0 returns a string in the format:įor example, :1502 would be inode 1502 on device major 03 (IDE, MFM, etc.ĭrives) minor 01 (first partition on the first drive).įind(1) with the -inum option can be used to locate the file. Under Linux 2.0 and earlier /proc//exe is a pointer to the binary which wasĮxecuted, and appears as a symbolic link. Main thread has already terminated (typically by calling pthread_exit(3)). Multithreaded process, the contents of this symbolic link are not available if the To run another copy of the same executable as is being run by process. This symbolic link can be dereferenced normally Īttempting to open it will open the executable. Under Linux 2.2 and later, this file is a symbolic link containing the actual Null bytes ('\0'), and there may be a null byte at the end. This file contains the environment for the process.
The main thread has already terminated (typically by calling pthread_exit(3)). In a multithreaded process, the contents of this symbolic link are not available if Note that the pwd command is often a shell built-in, and might not work properly. Out the current working directory of process 20, for instance, you can do this: This is a symbolic link to the current working directory of the process.
proc//coredump_filter (since kernel 2.6.23) Set of strings separated by null bytes ('\0'), with a further null byte after the The command-line arguments appear in this file as a In the latter case, there is nothing in this file: that is, a read on thisįile will return 0 characters. This holds the complete command line for the process, unless the process is a This file is present only if the CONFIG_CGROUPS kernel configuration option is control group in the hierarchy to which the process belongs set of subsystems bound to the hierarchyģ. The colon-separated fields are, from left to right:Ģ. For eachĬgroup hierarchy there is one entry containing colon-separated fields of the form: This file describes control groups to which the process/task belongs. The format is one unsigned long ID plus one unsigned long value forĮach entry. This contains the contents of the ELF interpreter information passed to the processĪt exec time. Each such subdirectory contains the following pseudo.
.jpeg "cat proc cpuinfo virtual address")
There is a numerical subdirectory for each running process the subdirectory is The following list describes many of the files and directories under the /proc hierarchy. The proc filesystem is a pseudo-filesystem which provides an interface to kernel data Linux 2.6.39-400.23.1.el6uek.Proc - process information pseudo-filesystem Model name : Intel(R) Core(TM) i5-2410M CPU 2.30GHzįlags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc up rep_good nopl pni monitor ssse3 lahf_lmĪddress sizes : 36 bits physical, 48 bits virtual Is this occurring because I am using virtual software? ~]# cat /proc/cpuinfo However on my OEL guest (on VirtualBox) /proc/interrupts only gives me a CPU0 column, suggesting that I only have one core. The Task Manager shows that I have 4 boxes under the Performance tab, which I assume to be 4 cores. My host machine is Windows 7, running an Intel Core i5 Processor.
0 kommentar(er)
