chmod wants the mode (0777 in your example)
first. Go read the docs on this one (follow the link).
| [reply] |
Sounds to me like you've created a directory with a
newline character ("\n") in it. You should use something like
chomp to strip off the newline after you've read it
in and before you give it to mkdir.
It probably didn't happen
with the second one because there wasn't a newline
at the end of the text file.
Have fun,
rdw
| [reply] |
Ahh, yes, that would make more sense -- the chmod
command wouldn't be creating directories, would it?
Anyway, to help you clean up what you've created, try
to capture the directory name with a glob from the shell,
like ls *dirname* to see if it will list it,
then rm -ri *dirname* to delete it (substituting
whatever glob you use to find the directory, naturally).
| [reply] |
Actually, I tried and failed to get my shell to let me delete a directory with
a "\n" in it....
...but of course, since perl created the directory,
it can remove it as well.
DaWolf - it's probably easiest to just change the script to use
rmdir to undo the 'damage' before you fix the chomp bug
Have fun,
rdw
| [reply] |
Just another point perhaps worth mentioning: Who has control over what is put in each text file?
I.e. if you have users on your system that can create these files, then you have a potential security risk - it would be worth untainting or checking the files before running any system calls on it. Just a warning! | [reply] |
It kind of sounds like your loop is skipping the first line of the text file. Try putting in a print statement and see how the loop behaves.
--=Lolindrath=-- | [reply] |