|
From: Phil S. <phi...@ho...> - 2001-11-02 06:53:39
|
This reminds me of the bad 'ol days of shell scripting... escaping special characters was always a black art. chuck clark wrote: > > Hmm...Kevin actually had 'sh -c "%s"' in the original code > I switched to '%s' and everything worked. And then I tried > 'sh -c %s' and that worked. I was curious and tried > "sh -c '%s'" but that failed as well. So it definitely has something > to do with the quotes. In the bash man page I found the following: > > Shell builtin commands return a status of 0 (true) if suc > cessful, and non-zero (false) if an error occurs while > they execute. All builtins return an exit status of 2 to > indicate incorrect usage. > > So I'm guessing maybe the shell is having issues quoting? I get a > return code of 2 whether I use a builtin or call a command. > > chuck > |