Re^2: (jptxs) perl 5.6.1 on AIX 5.1 doesn't open() a $var, only real path

[jptxs]

Yes, that was a typo. I did set a bunch of debug in the script and everything looked fine with the path being passed.

what could the umask do? If I create a file I own, I can't see how a umask would prevent then editing that file myself. Maybe I'm missing something... I will check it, though; and see what's happening there.

[bluto]

what could the umask do? If I create a file I own, I can't see how a umask would prevent then editing that file myself.

On AIX I've seen problems with giving garbage mode bits (e.g 0) to the equivalent of a sysopen call cause problems later accessing the file, even for the owner. I thought that there was a slight chance that perhaps a bad umask could cause the same problem (though very unlikely). But even why I try that I can't reproduce it (i.e. this works fine for me on perl 5.8.5...)

% umask 777
% perl -le 'open my $fh, ">foo" or die "open:$!"; print $fh "hello" or
+ die "print:$!"; close $fh or die "close:$!"'