gossamer threads

[gwlubin]

48hrs later gossamer is still not working, it started to to work now I am just getting 500, and it is making me crazy.

it there such a thing as a faulty cgi-bin? or is it always paths/permissions?

g/

[Armand]

having just installed it a couple days ago... my first install too (other than an ubb upgrade)... I would say it would be the paths and permissions.

Not that I am huge help but I would imagine you'd have to chmod your whole cgi-bin directory wrong to mess it up no?

worst part for me was the templates and style sheets thing.

[This message has been edited by Armand (edited 04-19-99).]

[Del]

Actually, if there is any file inside the cgi-bin directory, or subdirs of that, which is chmodded any higher than 755 the whole cgi-bin will break.

Here's what always gets me: if you've made any new directories inside your cgi-bin, make sure they're chmodded 755. If they're not, it can 'break' every script in the cgi-bin (happens to me all the time...)

Del

[Armand]

Ah.. leave it to Del to teach us how to break the cgi-bin. ..I'll have to resist the temptation to see if it really does break it.

On the Links thing I managed to even find some attributes within the files to get rid of some things I didn't like about the look of the script, like the fact that the font color of descriptions was coded into script and not templates. Hehe... I'm enjoying this hacking things too much!

[Justin]

Funny thing is I never play with permissions on scripts or directories other than any special data directories I need... as for cgi-bin subdirectories and scripts, they automagically are at the correct mode when created/uploaded.

Never messed with Gossamer Threads, but since so many people seem to have trouble with it I might just install it and see what's so tricky about it...

------------------
Justin Nelson
FutureQuest Support

[kteicher]

Generally with Links there is a config or permissions problem. I just installed it on my site in just a few minutes. Here is the config setup I used:

# Paths and URL's to Important Stuff
# --------------------------------------------------------
# PATH and URL of Admin CGI directory. No Trailing Slash.
$db_script_path = "/big/dom/xyourdomain/cgi-bin/links/admin";
$db_dir_url = "http://yourdomain.com/cgi-bin/links/admin";

# URL of User CGI directory. No Trailing Slash.
$db_cgi_url = "http://yourdomain.com/cgi-bin/links";

# PATH and URL of Pages to be built. No Trailing Slash.
$build_root_path = "/big/dom/xyourdomain/www/links";
$build_root_url = "http://yourdomain.com/links";

# PATH and URL of What's New page. No Trailing slash.
$build_new_path = "/big/dom/xyourdomain/www/links/New";
$build_new_url = "$build_root_url/New";

Follow the instructions for the file permissions. Also with the above set up make sure you build a directory called links under the /www directory.

If you need more help let me know, or I would be happy to install it for you.

Keith
http://webmasterexchange.com/links/

[This message has been edited by kteicher (edited 04-19-99).]

[Dean B]

Graham,
I keep responding to your emails bud offering to help you out. The offer's there ...



------------------
Regards, Dean.
**DMCity Web Board**
www.dmcity.com/cgi-bin/ubb/Ultimate.cgi

[hearts]

it there such a thing as a faulty cgi-bin? or is it always paths/permissions?

I suppose there is a such thing as a "faulty cgi-bin"... HOWEVER, if we are talking about services at FQ --- that answer is NO.

I cannot stress enough, that it is very important to understand your domain structure when installing scripts. Most installations of pre-written scripts fail cuz of ...

1) You set your permissions wrong -- chmodding

2) Your paths are incorrect

What is the exact error message you recieve when running the script? What is the exact error message in your web server's log?

Just take your time, and try again.

-------------
hearts
-----

[Deb]

Without a cgi-wrapper anything that is coded to be 777 would not work as 755. But since we do have the cgi-wrapper in place this is what allows files that are normally set at 777 to work as 755 as they should.

Common rule of thumb would be .. if it says set it to 777 and it's supposed to be inside the cgi-bin... set it to 755 and you'll be ok

Deb

[This message has been edited by Deb (edited 04-20-99).]

[kteicher]

I was able to install Links successfully for Graham this morning. He is up and running with no problems. I'm not sure what went wrong with his original install but I did a fresh one and all worked on the first try.

Keith