Thunderstone Support Forums

We've just upgraded our version of texis for NT to 3.01.984682785.

It seems that this newer version's monitor.exe is holding open file locks a lot longer than the November 1999 version we'd had before, and this is giving us major trouble-- we periodically rename existing database folders and swap in modified ones, but we've had to resort to monitor -k to manage to do this often times

It was never a problem with the old version on texis, and I was wondering if perhaps this hold of monitor.exe's is configurable in some way? Maybe there's a .cnf value we can change to help? We really don't want to kill peoples' searches if we can help it. Thanks for the advice!

There are some .cnf settings you can set in texis.cnf. Note that monitor -k won't kill people's searches, and should be safe to do. The texis.cnf settings are:

[Monitor]
; The monitor will check the database every Removal seconds. If the
; database has been removed, or has been idle for more than DB Quiet
; seconds then the monitor will quit.

Removal = 60
DB Quiet = 120

I have 2 monitor.exe processes running that I'm not able to kill in NT. I tried using <sqlcp rmlocks force f:\mydb> and monitor -k, but those processes still remain. Is there another way programmatically to kill these processes?

Not really. It's possible they are index update processes that are updating metamorph indexes, in which case they should exit after they are done.