in reply to Problem with module using Crypt::OpenPGP

If the "full path" is not the solution, then the next (standard) answer is: did you check the file permissions? The webserver runs not under your user id and has its own permissions.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

  • Comment on Re: Problem with module using Crypt::OpenPGP

Replies are listed 'Best First'.
Re: Re: Problem with module using Crypt::OpenPGP
by DamnDirtyApe (Curate) on Aug 17, 2003 at 18:58 UTC

    Thanks, I tried that too; I set the permissions to 0666, but no luck. :-(


    _______________
    DamnDirtyApe 
    Those who know that they are profound strive for clarity. Those who
would like to seem profound to the crowd strive for obscurity.
            --Friedrich Nietzsche
[reply]

      ...0666? Doesn't that mean world readable and writable, but not executable? Shouldn't you try 0755?

      Hope this helps.

      antirice    
      The first rule of Perl club is - use Perl
      The       ith rule of Perl club is - follow rule i - 1 for i > 1

[reply]

        The file in question is an ASCII text file containing the GnuPG public key. There's no reason for it to be executable. But, I tried it just in case, and no go. :-(


        _______________
        DamnDirtyApe 
        Those who know that they are profound strive for clarity. Those who
would like to seem profound to the crowd strive for obscurity.
            --Friedrich Nietzsche
[reply]

In Section Seekers of Perl Wisdom