Is it possible that it is a permission issue??
though wrong path seams more likely. If you can see them with ls then the path shouldn't be the problem. could you give us ls -al printout. | [reply] |
Argh... I am sorry to bother you guys... Whitespace beeing the problem. If you run the program with ... -o output ... it works fine but if I need to run it with Perls system command then it has to be ... '-o', $name, ... and not ... "-o $name" ... else it would introduce whitespace before the name of the file.
| [reply] |
What you think your pwd/cwd is different from what your program thinks are its pwd/cwd; your files are probably in a different folder
| [reply] |
This may sound silly, but it works: print STDERR the actual string that you intend to execute, then copy/paste that literal string to a new terminal session and try it. Inevitably, you will right-away discover one of two things: that the string isn’t as you thought it would be, or that when run by an actual shell it produces a syntax error of some kind. So, avoid guessing ... try it. (No one will see you say, “d’oh!”)
| [reply] |
Hi RuntimeError,
..I used the system command to run an external program which itself writes some other files according to given parameters..
Am only wondering, why can't perl do the writing of the files? Why use another program called within perl? If the job is simple enough for perl to handle, why all the troubles? Just thinking though!
If you tell me, I'll forget.
If you show me, I'll remember.
if you involve me, I'll understand.
--- Author unknown to me
| [reply] |
