Logcheck devel - Feb 2005 - logcheck fails: failed to get lockfile

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hallo,

after upgrading logcheck to 1.2.34 it fails to run with the error:
> Details:
> Failed to get lockfile: /var/lock/logcheck.lock
The error is caused by the new cron job, because logcheck now runs as user 
logcheck, which has no write permissions to /var/lock. The installer already 
created the directory /var/lock/logcheck with correct permissions but did not 
add

LOCKFILE="/var/lock/logcheck/logcheck"

to /etc/logcheck/logcheck.conf.

Maybe you use the above as default in /usr/sbin/logcheck to avoid this error.

mfg
Gunter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB/2G1ghsXb/J0PcERAlFwAJoCBqm8Ubwby2q1i2l3zLuCtL3XmACeNe9s
dhQ04kVshg5wu47prmgF0uE=z2MI
-----END PGP SIGNATURE-----

On Tue, 01 Feb 2005, Gunter Winkler wrote:
> Hallo,
> 
> after upgrading logcheck to 1.2.34 it fails to run with the error:
> 
> > Details:
> > Failed to get lockfile: /var/lock/logcheck.lock
could you please send the output on you system of:
ls -ld /var/lock
 
> The error is caused by the new cron job, because logcheck now runs as user 
> logcheck, which has no write permissions to /var/lock. The installer
already
> created the directory /var/lock/logcheck with correct permissions but did
not
> add
> 
> LOCKFILE="/var/lock/logcheck/logcheck"
> 
> to /etc/logcheck/logcheck.conf.
$ dpkg -L logcheck | grep lock
returns nothing.
/var/lock/logcheck is not created by current logcheck,
was it done in the older versions?
 
> Maybe you use the above as default in /usr/sbin/logcheck to avoid this
error.
thanks for your feedback

--
maks

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 01 February 2005 13:21, maximilian attems
wrote:
> could you please send the output on you system of:
> ls -ld /var/lock
root at ares:~# ls -ld /var/lock/
drwxr-xr-t  5 root root 4096 Feb  1 10:29 /var/lock/

root at ares:~# ls -l /var/lock/
total 12
drwxr-xr-x  2 logcheck logcheck 4096 Feb  1 13:02 logcheck
drwxr-xr-x  2 root     root     4096 Feb  1 13:55 mrtg
drwxr-xr-x  2 root     root     4096 Feb  1 10:30 subsys

I looked at another host, but there was no logcheck subdir in /var/lock. Maybe 
an earlier version of the logcheck package created this. After manually 
creating /var/lock/logcheck and changing the owner to logcheck, the error 
disappeared and logcheck now runs fine.
Both hosts were installed about a year ago with sarge.

On a third host, which was installed a few weeks ago (sarge) the lock dir is 
world writable:

root at achilles:~# ls -ld /var/lock/
drwxrwxrwt  2 root root 1024 2005-02-01 14:02 /var/lock/

Maybe these permission had been changed in the meantime.

mfg
Gunter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB/38TghsXb/J0PcERAqofAJ9fJBlO8gWTqGt6AIOHtdHMB8qVWwCeOHQa
uoJG1OB1Xrw5uLGS/FVykxA=2igp
-----END PGP SIGNATURE-----