SYSMGR

We're a bunch of Computers: Diana, Daphne, and Dido, called the 3D-cluster, running OpenVMS, Io running OpenVMS as well (in some obscure role in the network) Aphrodite, Athene and Irene running WindowsXP-Pro (SP2, of course) and Cerberus at the edge of the Network, with Charon, also running Linux, as standby. SYSMGR takes care of us.

Monday, July 31

31-Jul-2006 (update)

WASD
Well, it works - using IP address in stead of name. Thought so! As long as things are kept apart, that is:
In HTTP$CONFIG I specified:

[Service]
http://192.168.0.11:82 for www.grootersnet.nl
http://192.168.0.12:82 for homedesk.grootersnet.nl
http://192.168.0.13:82 for webmail.grootersnet.nl
http://192.168.0.200:82 for anything else (for the time being)

and in httpd$map, I specified a mapping file for each of them:

# www.grootersnet.nl
[Includefile] ht_root:[local]www_grootersnet_nl.conf
# homedesk.grootersnet.nl
[Includefile] ht_root:[local]homedesk_grootersnet_nl.conf
# webmail.grootersnet.nl
[Includefile] ht_root:[local]webmail_grootersnet_nl.conf
# wasd.grootersnet.nl
[Includefile] ht_root:[local]wasd_grootersnet_nl.conf

each of the giving the required mapping like this:

#[[www.grootersnet.nl:82]]
[[192.168.0.11:82]]

pass /* /web_disk2/public/*
pass / /web_disk2/public/

set * map=root=/web_disk2/public/

Not yet complete since scripting directories are currently missing (causing the counter (wwwcount.exe) on these pages to fail) but everthing else seems to be working - once file protection has been set correctly:

$ set sec/acl=(id=HTTP$SERVER,access=EXECUTE+read) web_disk2:[public...]*.*;*

Same applies to the other directories.

Even with this minimal configuration, the increase in speed is VERY NOTICABLE.

Next, getting everything to work this way, including scripting. Stay tuned!

31-Jul-2006

Actually
there is nothing really interresting to report. During holidays - and after that - Diana kept up and running even when temperatures raised to unhealthy heights of over 35 degrees Centigrade. Just the occasional spam (in comes in by numbers - need to get the real addresses of the backwardly unresolvable domains) and spurious attempts to run PERL and PHP on the webserver where the attempted applications don't exist. No FTP atempts at all, for weeks now. Do they finally learn?
Still have to create a script to scan the weblogs for "bad requests" as mentioned, but there is so much to do...
WASD
for one thing. I am attempting to transfer my webs to WASD - on port 82, for the moment (which cannot be accessed from the outside), it works fine but accessing www.grootersnet.nl:82 fails with a 404 error: cannot find the server. But that could well be a router issue since port 82 is not mapped. If that is even the case when requested from the local network, it's nasty but workable when using a local address. One more thing to try. If any of the webs could be accessed that way (that is: without a problem) I will rename all services to the proper ones - and to port 80, so I'll be running WASD then.
Well, there still are a few hicks in PHP and PERL but these are of less concern - at the moment.