<pathbin>/bin/sm not found?

[Russ Allbery]

Julien Oster <joster+inn at soft-research.de> writes:

> Just after pressing the send button I noticed the strange matter that
> the error message in fact states the command name with it argument as
> the file name. I then looked at the parsecontrol-script and saw the
> following:

> SM="${PATHBIN}/sm -q"

> I'm pretty sure that causes the problem, because since the entire
> command is enclosed in quotes my OpenBSD shell might see it as the file
> name. I then changed the above line to the following:

> SM=${PATHBIN/sm
> SMARGS=-q

> and replaced every further occurence of ${SM} in the script to ${SM}
> ${SMARGS} (I think just removing the quotes might also have done the
> trick, but I think this solution is cleaner)...

Given that ${SM} is used unquoted, this should be equivalent, since
variable interpolation should happen before argument parsing (as I
understand Bourne shell syntax).  But OpenBSD is apparently (from another
report of other problems) using pdksh as it's /bin/sh, which is both old
and known to be buggy.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>