That was me, and I am STILL having some wierd script problems under 2.1.14.
The following is taken directly from an xterm running bash under 2.0.27,
and demonstrates the correct behavior:
Under 2.0.27, the script identifies itself, via the /proc interface,
as "scum" - somewhat imprecise as the interpreter's identity is
hidden. Under 2.1.14, BOTH the interpreter AND the interpreted
program name are listed, for greater precision. Doing 'ps -ax' will
show you "bash /some/path/scum". Unfortunately, in your case, you
have specified arguments to PS (-acux) that tells PS to omit the
arguments to the running program, reducing your PS output to just
"bash".
It's not a bug; it's a feature. :-)
Kris