The Fugue

So you want to start up a screen session with multiple processes running in multiple windows, e.g. for monitoring logs. And you want to do it on reboot.

# $HOME/backuplogs.screenrc
screen /opt/tivoli/tsm/client/ba/bin/dsmadmc
screen -t dsmserv ssh tea 'tail -f /var/log/dsmserv/current; bash -l'
screen -t tea ssh tea 'tail -f /var/log/dsmsched/current; bash -l'
screen -t marvin ssh marvin 'tail -f /var/log/dsmsched/current; bash -l'
screen -t vogon ssh vogon 'tail -f /var/log/dsmsched/current; bash -l'
screen -t dent ssh dent 'tail -f /var/log/dsmsched/current; bash -l'
screen -t prefect ssh prefect 'tail -f /var/log/dsmsched/current; bash -l'

# crontab entry
@reboot screen -dmS backuplogs -c $HOME/backuplogs.screenrc

I've been struggling with how to get IE to do the wpad thing, and found crazy log entries like this:

172.16.59.232 - - [17/Apr/2004:17:40:57 -0600] "GET /wpad.da HTTP/1.1" 304 - "-" "Mozilla/4.0 (compatible; MSIE 6.0; Win32)"
172.16.59.232 - - [17/Apr/2004:17:41:24 -0600] "GET /wpad.da HTTP/1.1" 304 - "-" "Mozilla/4.0 (compatible; MSIE 6.0; Win32)"

Yes, that's from IE (which is apparently pretending to be Mozilla). Note that it's trying to get wpad.da, not wpad.dat. So I symlinked wpad.dat->wpad.da and it still didn't work. Google wasn't much help; most people were successful with just a symlink or copy. Finally I noticed the problem: I had a case mismatch in the name of my function, and a missing paren. Compilers and run-time syntax errors have spoiled me I guess. Now if I could just get IE to time out that cache...

In the meantime I did the windows update thing and got some kind of service pack or patch or something. Nothing that indicated IE would be changed, but apparently it was because IE is now properly requesting wpad.dat again.

Incidentally, if you're trying to configure dansguardian you need to test it, right? Well it's odd that there aren't more test files out there. This one works nicely for me: http://falcon.fugal.net/dgtest.html.

I was migrating a bind9 setup from Debian to SuSE and couldn't get the transfers to work. To make a long story short I had to put ipv6 addresses in my allow-transfer entry, e.g.:

allow-transfer {
    ::ffff:172.16.59.5; 172.16.59.5;
};

I have no idea whether the second ipv4 entry is really necessary but I don't want to be burned.

A probably-preferable alternate solution is to comment out the line:

listen-on-v6 { any; };

and leave the allow-transfer the way it was (ipv4-style).