On Thu, 30 Jun 2005 06:06, Gary V wrote: > BTW, razor version 2.74 which does address the Segfault issue is > available.
Yes, though I'd prefer to concentrate on getting the patched version into stable than going from a patched 2.72 to an unpatches 2.74. > Note that razor-client is now deprecated Yes, the version of 2.72 in unstable does not call it. 2.71 does (I hadn't noticed when I uploaded 2.71) but I don't think 2.71 got into unstable anyway. > so /etc/razor/razor-agent.conf > will no longer be created when you run razor-client. razor-agent.conf was created manually by me. > This is > actually a good thing. Now when you run 'razor-admin -create', > razor-agent.conf will be created in the user's directory, or where > you ask it to create it. For example, running as user root, if > you used to simply run razor-client, and then 'razor-admin -create', > it would create /etc/razor/razor-agent.conf. Now it will create > /root/.razor/razor-agent.conf. I'll have to look at this again, since it appears the behaviour has changed again. Last time I looked at it, /etc/razor/razor-agent.conf sets up system wide defaults which could be overridden by any user with $HOME/.razor/razor-agents.conf Because $RAZORHOME was getting set unreliably, especially when called by spamassassin, the /etc file was very useful in trying to prevent a log file being created in /. Even then it wasn't perfect, though I don't have a log file in / currently. > You may want to test any install > scripts with the new version, as it does behave differently when > creating a new razorhome. Sounds like something to do when I upgrade to 2.74/2.75, which I understand also fixes the sys-syslog issue. Corrin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
