Forums / Addon Payment Modules / Google Checkout: Why 777 for *.log files ???

Google Checkout: Why 777 for *.log files ???

Locked

Results 1 to 2 of 2

This thread is locked. New replies are disabled.

20 May 2009, 8:35 PM

neckwood

New Zenner

Join Date:: May 2009
Posts:: 4
Plugin Contributions:: 0

Google Checkout: Why 777 for *.log files ???

The instructions for installing Google Checkout read:

Make sure you set the file attribute to 777 for
/googlecheckout/logs/response_error.log and /googlecheckout/logs/response_message.log files.
Why on earth would anyone want to set the +x bit for a text file???

26 May 2009, 7:27 PM

zcnb

Zen Follower

Join Date:: Jun 2008
Posts:: 338
Plugin Contributions:: 0

Re: Google Checkout: Why 777 for *.log files ???

Your observation is correct: a text file need not be executable. I actually checked these 2 files with permissions set to 644 and GCO works just fine (and updates those files).
Even with 777 they are well protected because of .htaccess and the 0-length index.html files in that directory.

HTH :smile: