So halog didn't work in the adaq account. Better yet, /usr/bin/wish doesn't work from the adaq account at all. It terminates with
Application initialization failed: /adaqfs/coda/2.6.2/common/lib/tcl7.4/tclIndex isn't a proper Tcl index file
This turns out to be due to the environment variable TCL_LIBRARY, which is set unconditionally by $CODA/.setup. This breaks all system TCL/TK stuff unless one uses the binaries in $CODA/Linux/bin. Too bad that wish is named wish4.0 in that directory. Typing "wish4.0" works just fine from adaq.
To fix this, I unset TCL_LIBRARY (and a few related variables) in the halog startup script, /group/halla/www/hallaweb/html/halog/src/halogentry. I also added an alias to ~adaq/.tcshrc
This fixes halog, but not any other TCL/TK stuff we may have running under adaq.
Of course, this begs the question, why does CODA stomp all over the system's TCL/TK setup? Why don't CODA executables that need TCL not set their environment at their own startup time? Oh well.