It's probably totally unrelated, but I once managed to freeze an
OpenBSD box after attempting to make it automagically back up stuff to
a Windows Server 2003 box. In my case, I had installed sharity-light
(a package allowing you to access CIFS/SMB shares) and I had tried to
tell it to mount the CIFS/SMB share at some mountpoint -- this is when
it froze. It turned out that pf (which I had running on the OpenBSD
box) blocked some port that was needed for proper communication
between sharity-light and Windows Server 2003. I could only
troubleshoot by first ssh-ing into the OpenBSD box, then making the
mount attempt from the actual local keyboard/monitor of the OpenBSD
box (where things duly froze) and then using the preexisting ssh
session to troubleshoot and look at what was happening with tcpdump(8)
(cf. http://www.openbsd.org/faq/pf/logging.html ). If I didn't have a
preexisting ssh console open when making the mount attempt, then I
couldn't ssh into the box anymore from the moment of it freezing
(which meant there was no way to stop the madness, not even with a
local Ctrl+C; in that case I had to power cycle the machine). But with
a preexisting ssh session un-freezing the OpenBSD box was as simple as
punching a big hole into pf.conf (or disabling pf).
Again, you don't seem to be using sharity-light (at least it's not in
your below package list), but I thought I'd tell ya anyway; maybe
something along these lines might help you or a future reader of the
archives. For the record, my above problems happened with OpenBSD 3.9
-release/i386 and the appropriate sharity-light package.
