Your message dated Tue, 3 Jul 2007 16:29:42 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: orca
Version: 0.2.3
Severity: normal
I've been getting daily messages like this one for a long time, even
long after I uninstalled orca:
From: [EMAIL PROTECTED] (Cron Daemon)
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> test -x /usr/sbin/anacron || run-parts
--report /etc/cron.daily
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env:
<PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
Date: Sun, 12 Dec 2004 06:37:32 +0200 (EET)
/etc/cron.daily/logrotate:
orca: no process killed
error: error running postrotate script
run-parts: /etc/cron.daily/logrotate exited with return code 1
(This sample isn't entirely fresh because I've been deleting them
lately. This one was still left in my inbox as a reminder to report
this bug.)
I had the package installed briefly sometime last summer or so, but I
never got around to configuring it properly and the cron reports were
annoying me so I removed it, thinking they would cease. Turns out it
just continues to send these ...
I don't know what the fix should be exactly, but the immediate problem
seems to be that the script in /etc/logrotate.d/orca assumes that an
orca process will be running at the time the cron job executes, and
throws an error if not, causing anacron to generate an error message.
I don't know if this is specific to anacron; I would think not.
Possibly changing the script so that the error is not fatal might
suffice -- I'm not familiar enough with logrotate and anacron to tell
for sure. (Perhaps you'd also need to quench any warning message. Ugh.)
/* era */
Hmm, if the logrotate script uses killall, shouldn't the package then
depend (or even pre-depend?) on psmisc?
[Sorry for the bad form -- I certainly know I shouldn't report
multiple bugs in one bug report but I'm uncertain if this is a bug and
filing a report just in case seems excessive. Please clone to a
separate bug if you think you need one.]
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686-smp
Locale: LANG=C, LC_CTYPE=C
Versions of packages orca depends on:
ii libber0 0.4.1 A Basic Encoding Rules (ITU X.690)
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libconfig0 0.1.5 Configuration file parser library
ii libdebug0 0.4.2 Memory leak detection system and l
ii librrd0 1.0.48-2 Time-series data storage and displ
ii logrotate 3.7-2 Log rotation utility
--- End Message ---
--- Begin Message ---
This package has been removed from Debian unstable. I'm therefore
closing this bug report. The package has been removed because it
was obsolete and unmaintained.
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
