Starting Bash with the --posix command-line option or executing ‘set -o posix’ while Bash is running will cause Bash to conform more closely to the posix standard by changing the behavior to match that specified by posix in areas where the Bash default differs.
When invoked as
sh, Bash enters posix mode after reading the
The following list is what's changed when `posix mode' is in effect:
bgbuiltin uses the required format to describe each job placed in the background, which does not include an indication of whether the job is the current or previous job.
killbuiltin does not accept signal names with a ‘SIG’ prefix.
.filename is not found.
names. That is, they may not contain characters other than letters, digits, and underscores, and may not start with a digit. Declaring a function with an invalid name causes a fatal syntax error in non-interactive shells.
cdbuiltin will not implicitly append the current directory to it. This means that
cdwill fail if no valid directory name can be constructed from any of the entries in $CDPATH, even if the a directory with the same name as the name given as an argument to
cdexists in the current directory.
forstatement or the selection variable in a
selectstatement is a readonly variable.
readonlybuiltin commands display their output in the format required by posix.
trapbuiltin displays signal names without the leading
trapbuiltin doesn't check the first argument for a possible signal specification and revert the signal handling to the original disposition if it is, unless that argument consists solely of digits and is a valid signal number. If users want to reset the handler for a given signal to the original disposition, they should use ‘-’ as the first argument.
sourcebuiltins do not search the current directory for the filename argument if it is not found by searching PATH.
aliasbuiltin displays alias definitions, it does not display them with a leading ‘alias ’ unless the -p option is supplied.
setbuiltin is invoked without options, it does not display shell function names and definitions.
setbuiltin is invoked without options, it displays variable values without quotes, unless they contain shell metacharacters, even if the result contains nonprinting characters.
cdbuiltin is invoked in logical mode, and the pathname constructed from
$PWDand the directory name supplied as an argument does not refer to an existing directory,
cdwill fail instead of falling back to physical mode.
pwdbuiltin is supplied the -P option, it resets
$PWDto a pathname containing no symlinks.
pwdbuiltin verifies that the value it prints is the same as the current directory, even if it is not asked to check the file system with the -P option.
fcbuiltin does not include an indication of whether or not a history entry has been modified.
commandbuiltins will not report a non-executable file as having been found, though the shell will attempt to execute such a file if it is the only so-named file found in
viediting mode will invoke the
vieditor directly when the ‘v’ command is run, instead of checking
xpg_echooption is enabled, Bash does not attempt to interpret any arguments to
echoas options. Each argument is displayed, after escape characters are converted.
ulimitbuiltin uses a block size of 512 bytes for the -c and -f options.
SIGCHLDwhen a trap is set on
SIGCHLDdoes not interrupt the
waitbuiltin and cause it to return immediately. The trap command is run once for each child that exits.
There is other posix behavior that Bash does not implement by default even when in posix mode. Specifically:
$EDITORas a program to edit history entries if
FCEDITis unset, rather than defaulting directly to
xpg_echooption to be enabled for the
echobuiltin to be fully conformant.
Bash can be configured to be posix-conformant by default, by specifying
the --enable-strict-posix-default to
configure when building
(see Optional Features).