[Once again, apologies for the crosspost...] I've released atalklogger 1.2.1, which fixes a couple of bugs in version 1.2. The important one is that 1.2 would crash if papd was started after atalklogger. Since papd starting after atalklogger is the recommended configuration, this could be problematic. Version 1.2.1 can be downloaded from <http://prism.simplenet.com/atalklogger.tcl.gz>, or you can apply the patch below. --Benjamin Gilbert =========================================================================== === --- atalklogger.tcl.old Thu Apr 20 17:58:24 2000 +++ atalklogger.tcl Sat Apr 22 14:32:07 2000 @@ -41,6 +41,12 @@ # and pre-2.1.4/2.2.0; it may work with earlier or later versions, but your # mileage may vary. # +# v1.2.1 -- 2000.04.22 +# - A bug in proc line would cause atalklogger to crash if papd was +# started after atalklogger (note that papd starting after atalklogger +# is the recommended behavior). Sigh. Fixed. +# - Errors encountered during initialization could cause atalklogger to +# crash without logging an error. Fixed. # v1.2 -- 2000.02.25 # Cleaned up (relatively speaking) for public release # v1.1 -- 2000.01 @@ -121,7 +127,7 @@ global pidfile doafpstatus dopapstatus dohosts progversion outlogperms afpstatperms papstatperms # Define atalklogger's version number - set progversion "1.2" + set progversion "1.2.1" # Check Tcl version. if [catch {package require Tcl 8.0} error] { @@ -616,7 +622,7 @@ # and the connections actually would have been shot the previous # shutdown (this might be necessary if papd hadn't properly # shut down) - unset papdata + catch {unset papdata} writestatus } } @@ -658,7 +664,10 @@ # PROGRAM STARTUP ########################################################################### ##### -initialize +if [catch {initialize} err] { + syslog err "initialization failed: $err" + shutdown 1 +} set breakeventloop "" vwait breakeventloop
