Thanks for the response, Neo

>>When you make a mistake like this you need to 'stop thinking GUI' and get to the command line:

I didn't use for nothing. I should've known better. But it's spilt milk. I'm looking for the mop.

>>(1) What is the user ID your web server runs when users are connecting? Hint: ps aux | grep httpd

ps - process status
aux - all interesting user oriented and no terminal processes (I think)
| pipe it to
grep - get regular expression print
httpd - match this pattern

http://rhinoseros.com/~pics/temp/psauxgrephttpd.gif

But it's still just so many numbers to me.

>>(2) Does this user ID have executable permissions for the PERL or other CGI scripts?

I don't know and I don't know how to find out.

>>(3) Does this user ID have read permissions into the HTTP document tree?

ditto.

>>These are the things that the author of your cryptic note ...

I understand that, but it puts me no closer to solving the problem.

>>FWIW: In over 15 years of UNIX and Linux work, I've never used a tool like Webmin.... it is just too much fun and a lot faster (when you get used to it) to command the shell !!

For what it's worth, I used DOS 3.3 until 1998. I did not do any networking. Earlier this year, I saw webmin in a lab setting and was not impressed. A friend is taking a course and they are stressing webmin a lot. I just bought into a dedicated server after practicing at home for a few months and the company installed webmin so I thought I'd have a look. I should've known better cuz now it's screwed things up. Running the web server and troubleshooting scripts is all well and good but it still doesn't explain to me why other read/write problems exist in ssh or ftp situations. I have no phobia with command lines nor shells. I'll add, I like unix/linux as a concept but "useful" information is just plain and simple too hard to come by.

Thanks Neo, I hope you can point me to the next step.