Just want to share with everyone a problem and workaround I found for installing on VServers using install.cgi via telnet. Install seems to go smoothly but when you attempt to run setup for the first time all you get is server errors. This results from physical server paths instead of virtual server paths being built into the scripts during install.

When a VServer client starts a telnet session, the default directory they are taken to is /usr/home/username. The problem with this is the virtual directory they are in is /. Install.cgi wants to build other scripts using the /usr/home/username prefix in the server path and won't let you install if you try to remove it during the install. So, the way you must leave it is
/usr/home/username/usr/local/etc/httpd/[htdocs or vhosts]/domain... instead of trying to edit it to
/usr/local/etc/httpd/[htdocs or vhosts]/domain...

Location of perl can stay at /usr/local/bin/perl5 as there are both physical and virtual paths to it.

When the install completes, FTP the entire thing locally with directory structure intact. Using windoze explorer advanced file find, I searched for all files in and below the links cgi directory containing the text "/usr/home/username" and used the replace function in wordpad to remove this prefix from all server paths in all files it found containing it. The offending text is found in all scripts in the links main /cgi-bin directory, /cgi-bin/admin, cgi-bin/admin/Links/ConfigData.pm and cgi-bin/admin/mysqlman/mysql.cgi.

When finished editing, upload back to the server in ASCII and run http://domain/path_to_links_cgi_directory/admin/setup.cgi.

Now, if I can just figure out why nph-build does not work I'll be a happy guy!

Mark Brasche
http://SurfSafely.com/