Re: A few configuration bugs in razor-2.72

On 6/24/05, Gary V <[email protected]> wrote:

[snip]

> 
> This is how I configure amavis, it may possibly get you going:
> 
> As root, run
>  razor-admin create
>  razor-admin register
> 
> It should create /root/.razor/razor-agent.conf
> 
> edit /root/.razor/razor-agent.conf
> and explicitly set razorhome:
> 
> razorhome = /var/amavis/.razor
> 
> then copy root's entire .razor directory to amavis:
> 
> cp -r /root/.razor /var/amavis
> 
> This part is probably unnecessary, but I do it anyway:
> razor-admin -create -home=/var/amavis/.razor
> 
> Both root and amavis will use razorhome = /var/amavis/.razor

Thanks Gary. I have no problem in terms of working around the issues
that I originally reported. Your suggestions were kindly welcomed,
nonetheless ;)

While we're on the topic, I've discovered another inconsistency
between razor-2.61 and razor-2.72 :(

With these tests, the conditions were precisely the same as in my
original tests with one exception: I created a pre-existing "master"
configuration file at: /etc/razor/razor-agent.conf. Now, if I then
install razor-2.61 and run the following command:

  razor-admin -d -create -home=/var/amavis/.razor

Here is what happens:

  1) It overwrites /etc/razor/razor-agent.conf with a newly generated
     configuration file (perserving the options already specified).

  2) It creates the following files in /var/amavis/.razor:
       * server.folly.cloudmark.com.conf
       * servers.catalogue.lst
       * servers.discovery.lst
       * servers.nomination.lst

Now, if I clean up and do exactly the same thing with razor-2.72:

   1) It overwrites /etc/razor/razor-agent.conf with a newly generated
      configuration file (perserving the options already specified),
      just as it did before.

   2) It creates just one file in /var/amavis/.razor:
        * server.joy.cloudmark.com.conf

   3) It creates the rest under /etc/razor (!):
        * servers.catalogue.lst
        * servers.discovery.lst
        * servers.nomination.lst

Perhaps I'm missing something but surely the 2.72 behaviour could be
considered a bug? That is, the newly generated configuration files
should reside under the home directory that was explicitly stated on
the command line and *nowhere* else, right?

The reason I looked into that is because I've been examining the way
in which my distro (Gentoo) packages razor. I wish to propose that
they ship a default /etc/razor/razor-agent.conf file in much the same
was as, say, Debian do. Their amavisd-new package contains a hook to
call razor-admin and automatically set up a a razorhome for amavis -
very much in the way that's been described in this thread. It also
contains an ugly grep to alter the debug level after generation so I
thought "hey, really we should just ship a default config file in the
razor package and let further invocations of razor-admin inherit from
that". It was this line of thinking that led to me to toy around and
discover the above. razor's willingness to overwrite vendor-shipped
configuration files in this manner gives me concern in terms of
packaging but I'll stow those thoughts because it's probably off-topic
at this stage and I need to think it through myself :/

Regards,

--Kerin Millar


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click