Sonic.net

Hello,

In web server applications (like php) one sees paths of the form:

/nfs/www/WWW_pages/chongo/isthe.com

However when logging into to a sever via ssh, one sees paths of the form:

/nfs/WWW_pages/chongo/isthe.com

Please add the following symlink to my filesystem:

ln -s . /nfs/www

Or please do:

mkdir -p /nfs/www
ln -s /cgi-bin /nfs/www/cgi-bin
ln -s /ftp /nfs/www/ftp
ln -s /web /nfs/www/www_pages
ln -s /web /nfs/www/WWW_pages

so that from an ssh based login, /nfs/www/WWW_pages resolves to /nfs//WWW_pages.

Thank you.

chongo (Landon Curt Noll - sonic username: chongo) /\oo/\

Hello,

Had anyone else noticed the difference between what the web server sees and the filesystem one observes when you ssh into to sh.sonic.net?

We have a php program that runs successfully via a URL in the web server. However when we try to run the same php program when ssh-ed into sh.sonic.net, the program fails. The reason is that the php program seems web paths that start with:

/nfs/www/WWW_pages/...

whereas when I login via ssh, I see paths of the form:

/nfs/WWW_pages/...

The lack of a /nfs/www means I cannot debug the code directly from a shell. It means that code that runs via the web server cannot work under the shell.

Either /nfs/www should point at /nfs, OR there should be a /nfs/www directory with suitable symlinks for cgi-bin, ftp www_pages, WWW_pages in order to fix this problem.

I cannot do this because /nfs is owned by root, someone from Sonic needs to fix this.

chongo (Landon Curt Noll) /\oo/\

Hello,

The path you can use for this situation would be: /nfs/WWW_pages/username/site.com

This should work fine for both shell and http. We have tested both with no issues.

Thank you,

Thank you