Re: wait -n shouldn't collect multiple processes

thinking that an exxplanation about the interactive vs non-interactive behaviour might be useful. Cheers, Ben signature.asc Description: PGP signature

Re: wait -n shouldn't collect multiple processes

er? Cheers, Ben signature.asc Description: PGP signature

Re: wait -n shouldn't collect multiple processes

trying to implement something akin to 'make -j' in bash. Make will stop if any of the child processes fail. Cheers, Ben signature.asc Description: PGP signature

Re: wait -n shouldn't collect multiple processes

pletes, another one is started immediately. If I start (say) 10 processes and then wait on the first, I may have chosen the longest running process. Ben signature.asc Description: PGP signature

wait -n shouldn't collect multiple processes

of the available (terminated) processes. If there are multiple, they can be collected by calling wait -n multiple times or calling wait without '-n'. Ben

build failure with enable-static-link

Hello, bash-4.4 doesn't build with --enable-static-link. Buidling with an additional --without-bash-malloc makes it work. /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libc.a(malloc.o): In function `free': (.text+0x5f20): multiple definition of `free' ./lib/malloc/libmalloc.a(malloc.o)

PS0 issue with escape sequence

Hello, using bash-4.4, setting PS0 to '\[\033[1;36m\]started at \t\[\033[0m\]\n' makes it output PS0 with a non-printable \x01\x02 prefix and suffix. 01 02 73 74 61 72 74 65 64 20 61 74 20 30 33 3a |..started at 03:| 0010 31 38 3a 30 37 01 02 0a |18:07..

Associative array assignment crashes Bash interpreter

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA

Buffer overflow bug in Bash

etc/hadoop/conf/`basename $n`" if [ -n "${x[$f]}" ]; then for m in ${foo[$n]}; do echo; done fi done ------ Best regards, -- Ben Okopnik

Re: Parallelism a la make -j / GNU parallel

Colin McEwan writes: > I frequently find myself these days writing shell scripts, to run on > multi-core machines, which could easily exploit lots of parallelism (eg. a > batch of a hundred independent simulations). > > The basic parallelism construct of '&' for async execution is highly > expres

Re: Built-in printf Sits Awkwardly with UDP.

ond after the last > write. Unfortunately, there's no such thing in stdio. That sounds like a bad design for a log file anyhow. Log entries should get flushed quickly, otherwise you lose the last few log entries before a segfault or signal and have fewer clues about the cause. -- Ben Pfaff http://benpfaff.org

Re: Bash source repository

d on the change that occurred. It is a waste of time to use "git mv" if some other way is easier. -- Ben Pfaff http://benpfaff.org

Re: Verbatim pasting

Andre Majorel writes: > Binding printable ASCII characters to readline functions is > convenient but it can bite you when you paste text into a shell. This also bites me from time to time when I cut-and-paste a command from an editor window into a bash terminal window. If the line that I cut-an

words in COMPWORDS vs. words in COMPREPLY

ue,...", and this seemingly odd behavior is making life difficult. Thanks, Ben. -- Ben Pfaff http://benpfaff.org

Re: functions, process substitution, bad file descriptor

On Feb 27, 2009, at 4:02 PM, Chet Ramey wrote: Ben wrote: I ran into a problem using process substitution This will be fixed in the next version. thank you! ``The lyf so short, the craft so long to lerne.'' - Chaucer i've noticed

functions, process substitution, bad file descriptor

I ran into a problem using process substitution. A much reduced version is show below. The function f2 has the problem, the function f1 does not. Are there is some facts about the life cycle of the files created by process substitution I don't appreciate? - ben bash-3.2$ ls -l /tm

Re: Memory leak when catting(/sedding/...) large binary files with backticks

he inner workings of bash, maybe it's working as intended. I just figured since it was eating my memory and not making that memory available to other programs when it was ^C'd (as you would do when you realised you'd inadvertently catted or sedded a 3GB binary file) that I'd report it. Ben

checkwinsize should be the default

Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba

[Patch] Fix QNX biuld error

There is an error on line 29 of variables.c in bash-3.1. It should read: #include not #include Attached is a patch that fixes this, although it would be easier to fix it manually. Ben --- bash-3.1/variables.c2005-11-12 20:22:37.0 -0600 +++ bash-3.1.orig/variables.c 2006-09

Segfault in bash 3.0

bash version 3.0 crashes with a segmentation fault when running this script: #!/bin/bash # Running this script crashes bash version 3.0 (and 2.05b.0(1)) function foo { local w local c c=([EMAIL PROTECTED] and stuff) echo [EMAIL PROTECTED] }

bash feature request: pushd -v, popd -v

ss of whether this request is feasible. :) Thanks, Ben Horowitz P.S. Here is version information - it is possible that this feature has been added to a newer version of bash than I have: $ bash --version GNU bash, version 2.05b.0(1)-release (i386-pc-linux-gnu) Copyright (C) 2002 Free Softwa