A few man page fixes from RHEL-5

Hello, these three patches have been accepted into RHEL-5.2 and I think they may be worth including in bash upstream. More info at , and .

Re: A few man page fixes from RHEL-5

Tomas Janousek wrote: these three patches have been accepted into RHEL-5.2 and I think they may be worth including in bash upstream. +Also, please note that while executing in non-interactive mode and while in +.I posix +mode, any special builtin (like \fB.\fP, \fB:\fP, \fBbreak\fP, +\fBcontinue

Re: A few man page fixes from RHEL-5

Matthew Woehlke <[EMAIL PROTECTED]> writes: > Doesn't 'exec' replace the process? I get the others (I think), but I > don't understand what shell is left to "stop execution" after an exec. exec can fail. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeld

Re: A few man page fixes from RHEL-5

Matthew Woehlke wrote: Doesn't 'exec' replace the process? I get the others (I think), but I don't understand what shell is left to "stop execution" after an exec. `exec' can fail for various reasons: usually because the file to be executed is not present or not executable. In its default mod

Re: A few man page fixes from RHEL-5

Andreas Schwab wrote: Matthew Woehlke <[EMAIL PROTECTED]> writes: Doesn't 'exec' replace the process? I get the others (I think), but I don't understand what shell is left to "stop execution" after an exec. exec can fail. D'oh, fail to *do* anything... I was thinking if whatever was exec'd

bash sucks lots of RAM doing read & echo in loop

Configuration Information [Automatically generated, do not change]: Machine: i386 OS: freebsd6.2 Compiler: cc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='freebsd6.2' -DCONF_MACHTYPE='i386-portbld-freebsd6.2' -DCONF_VENDOR='portbld' -DLOCALEDIR='/usr/local/share/loc