Gossamer Forum
Home : Products : Links 2.0 : Installation -- Unix :

Complete permission listing is needed

Quote Reply
Complete permission listing is needed
Hi!
I see that most of new users have problems on setting permissions correctly.
Can any experienced user of Links script create a complete listing with ALL files/directories AND ALL permissions?
That's could solve many problems and could answer MANY questions.
(to Alex SmileThis list could also become part of installation.
Thanks
AAP


------------------
Internet Law Specialist
http://parthenis.gr
Quote Reply
Re: Complete permission listing is needed In reply to
Hi there,

The permissions you need are detailed in the readme file, but here they are again for you.

chmod 755 (-rwxr-xr-x) on all .cgi files.
chmod 666 (-rw-rw-rw-) on all files in the cgi-bin/admin/data directory.
chmod 666 (-rw-rw-rw-) on all your template files (if using the online editor)located in cgi-bin/admin/templates.
chmod 777 (drwxrwxrwx) on the hits directory
chmod 777 (drwxrwxrwx) on the ratings directory
chmod 777 (drwxrwxrwx) on the directory where Links pages will be created. probably www.yourdomains.co.uk/ ie root folder where your site files are

Hope This Helps.



------------------
Regards
MDJ
http://www.isee-multimedia.co.uk
Quote Reply
Re: Complete permission listing is needed In reply to
The Readme.txt of Links 2.0 includes this paragraph:

3. Set permissions:
chmod 755 (-rwxr-xr-x) on all .cgi files.
chmod 666 (-rw-rw-rw-) on all files in the data directory.
chmod 666 (-rw-rw-rw-) on all your template files (if using the online editor).
chmod 777 (drwxrwxrwx) on the hits directory.
chmod 777 (drwxrwxrwx) on the ratings directory.
chmod 777 (drwxrwxrwx) on the directory where Links pages will be created.


Links 2.0: Readme.txt
http://www.gossamer-threads.com/...pts/links/Readme.txt


To complete those brief instructions, I think that usual
permissions for other scripts are:

Directories
755: Cgi-bin directories
755: Read-only (for visitors) directories
777: Directories with full writing permissions

Files
755: Executable script files (.cgi, .pl)
644: Read-only (for visitors) files
666: Files with full writing permissions


Therefore, in the case of Links 2.0, the most probable permissions
are the following, if I am not wrong. Please, correct me any error.
Thank you.

These are UNIX permissions. In the case of Windows NT, "full control"
is an option that seems to work; I don't know a finer adjustment for
NT servers.


UNIX permissions for Links 2.0:

755 DIRECTORY cgi-bin/links/

755 * admin (SUBDIR)
755 add.cgi
755 jump.cgi
755 modify.cgi
755 rate.cgi
755 search.cgi
755 subscribe.cgi

755 DIRECTORY cgi-bin/links/admin/
(password protected)

755 * backup (SUBDIR)
755 * data (SUBDIR)
755 * Html (SUBDIR)
755 * Lwp (SUBDIR)
755 * templates (SUBDIR)
755 admin.cgi
755 admin_html.pl
644 category.def
755 db.pl
755 db_utils.pl
644 links.cfg
644 links.def
644 Mailer.pm
755 nph-build.cgi
755 nph-email.cgi
755 nph-verify.cgi
755 site_html.pl
755 site_html_templates.pl
644 Template.pm
644 Validator.pm

755 DIRECTORY cgi-bin/links/admin/backup/

644 index.html

755 DIRECTORY cgi-bin/links/admin/data/

777 * hits (SUBDIR)
777 * rates (SUBDIR)
666 categories.db
666 categoryid.txt
666 email.db
666 links.db
666 linksid.txt
666 modified.db
666 url.db
666 validate.db

777 DIRECTORY cgi-bin/links/admin/data/hits/

666 index.count

777 DIRECTORY cgi-bin/links/admin/data/rates/

666 index.html

755 DIRECTORY cgi-bin/links/admin/Html/

644 Entities.pm
644 HeadParser.pm
644 Parser.pm

755 DIRECTORY cgi-bin/links/admin/Lwp/

755 * Parallel (SUBDIR)

755 DIRECTORY cgi-bin/links/admin/lwp/Parallel/

755 * Protocol (SUBDIR)
644 Protocol.pm
644 UserAgent.pm

755 DIRECTORY cgi-bin/links/admin/lwp/parallel/Protocol/

644 ftp.pm
644 http.pm

755 DIRECTORY cgi-bin/links/admin/templates

666 add.html
666 add_error.html
666 add_success.html
666 category.html
666 cool.html
666 detailed.html
666 email.html
666 email_error.html
666 email-add.txt
666 email-del.txt
666 email-mod.txt
666 home.html
666 link.html
666 modify.html
666 modify_error.html
666 modify_success.html
666 new.html
666 rate.html
666 rate_error.html
666 rate_success.html
666 rate_top.html
666 search.html
666 search_error.html
666 search_results.html

777 DIRECTORY pages (or root to build categories)

644 background.gif
644 links.css

(There are details on this last 777 permission
in the links.cfg file).

Quote Reply
Re: Complete permission listing is needed In reply to
Note: It seems that the Lwp directory must be LWP (all capital letters). This only affects LWP directory. (Used by Links 2 to verify links, etc.). The rest of the previous list seems to be all right.

Last edited by:

Juan G: Oct 24, 2001, 11:22 AM
Quote Reply
Re: [Juan G] Complete permission listing is needed In reply to
Links 2.1 doesn't use the LWP directory.
Quote Reply
Re: [RedRum] Complete permission listing is needed In reply to
Well, in this case, this is only for Links 2.0.

In this version, for example for the quick link check, nph-verify.cgi uses UserAgent.pm at LWP\Parallel to verify links. If nph-verify.cgi does not find LWP, then it uses an alternative but slow method after the following error message:

"Unable to load Parallel User Checker. System Error:
Can't locate LWP/Parallel/UserAgent.pm in @INC (...) [snip]
Using IO::Socket method instead."

Renaming Lwp to LWP works well instead. (This has happened with my website today, on a Unix server).