i think there were actually 2 problems. the original problem on my 64-bit (home) machine is still present. when i try to run the above shell script on the 64-bit machine i get this error: --- malloc: ../bash/dispose_cmd.c:241: assertion botched free: called with unallocated block argument Aborting...Aborted --- if i add the "#!/bin/[ba]sh" line to the script it does work fine. "ulimit -a" output: --- core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 40448 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) unlimited virtual memory (kbytes, -v) unlimited file locks (-x) unlimited --- for my work (32-bit) computer the cause (i suspect) was the "/usr/share/binfmts/jar" file; when running a script from a bash ssh shell (without the "#!/bin/[ba]sh" line), the process locks up with around 50% CPU and must be killed externally. i could recreate this by simply SSHing from this computer to another computer, then back to my work computer, and running the script. removing java from this computer solved this problem, and this computer does not exhibit the crash problem of my home computer (above). "ulimit -a" for this computer is: --- core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 8187 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 8187 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited ---
-- shell scripts cannot run from bash https://bugs.launchpad.net/bugs/299690 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
