MAN PAGE COMMENTS to

Chet Ramey
Case Western Reserve University
chet@po.cwru.edu

Last Change: Sat Feb 7 20:50:40 EST 2009

bash_builtins, strip all but Built-Ins section

There's some problem with having a `@'
in a tagged paragraph with the BSD man macros.
It has to do with `@' appearing in the }1 macro.
This is a problem on 4.3 BSD and Ultrix, but Sun
appears to have fixed it.
If you're seeing the characters
`@u-3p' appearing before the lines reading
`possible-hostname-completions
and `complete-hostname' down in READLINE,
then uncomment this redefinition.

.nr )E 0 .}f

\} .}f ..
File Name macro. This used to be `.PN', for Path Name,
but Sun doesn't seem to like that very much.

\|\\$1\| ..

rbash - restricted bash, see bash(1) rbash bash_builtins
rbash.1
.zY

If bash is started with the name rbash , or the -r option is supplied at invocation, the shell becomes restricted. A restricted shell is used to set up an environment more controlled than the standard shell. It behaves identically to bash with the exception that the following are disallowed or not performed:

changing directories with cd setting or unsetting the values of SHELL , PATH , ENV , or BASH_ENV specifying command names containing / specifying a file name containing a / as an argument to the . builtin command Specifying a filename containing a slash as an argument to the -p option to the hash builtin command importing function definitions from the shell environment at startup parsing the value of SHELLOPTS from the shell environment at startup redirecting output using the >, >|, <>, >&, &>, and >> redirection operators using the exec builtin command to replace the shell with another command adding or deleting builtin commands with the -f and -d options to the enable builtin command Using the enable builtin command to enable disabled shell builtins specifying the -p option to the command builtin command turning off restricted mode with set +r or set +o restricted.

These restrictions are enforced after any startup files are read.

(see "COMMAND EXECUTION" under bash(1)), \} rbash turns off any restrictions in the shell spawned to execute the script. end of rbash.1

0

Bash Reference Manual, Brian Fox and Chet Ramey

The Gnu Readline Library, Brian Fox and Chet Ramey

The Gnu History Library, Brian Fox and Chet Ramey

Portable Operating System Interface (POSIX) Part 2: Shell and Utilities, IEEE

sh(1), ksh(1), csh(1)

emacs(1), vi(1)

readline(3)

0

.FN /bin/bash The bash executable

.FN /bin/rbash The rbash executable

.FN /etc/profile The systemwide initialization file, executed for login shells

.FN ~/.bash_profile The personal initialization file, executed for login shells

.FN ~/.bashrc The individual per-interactive-shell startup file

.FN ~/.bash_logout The individual login shell cleanup file, executed when a login shell exits

.FN ~/.inputrc Individual readline initialization file

Brian Fox, Free Software Foundation

bfox@gnu.org

Chet Ramey, Case Western Reserve University

chet.ramey@case.edu

If you find a bug in bash, you should report it. But first, you should make sure that it really is a bug, and that it appears in the latest version of bash . The latest version is always available from ftp://ftp.gnu.org/pub/bash/.

Once you have determined that a bug actually exists, use the bashbug command to submit a bug report. If you have a fix, you are encouraged to mail that as well! Suggestions and `philosophical' bug reports may be mailed to bug-bash@gnu.org or posted to the Usenet newsgroup gnu.bash.bug .

ALL bug reports should include:

0

20 The version number of bash

The hardware and operating system

The compiler used to compile

A description of the bug behaviour

A short script or `recipe' which exercises the bug

Comments and bug reports concerning this manual page should be directed to chet@po.cwru.edu .