It really, really helps to post a code fragment that demonstrates the problem. The challenge with trying to describe what you're doing is that if you have blind spots, they carry over into your description. With code, we have something objective to analyze.
Without code to look at, I can't tell from your description whether you're trying
mkdir("/blah/10", 0nnn) or die "/blah/10: $!";
or
chdir("/blah") or die "/blah: $!";
mkdir("10", 0nnn) or die "10: $!";
One of these is fundamentally wrong. The other should work, or should tell you why it isn't working.
| [reply]
[d/l]
[select] |
the first. and the second. and File::Path's:
mkpath( '/blah/10' , 0 , 0775 ) or die "$!";
they all return the same error, which I mentioned in the original post. the issue isn't how I'm implementing the mkdir, it's the fact the mkdir is creating a file instead of a directory.
personally, I'm at a loss to see how any implementation of mkdir can explain what I'm seeing. which, of course, might explain why I'm here in the first place.
| [reply]
[d/l] |
use File::Path;
foreach my $n ( 0 .. 12 ) {
mkpath("/blah/$n", 1, 0755) or die "$n: $!";
}
do you still get a bogus "/blah/10". And if so, does "strings /blah/10" provide any hints about what the file is?
| [reply]
[d/l] |
Have you considered using truss or strace, whichever your system has, to see what is actually going on? This might give a clue or two.
--traveler | [reply] |
I'm not familiar enough with either truss or strace to get any helpful information I'm afraid. and, of course, I'm under something of a time crunch... or I'd work on fixing that now. thanks in any case...
| [reply] |