Welcome, Guest. Please login or register.
Did you miss your activation email?


Login with username, password and session length

Search

 
Advanced search

8043 Posts in 1856 Topics- by 2099 Members - Latest Member: roi
Pages: [1]   Go Down
Print
Author Topic: Can't CHMOD 777, can I 666?  (Read 411 times)
0 Members and 1 Guest are viewing this topic.
Falcon213
Guest
« on: May 03, 2004, 02:19:00 AM »

Like the topic says, I can't CHMOD anything to 777 on my host. I figured that since nothing in the calendarscript directory is executed, I could CHMOD everything to 666. (All directories and calendar.pl and calendar_admin.pl are 755.) When I try to lead calendar.pl or calendar_admin.pl. I get a 500 error. I checked everything in the getting started and installation sections, everything is how it should be. Any help?

Thanks.

Logged
Falcon213
Guest
« Reply #1 on: May 03, 2004, 02:30:00 AM »

Update: I also tried using the installation batch file and just letting it chmod as 777, because I think my host only won't let me execute files that are chmodded 777. Still got 500 error, though.
Logged
DanO
Moderator
Full Member
*****

Karma: 13
Offline Offline

Posts: 230

Please don't PM me. Post in the open forum.


WWW
« Reply #2 on: May 03, 2004, 12:17:00 PM »

** Still got 500 error **

Did you check the server error logs to see if a more detailed error message as reported? If it wasn't helpful and you have shell access (telnet, SSH, etc.) try running the script from there to see what errors Perl reports.

666 or 766 should be all that's necessary for the rest of the files and directories, the calendar.pl and calendar_admin.pl files and their directory to 755 (depending on your server's set up - check your host's CGI FAQs).

Whenever I've installed CalendarScript I've just unzipped the files locally, FTP'd them to the server maintaining the directory structure and just set the permissions of the calendar.pl and calendar_admin.pl files and their directory to 755. No other permissions needed to be changed on any of my installations.

Dan O.

------------------

Logged
musicvid
New Member
*

Karma: 1
Offline Offline

Posts: 8


WWW
« Reply #3 on: May 12, 2004, 08:36:00 AM »

**No other permissions needed to be changed on any of my installations.**

Yes, and it's easy for beginners like me to be lured into changing a bunch of permissions before even trying out the script, or before checking other simple problem areas like paths or transfer mode (just putting it on "auto" won't work).

Cgi-bin folders are often preconfigured to accept files with the *minimum* permissions necessary for most scripts to work, which is obviously the most secure state (why give the outside world write permissions when they're usually not necessary).

Before changing everything to 777, try the default permissions and see if they work. Usually no changes are needed. The Unix Apache server I use defaults the actual folders and files with .cgi and .pl extensions to 755, and everything else to 644. Calendarscript and almost every other script I have tried works fine this way.

------------------

[This message has been edited by musicvid (edited May 12, 2004).]

Logged
Pages: [1]   Go Up
Print
Jump to: