Fixing bash script bogosity - help?

[Martin Langhoff]

On Tue, Apr 28, 2009 at 12:03 PM, Ignacio Vazquez-Abrams
<ivazqueznet at gmail.com> wrote:
> But if you're willing to let go of this futile quest to keep $CMD a
> string then you'll find that it can be done:

Your example doesn't work. I don't care about keeping $CMD as a
string, I think you are misunderstanding the problem. We need to build
it as a string to provide it as a single parameter value. This is
because we want to run the command with all properly escaped params
under runuser.

cheers,


m
-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff