Problem solved. I had an *image* called "rpiece" in the current working
directory (and . in my search path). I'm not exactly sure what causes that
to spawn all these bash shells, but obviously my system was very confused.
Thanks for all the suggestions and the insights on case sensitivity.
And thanks to Mark for his runsmp script (in the benchmark package), which
does a nice job of keeping my processors busy (it's hot under my desk!).
···
On 3/5/10 8:41 AM, "Greg Ward" <gregoryjward@gmail.com> wrote:
Hi Rob,
Thomas is referring to the fact that filenames on the default OS X
filesystem are not case-sensitive, so "Foo.dat" is the same as
"fOo.DaT". If you create the former, you can refer to it as the
latter. It will still show up with the case you created it with, but
the system silently ignores case when you refer to it. You can't have
both "Foo.dat" and "fOo.dat" in the same directory -- creating the
latter would overwrite the former.
This has nothing to do with what goes into a bash script, or how
rpiece gets its options. Only on older Windows systems is case
ignored in the command line itself. I don't know when that stopped
being true, but I don't think that's true any longer.
I am as puzzled by the behavior you're seeing as everyone else.
Without having all your files and scripts, though, it's pretty
difficult to reproduce.
Weird. Normally, image files and the like aren't "executable" -- you must have had that bit set on your file, somehow, and the OS interpreted the header as a bash script. No wonder you had such a mess!
-Greg
···
From: "Guglielmetti, Robert" <Robert.Guglielmetti@nrel.gov>
Date: March 5, 2010 8:52:41 AM PST
Problem solved. I had an *image* called "rpiece" in the current working
directory (and . in my search path). I'm not exactly sure what causes that
to spawn all these bash shells, but obviously my system was very confused.
Thanks for all the suggestions and the insights on case sensitivity.
And thanks to Mark for his runsmp script (in the benchmark package), which
does a nice job of keeping my processors busy (it's hot under my desk!).
Yeah, I don't know how it could have been set as executable either, and I
already deleted the file so I can't even know for sure, but that must have
been the issue. Good times.
···
On 3/5/10 10:02 AM, "Greg Ward" <gregoryjward@gmail.com> wrote:
Weird. Normally, image files and the like aren't "executable" -- you
must have had that bit set on your file, somehow, and the OS
interpreted the header as a bash script. No wonder you had such a mess!
-Greg
From: "Guglielmetti, Robert" <Robert.Guglielmetti@nrel.gov>
Date: March 5, 2010 8:52:41 AM PST
Problem solved. I had an *image* called "rpiece" in the current
working
directory (and . in my search path). I'm not exactly sure what
causes that
to spawn all these bash shells, but obviously my system was very
confused.
Thanks for all the suggestions and the insights on case sensitivity.
And thanks to Mark for his runsmp script (in the benchmark package),
which
does a nice job of keeping my processors busy (it's hot under my
desk!).
_______________________________________________
Radiance-general mailing list
Radiance-general@radiance-online.org
http://www.radiance-online.org/mailman/listinfo/radiance-general