Bug#304978: [Logcheck-devel] Bug#304978: Failed to get lockfile: /var/lock/logcheck.lock

2005-04-18 Thread Todd Troxell
On Mon, Apr 18, 2005 at 09:31:14AM +0200, maximilian attems wrote: > todd what do you think about that dir? > sounds ok for me, > but i don't get why you paranoid guy show your logcheck run > to world, why not use 750 above?? It sounds good to me. I think 755 is fine. nb: I've just tested this

Bug#304978: [Logcheck-devel] Bug#304978: Failed to get lockfile: /var/lock/logcheck.lock

2005-04-18 Thread Rainer Zocholl
[EMAIL PROTECTED](maximilian attems) 18.04.05 09:31 >On Sun, 17 Apr 2005, Rainer Zocholl wrote: >> Everytime(!) i upgrade debian logcheck i run into the error >> that logcheck is trying to generate its lockfile at a >> forbidden location. >> The error message/mail is a bit missleading too. >on

Bug#304978: [Logcheck-devel] Bug#304978: Failed to get lockfile: /var/lock/logcheck.lock

2005-04-18 Thread maximilian attems
On Sun, 17 Apr 2005, Rainer Zocholl wrote: > Everytime(!) i upgrade debian logcheck i run into the error > that logcheck is trying to generate its lockfile at a > forbidden location. > The error message/mail is a bit missleading too. on debian systems by default belows dir is writable for world: