Hello Andy,
Saturday, October 4, 2008, 12:28:44 PM, you wrote:
|
> |
HI Pete, Thanks for your feedback. I had to create the UpdateReady.txt file before I was able to test my update script from the command line – but I didn’t realize that I would be created in the Workspace folder. Without that information, one cannot adapt the update script to one’s needs. Since the server always creates UpdateReady file in the Workspace folder and always expects the .SNF file in the Rulebase folder, it’s pretty safe to say that anyone using the getRuleBase.cmd would absolutely have to add the Workspace and Rulebase paths – otherwise they can’t possibly find the UpdateReady file and the script will just exit OR it will not place the SNF File where the server will find it. Anyone who has their own update mechanism clearly doesn’t fall under this discussion at all. My conclusion is, that the current getRuleBase.cmd only handles the case when there are no separate directories – but the with the changes I made, the getRuleBase.cmd would allow a user to define separate directories at the top of the script (if that’s how they configured things) and thus correctly handle a SINGLE as well as separate directories. In my opinion, that is the more “correct” behavior. |
I'm still trying to think of a way to describe this modification so that it makes sense without causing lots of confusion.
Since we're trying to reach a larger audience these days we've created a generalized approach and built an installer that configures SNF, Declude, mxGuard, and MINIMI on IMail, SmarterMail, and even a "generic" (roll your own) configuration.
The installer performs upgrades from the previous version as well.
The idea is that more folks won't have to do any tweaking at all.
Your proposed getRulebase works great for your structure-- and I agree it's a nice idea to have a WORKSPACE_PATH and RULEBASE_PATH variable.. BUT I'm having a hard time figuring out a way to include those and their various options without adding a lot of confusion and complexity...
The existing getRulebase script works perfectly when used with the installer and nobody has to touch it.
My best thinking at the moment is to perhaps do something like this:
|
REM ----- Edit This Section --------------------------------------------------------- SET LICENSE_ID=licenseid SET AUTHENTICATION=authenticationxx SET SNIFFER_PATH=D:\IMail\declude\SNF REM Modify the next two lines if you modify SNF's directory structure. SET RULEBASE_PATH=%SNIFFER_PATH% SET WORKSPACE_PATH=%SNIFFER_PATH% REM ------------------------------------------------------------------------------------- |
Of course doing that would mean rewriting our installer too (Since it needs to modify/generate the getRulebase script.
For the immediate future this discussion is archived and searchable and I will add a task to the web site project to describe some of these getRulebase.cmd scenarios.
How does that sound?
_M
--
Pete McNeil
Chief Scientist,
Arm Research Labs, LLC.
############################################################# This message is sent to you because you are subscribed to the mailing list <[email protected]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
