Earl R Shannon wrote:
Hello,
We are preparing to migrate an older cyrus install to a newer one. One of the things we are having to address are the sieve scripts being compiled to byte code.
We've not yet found an complete answer to how a script goes from "text on my client" to "byte code on the server".
We've been using text scripts and do know that sievec makes a script into byte code, but the tools we have don't work on the new server as the making stuff into byte-code part seems to be skipped.
Are you using home-grown tool?
From the client side, the new timsieved should present the text script and then compile it when resubmitted by the client.
If you want to compile all of the existing scripts, I'd use tools/masssievec.
-- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
