History
Multics originated the idea of a search path. The early Unix shell only looked for program names in/bin
, but by Version 3 Unix the directory was too large and /usr/bin
, and a search path, became part of the operating system.
Unix and Unix-like
On POSIX and Unix-like operating systems, the$PATH
variable is specified as a list of one or more directory names separated by colon (:
) characters.
Directories in the PATH
-string are not meant to be escaped, making it impossible to have directories with :
in their name.
The /bin
, /usr/bin
, and /usr/local/bin
directories are typically included in most users' $PATH
setting (although this varies from implementation to implementation). The /sbin
and /usr/sbin
entries for easily executing .
) is sometimes included by users as well, allowing programs residing in the current working directory to be executed directly. System administrators as a rule do ''not'' include it in $PATH
in order to prevent the accidental execution of scripts residing in the current directory, such as may be placed there by a malicious /home/userjoe/bin/script.sh
) or relative path (./script.sh
) on the command line.
When a command name is specified by the user or an exec call is made from a program, the system searches through $PATH
, examining each directory from left to right in the list, looking for a DOS, OS/2, and Windows
On DOS, OS/2, and Windows operating systems, the%PATH%
variable is specified as a list of one or more directory names separated by semicolon (;
) characters.C:\WINDOWS\system32
) is typically the first directory in the path, followed by many (but not all) of the directories for installed software packages. Many programs do not appear in the path as they are not designed to be executed from a command window, but rather from a Graphical User Interface. Some programs may add their directory to the front of the PATH variable's content during installation, to speed up the search process and/or override OS commands. In the DOS era, it was customary to add a EXE
or COM
Com or COM may refer to:
Computing
* COM (hardware interface), a serial port interface on IBM PC-compatible computers
* COM file, or .com file, short for "command", a file extension for an executable file in MS-DOS
* .com, an Internet top-level d ...
, and batch scripts have extensions of BAT
or CMD
. Other executable filename extensions can be registered with the system as well.
Once a matching executable file is found, the system spawns a new process which runs it.
The PATH variable makes it easy to run commonly used programs located in their own folders. If used unwisely, however, the value of the PATH variable can slow down the operating system by searching too many locations, or invalid locations.
Invalid locations can also ''stop'' services from running altogether, especially the 'Server' service which is usually a dependency for other services within a Windows Server environment.
References
{{DEFAULTSORT:Path (Variable) Computer file systems Environment variables