reopen 247057
thanks

Hi,

On Wed, 2005-02-09 at 14:03 -0800, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> #247057: razor: creates /razor-agent.log,
> which was filed against the razor package.
> 
> It has been closed by one of the developers, namely
> Corrin Lakeland <[EMAIL PROTECTED]>.

> [...]

>    * RAZOR_HOME is now derived automatically and cannot be manually set.
>        The logic for deriving it automatically has been improved so you
>          shouldn't see any problems unless they're trying to do something odd.
>          I'm going to close the old bug reports about logging to / because
>          I cannot reproduce them at all with this version
>          (Closes: #269723, #262765, #247057)
>          This also fixes the potential security concerns with logging to /tmp
>          as logging to /tmp should never happen now. (Closes: #292420)
>        For all users, the default configuration file is
>          /etc/razor/razor-agent.conf unless this file does not exist.
>          Any user, including root, can override this default by creating a
>          file ~/.razor/razor-agent.conf.  If the latter file exists, then the
>          file in /etc will be ignored.   Note that this behaviour is different
>          to previous versions of razor.

Sorry for not reacting earlier.

Unfortunately, the problem persists here. I'm running current sid and on
"/etc/init.d/spamassassin restart", /razor-agent.log is created.

/etc/default/spamassassin contains:

==========================================================================
# /etc/default/spamassassin
# Duncan Findlay

# WARNING: please read README.spamd before using.
# There may be security risks.

# Change to one to enable spamd
ENABLED=1

# Options
# See man spamd for possible options. The -d option is automatically added.

# NOTE: version 3.0.x has switched to a "preforking" model, so you
# need to make sure --max-children is not set to anything higher than
# 5, unless you know what you're doing.

OPTIONS="--create-prefs --max-children 5 --helper-home-dir=/tmp"

# Pid file
# Where should spamd write its PID to file? If you use the -u or
# --username option above, this needs to be writable by that user.
# Otherwise, the init script will not be able to shut spamd down.
PIDFILE="/var/run/spamd.pid"

# Set nice level of spamd
#NICE="--nicelevel 15"
==========================================================================

Output from razor-check:

==========================================================================
# razor-check --verbose ipod_format
 Razor-Log: Computed razorhome from env: /root/.razor
 Razor-Log: No razorhome found, using all defaults
 Razor-Log: read_file: 1 items read from /etc/razor/razor-agent.conf
Feb 18 23:13:52.292717 check[4698]: [ 2] [bootup] Logging initiated 
LogDebugLevel=9 to stdout
Feb 18 23:13:52.296799 check[4698]: [ 5] computed razorhome=, 
conf=/etc/razor/razor-agent.conf, ident=identity
Feb 18 23:13:52.300574 check[4698]: [ 2]  Razor-Agents v2.67 starting 
razor-check --verbose ipod_format
Feb 18 23:13:52.305530 check[4698]: [ 9] uname -a: Linux atari 2.6.8-2-686 #1 
Mon Jan 24 03:58:38 EST 2005 i686 GNU/Linux
Feb 18 23:13:52.314057 check[4698]: [ 1] razor-check error: Can't open 
ipod_format: No such file or directory
Can't open ipod_format: No such file or directory
==========================================================================

There's no /root/.razor, and /etc/razor/razor-agent.conf contains:

==========================================================================
# See razor-agent.conf (5)

# Change this to 5 for safer classification of MIME attachments.  This will let 
more spam through
logic_method = 4
# Uncomment the next line for logging via syslog
#logfile = sys-syslog
# If you do log to syslog, consider using logrotate
# (see /usr/share/doc/razor/logcheck.ignore.eg)
==========================================================================

So basically, the same problem as before. Please tell me how I can help
here, since I can reproduce the problem very easily.

Thanks.

bye,
  Roland




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to