Mike, I fired up my album server today at home. Went to work and accessed the page(s). All the picture album icons showed up and all seemed to be working fine until I tried to click on an album of over a hundred low resolution pictures. I guess my work network gateway (with tons of security measures and firewalls builtin) really slows down the picture loading process! It never completed and for some reason timed out with a TCP error related I think to "timed out" or not responding due to network congestion. Hmmmmm. Fine,
but after that I lost total connectivity to the dump Apache service! I cannot even get into the machine anymore! So I will have to wait until I get home to reset the server. I have no idea what caused the lockup... album behaviour or flaky Apache server software behaviour. Nevertheless, that server is locked up for now and won't respond to anything. Sheesh!
Also, I think you are right about the Apache server not allowing access to the album directories. Last night I copied the thumbnail images (your originally named img), to the directory Apache server allows for document access. Before my server died on me, I had simply typed in the URL pointing to that images directory and it did indeed list an index to my browser of all the thumbnail file contents! But when I tried to browse the same images file in the apache2/images path where album.pl uses, I get a page access error that it is not there. So, indeed, it seems to be an Apache config issue and not the album software.
However, I don't have any idea at this moment as to why and what locked up my server machine after trying to browse one of my larger picture albums this morning. Even if the network was slow in transferring the pic files and timed out, that should not have knocked out and locked out the apache server! I think the apache server code is flaky now. Oh well,
learning curve(s)...
Thanks for everything!