On Thu, 01 Sep 2005, Todd Troxell wrote:
> tag 312393 moreinfo
> thanks
>
> My guess on this is that the postinst script got interrupted. Is anyone able
> to reproduce this?
well i guess one needs to setup webmin in a woody choort.
and try to upgrade.
haven't yet bothered, as i have zero webmin
tag 312393 moreinfo
thanks
My guess on this is that the postinst script got interrupted. Is anyone able
to reproduce this?
--
[ Todd J. Troxell ,''`.
Student, Debian GNU/Linux Developer, SysAdmin, Geek : :' :
http://debian.org || http://rap
> > ls -l /etc/logcheck
> > total 44
> > drwxr-s--- 2 root logcheck 4096 Jun 7 20:51 cracking.d
>
> .
> looks fine indeed.
> strange permissions are set on the same step almost.
> did the logcheck upgrade have any notable errors?
Don't remember. I had problems with the webmin upgrade (woody->sar
On Wed, 08 Jun 2005, Peter Walser wrote:
>
> > please send us the output of
> > ls -l /etc/logcheck
> ls -l /etc/logcheck
> total 44
> drwxr-s--- 2 root logcheck 4096 Jun 7 20:51 cracking.d
..
looks fine indeed.
strange permissions are set on the same step almost.
did the logcheck upgrade have
> please send us the output of
> ls -l /etc/logcheck
ls -l /etc/logcheck
total 44
drwxr-s--- 2 root logcheck 4096 Jun 7 20:51 cracking.d
drwxr-xr-x 2 root root 4096 Jun 7 20:51 cracking.ignore.d
-rw-r--r-- 1 root logcheck 180 Apr 19 2004 header.txt
drwxr-xr-x 2 root logcheck 4096 Mar 2
On Wed, 08 Jun 2005, Peter Walser wrote:
> Today I upgraded my server from woody to sarge.
> After repeated installing and uninstalling of webmin (where logcheck is
> used), I ended up with a version that does not work.
>
> The directory for the lockfile.lock is not writable for the user logcheck
Package: logcheck
Version: 1.2.39
Severity: important
Today I upgraded my server from woody to sarge.
After repeated installing and uninstalling of webmin (where logcheck is
used), I ended up with a version that does not work.
The directory for the lockfile.lock is not writable for the user logc
7 matches
Mail list logo
