[SOLVED] Re: telnet ok, HTTP not

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Okay, I believe I found it. The world seems (remotely) a rational place 
again.

The problem seems to lie in the way symbolic links are translated. 
Through my ip-up scripts, I was creating symlinks for each IP using 
full paths, i.e.

ls -s /public/file/0 /public/file/$IP

That had the effect of creating the following symlink:

lrwxrwxrwx    1 14 Nov 19 16:15 128.2.66.150 -> /public/file/0

...with which the server returned a 404. BUT! When it dawned on me to 
try creating the links with a relative path and I changed my scripts 
to:

cd /public/file
ln -s 0 $IP

...which created the following in /public/file/:

lrwxrwxrwx    1 14 Nov 19 19:50 128.2.66.150 -> 0

...everything worked just fine!


Could this be a parsing problem, or were my links plain wrong?

Thank you for sticking with me through this!

- -A
- -- 
http://andrew.cmu.edu/~apapadop/pub_key.asc
3DAD 8435 DB52 F17B 640F  D78C 8260 0CC1 0B75 8265
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE92vC1gmAMwQt1gmURAnE9AJ0ZSOksWr2DuhYYBYIHeNwszfJvFQCfU6ig
RD0dO0+5SQ2CEtrPTwzcST8=
=jZB/
-----END PGP SIGNATURE-----