Your message dated Wed, 3 Sep 2008 12:06:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#330220: logcheck: Fails to obtain lockfile
has caused the Debian Bug report #330220,
regarding logcheck: Fails to obtain lockfile
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
330220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330220
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: logcheck
Version: 1.2.39
Severity: important
Every time locheck runs from cron on my system it generates a mail
reporting:
| Failed to get lockfile: /var/lock/logcheck/logcheck.lock
This only appears to happen when running from cron. Attempting to run
logcheck or lockfile-create by hand seems to work as expected. The
permissions on the lock directory appear to be fine:
| $ ls -ld /var/lock/logcheck/
| drwxr-xr-x 2 logcheck logcheck 4096 Sep 26 20:02 /var/lock/logcheck/
so I'm at a bit of a loss trying to explain this. I've not done any
configuration of logcheck, it's been doing this since it was installed.
Filing this with severity important since it has a major effect on
usability, though given that this is sarge I suspect the problem may
have already been addressed.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages logcheck depends on:
ii adduser 3.63 Add and remove users and groups
ii cron 3.0pl1-86 management of regular background p
ii debconf [debconf 1.4.30.13 Debian configuration management sy
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii exim4 4.50-8 metapackage to ease exim MTA (v4)
ii exim4-daemon-hea 4.50-8 exim MTA (v4) daemon with extended
ii lockfile-progs 0.1.10 Programs for locking and unlocking
ii logcheck-databas 1.2.39 A database of system log rules for
ii logtail 1.2.39 Print log file lines that have not
ii mailx 1:8.1.2-0.20040524cvs-4 A simple mail user agent
ii sysklogd [system 1.4.1-17 System Logging Daemon
-- debconf information:
logcheck/changes:
* logcheck/install-note:
--- End Message ---
--- Begin Message ---
* Mark Brown <[EMAIL PROTECTED]> [2005-09-26 22:17:40 CEST]:
> Every time locheck runs from cron on my system it generates a mail
> reporting:
>
> | Failed to get lockfile: /var/lock/logcheck/logcheck.lock
>
> This only appears to happen when running from cron. Attempting to run
> logcheck or lockfile-create by hand seems to work as expected. The
> permissions on the lock directory appear to be fine:
>
> | $ ls -ld /var/lock/logcheck/
> | drwxr-xr-x 2 logcheck logcheck 4096 Sep 26 20:02 /var/lock/logcheck/
>
> so I'm at a bit of a loss trying to explain this. I've not done any
> configuration of logcheck, it's been doing this since it was installed.
As discussed on IRC I'm closing the issue as it wasn't really
reproducible and others contributing to the bug report had clear
permission issues with their directories.
If it pops up again and you find something to pinpoint or narrow it
down, feel free to raise your voice again. :)
So long, and thanks.
Rhonda
--- End Message ---
_______________________________________________
Logcheck-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/logcheck-devel
