Home > Failed To > Failed To Get Lock File /var/lock/logcheck/logcheck.lock

Failed To Get Lock File /var/lock/logcheck/logcheck.lock

i try to summarize >* if /var/lock is not world writable, one should have a dir below > for one owns needs. Yes. >* if /var/lock is world writable, one could block logcheck runs. simply by searching for the error message at google ;-) (some things are too simple) (But no helpful answers like yours, thanks.). >> Is it a so common (dangerous) practise to Full text and rfc822 format available. have a peek at this web-site

Full text and rfc822 format available. Acknowledgement sent to Pablo Barbachano : Extra info received and forwarded to list. jamie: * Add rule in violations.ignore.d/logcheck-postfix for postgrey (Closes: #30088) * Modify bind notify rule for bind 9.3.x (Closes: #303176) * Add various workstation kernel/udev rules for removable devices (Closes: #297995) drwxr-xr-x 2 root root 1024 2005-04-18 23:14 bastille drwx------ 2 root root 1024 2005-03-11 21:11 lvm So far your are right: The problem is hidden by the sticky bit.

Copy sent to Debian logcheck Team . Reported by: Rainer Zocholl Date: Sat, 16 Apr 2005 22:18:02 UTC Severity: important Found in versions 1.2.37, 1.2.39 Fixed in version logcheck/1.2.38 Done: Todd Troxell Bug is archived. Trouble? But meanwhile i found others had that problem too.

I think that is a very "unwanted behavior". Debian bug tracking system administrator . OK? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.

Changed in logcheck: status: Confirmed → Fix Committed Scott James Remnant (Canonical) (canonical-scott) on 2006-04-20 Changed in logcheck: status: Fix Committed → Fix Released See full activity log To post a Message #15 received at [email protected] (full text, mbox, reply): From: Rainer Zocholl To: <[email protected]> Subject: Re: Bug#304978: [Logcheck-devel] Bug#304978: Failed to get lockfile: /var/lock/logcheck.lock Date: 18 Apr 2005 23:49:00 +0200 I've used logcheck for a while and never seen this error, but with some other software I've found that it an hourly cron job is still running an hour later. https://bugs.debian.org/304978 It might be the same kind of problem I have with courier imap where it seems that the courier directory is not created in /var/run which makes courier bail out.

nor aptitude reinstall logcheck. I've used logcheck for a while and never seen this error, but with some other software I've found that it an hourly cron job is still running an hour later. If "root" is going to create the lock, root will "win" and maybe kill/remove that lock before the first program really finished. So it looks into /var/lock to see what's on.

User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License. I am nearly sure that there is no lock file in that directory. Hm, maybe that change was done by "hardening" the system? that should just work on runtime. -- maks ps i don't get your nospam stuff, perhaps you'll read your bug report.

Notification sent to Rainer Zocholl : Bug acknowledged by developer. http://3swindows.com/failed-to/failed-to-take-master-pipe-connection-lock-cs-1-6.html Message #39 received at [email protected] (full text, mbox, reply): From: maximilian attems To: Pablo Barbachano , [email protected] Subject: Re: [Logcheck-devel] Bug#304978: logcheck: wrong permissions Date: Tue, 3 May 2005 23:41:58 Full text and rfc822 format available. Reinstalling of logcheck didn't help Hmm.

  • Information forwarded to [email protected], Debian logcheck Team : Bug#304978; Package logcheck.
  • Reply sent to Todd Troxell : You have taken responsibility.
  • So when root changes the (old) lock, it >> changes the "unwanted" file too etc...
  • Contact [EMAIL PROTECTED] Re: Re: Logcheck error: Failed to get lockfile: /var/lock/logcheck/logcheck.lock 2005-06-23 Thread Fabio Massami Yamamoto You may have to change the owner of the lock folder.
  • I think 755 is fine.
  • Reinstalling of logcheck didn't help best regards michal sedlak ----- Original Message ----- From: "Adam Funk" <[emailprotected]> To: <[emailprotected]> Sent: Thursday, June 23, 2005 3:55 PM Subject: Re: Logcheck error: Failed
  • Copy sent to Debian logcheck Team .
  • Student, Debian GNU/Linux Developer, SysAdmin, Geek : :' : http://debian.org || http://rapidpacket.com/~xtat `. `' `- ] [signature.asc (application/pgp-signature, inline)] Severity set to `important'.
  • Full text and rfc822 format available.
  • Copy sent to Debian logcheck Team .

Contact [EMAIL PROTECTED] Re: Logcheck error: Failed to get lockfile: /var/lock/logcheck/logcheck.lock 2005-06-23 Thread Michal Sedlak Thank fou for response. from [Michal Sedlak] Subject: Re: Logcheck error: Failed to get lockfile: /var/lock/logcheck/logcheck.lock From: "Michal Sedlak" Date: Fri, 24 Jun 2005 00:07:02 +0200 Thank fou for response. The diff is actually against Debian's 1.2.43a. Source Can anybody help please?

So the other program is blocked because of an violation of the first program... Report a bug This report contains Public information Edit Everyone can see this information. Given below is the mail I get from logcheck whenever it runs.

Reinstalling of logcheck didn't help best regards michal sedlak - Original Message - From: Adam Funk [EMAIL PROTECTED] To: [email protected] Sent: Thursday, June 23, 2005 3:55 PM Subject: Re: Logcheck error:

I think the fix should be made upstream. Request was from xtat to [email protected] FAQ Forum Quick Links Unanswered Posts New Posts View Forum Leaders FAQ Contact an Admin Forum Community Forum Council FC Agenda Forum Governance Forum Staff Ubuntu Forums Code of Conduct Forum why is it misleading? > Solution: > > you must edit the script(!) as logcheck has as security flaw > and tries to place it's lock file under /var/lock/ which is

Copy sent to Debian logcheck Team . OTH: What happens, if a (bad) programm stroes a lock into /var/lock that (un)intentionally has the same name as an other program will be using later? The results of the first programs are random! have a peek here The logcheck package should create the directory with the correct permissions and ownership.

Contact [emailprotected] [Morewiththissubject...] Logcheck error: Failed to get lockfile: /var/lock/logcheck/logcheck.lock, Michal Sedlak Re: Logcheck error: Failed to get lockfile: /var/lock/logcheck/logcheck.lock, Adam Funk Re: Logcheck error: Failed to get Allowing everybody > to place a link to an unwanted file with the name of > a root lock file? drwxr-xr-x 2 www-data www-data 4096 Mar 22 2004 DAV drwx------ 2 root root 4096 Jan 8 23:43 lvm drwxr-xr-x 2 root root 4096 Apr 18 23:10 mrtg drwxr-xr-x 2 root root Full text and rfc822 format available.

Mark as duplicate Convert to a question Link a related branch Link to CVE Duplicates of this bug Bug #6487 Bug #36754 Bug #37541 Bug #42360 You are not directly subscribed Subscribing... Trouble? The problem is that /var/lock/logcheck has permissions: drwxr-xr-x 2 root root 48 Apr 19 17:58 logcheck I dont know why, because it should be changed in the postinst ... -- System

Presumably the lock directory is now purged at startup, though I don't know what's changed.