True, but you seem to imply that
/a/path/to/remote/log/file/on/machine/c
could not map to a remote file as the OP claimed, and that's not true. All of the protocols you mentioned can be integrated into the file system. In fact, you didn't list SMB and NFS which are often if not always integrated into the file system.
It could be that the OP just made up a path and hoped it would somehow allow him to access a remote file, in which case HTTP, SFTP, etc would prove to be potential solutions.
But here on, I'm going to assume the path the OP is using should access a remote file. A good way to verify this is to check if it works outside of Perl, say by passing it to ls/dir. If not, then there's no reason to expect it to work in Perl. However, if it does work in the shell, you should have every expectation that it will also work in Perl.
Some things to check:
- Can you list that file with ls/dir?
- Are you sure the string you are passing to open is the same you are passing to ls/dir?
- Is the Perl script run by a different user (with different permissions) than the one as which you ran ls/dir?
It might help to know why open failed by including $! in the error message.
|