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

Seems like a simple problem with paths!! PLS help!

Quote Reply
Seems like a simple problem with paths!! PLS help!
Hello

I decided to reinstall Links 2.0 and start from scratch. I want to try and troubleshoot this thing step by step as I'm sure it's a simple error that has me stumped.

I installed everything correctly, all permissions are set correctly, all files uploaded in ASCII. I have successfully accessed the admin.cgi thru my browser, and all menu options above "Building" work flawlessly.

Now, when I try to build, I can't from the web, which may be a shell problem. But that's not my concern Smile furthermore, when I try to build from telnet, I get this error.

Code:
Error including libraries: Can't locate /usr/local/etc/httpd/htdocs/dist/lin
ks/admin/db_utils.pl in @INC (@INC contains: . /usr/local/lib/perl5/i386-bsdos/5
.00404 /usr/local/lib/perl5 /usr/local/lib/perl5/site_perl/i386-bsdos /usr/local
/lib/perl5/site_perl .) at ./nph-build.cgi line 31.


Now.... my links.cfg looks like this:

Code:
# PATH and URL of Admin CGI directory. No Trailing Slash.
$db_script_path = "/usr/local/etc/httpd/htdocs/dist/links/admin";
$db_dir_url = "http://www.bill.co.uk/dist/links/admin";

# URL of User CGI directory. No Trailing Slash.
$db_cgi_url = "http://www.bill.co.uk/dist/links";

# PATH and URL of Pages to be built. No Trailing Slash.
$build_root_path = "/usr/local/etc/httpd/htdocs/dist/links/pages";

I dont understand why nph-build.cgi cannot find that file, when the path designated in links.cfg is obviously being used correctly by the admin script as well as most others I have accessed from the web. Just nph-build.cgi that gives the error so far! I find that nph-build.cgi works correctly if I include the "/usr/home/bill" at the beginning of my full path in links.cfg (I am running on a virtual server).... but then all other scripts such as admin.cgi give errors! I don't know if I have to tweak a script or what.

Is there a simple resolution to all of this? Alex?? Bobsie?? hehe..Please, I love the potential this script is showing already and would love to see it work! Let me know if I can post anything else of help.

[This message has been edited by JNman (edited May 19, 1999).]

[This message has been edited by JNman (edited May 19, 1999).]
Quote Reply
Re: Seems like a simple problem with paths!! PLS help! In reply to
In nph-build.cgi:

Quote:
require "links.cfg"; # Change this to full path to links.cfg if you have problems.

Try changing that to:

Quote:
require "/usr/local/etc/httpd/htdocs/dist/links/admin/links.cfg"; # Change this to full path to links.cfg if you have problems.

I hope this helps.

[This message has been edited by Bobsie (edited May 19, 1999).]
Quote Reply
Re: Seems like a simple problem with paths!! PLS help! In reply to
Hello,

I tried changing the code. Now, when I execute nph-build.cgi, it replies:

Code:
Error including libraries: Can't locate /usr/local/etc/httpd/htdocs/dist/link
s/admin/links.cfg in @INC (@INC contains: . /usr/local/lib/perl5/i386-bsdos/5.00
404 /usr/local/lib/perl5 /usr/local/lib/perl5/site_perl/i386-bsdos /usr/local/li
b/perl5/site_perl .) at ./nph-build.cgi line 30.

Make sure they exist, permissions are set properly, and paths are set correctly.


I don't get it. Seems some scripts recognize the full path (admin.cgi), yet others don't (nph-build.cgi). By the way, that path should be correct, it even shows up in the SCRIPT_FILENAME variable when debugging. It seems to be something about nph-build.cgi, but I am not as affluent with CGI code as some of you. Smile

Thanks for any help!
Quote Reply
Re: Seems like a simple problem with paths!! PLS help! In reply to
Try putting "/usr/home/bill" at the beginning of that path in nph-build.cgi and see if it works. That path would only then be used by nph-build.cgi and not the others.

If it does work (or even if it doesn't), I suggest you have a long talk with your ISP to find out why your paths are not working correctly. Something is definitely not configured right on your server.