On Friday, February 24, 2006, 10:31:25 AM, Goran wrote: GJ> Hi,
GJ> I just got my service up and running using Matt's post GJ> http://www.mail-archive.com/sniffer@sortmonster.com/msg00169.html GJ> It was simple especially since I already the resource kit installed. GJ> Now I know that this I supposed to work to get the persistent instance GJ> to load the new rulebase after a download. GJ> REM Load new rulebase file. GJ> %LicenseID%.exe reload GJ> But is there any way to query the service and ask it to tell you when GJ> was the last time the rulebase was loaded? Or what version of the GJ> rulebase it is using? By default, the persistent instance will reload the rulebase about once every 10 minutes. The reload command creates a semaphore file in the workspace and waits for it to disappear. When the persistent instance has complied it will delete the file. Therefore, the command " <licenseid>.exe reload " will generally not return until the rulebase has been reloaded. In some cases, due to a timing function bug, the persistent instance may not respond to the reload or other semaphores... however, it does still reload itself every 10 minutes or so. A sure way of reloading the rulebase if you need to force it and you suspect something isn't quite right is to restart the persistent instance. GJ> When running in peer mode this question does not GJ> arise since the instances read the file off disk so there is no problem. GJ> With the persistent instance this is not the case and I would like to GJ> know that it really is using the newest rulebase. Just to clarify a bit... in peer-server mode, a server-peer will load the rulebase, process some number of messages including it's own, and then return. So, reloads are frequent, but not guaranteed. Client-peers do not load the rulebase. The persistent instance processes many more messages than a server-peer and then reloads after it drops. Otherwise it is very much the same as an ordinary peer instance. As a rule, unless something is broken then you can be sure the new rulebase is running within about 10 minutes (by default) of when it appears in the workspace. Hope this helps, _M PS: I'm working on adding some of the version 3 features to version 2 for testing and tuning on our way to a full version 3 engine. Soon I will be coming out with incremental version 2 releases on our way to 3. I will be making instrumentation features a priority since they will be helpful while tuning and (hopefully not) debugging the new prototoypes. This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
