It turns out that the problem is not caused by tmpreaper but by zshell
(or its configuration). Sorry for all the noise, but therefor this bug
report can be closed :-D
kind regards,
Arno
Debian Bug Tracking System wrote:
Thank you for the additional information you have supplied regarding
thi
Unfortunately I haven't been able to reproduce this problem yet. As soon
as I know more (and have some spare time) on this issue, I'll let you know.
Paul Slootman wrote:
On Sat 05 Apr 2008, Arno van Amersfoort wrote:
I have my /tmp mounted on a seperate partition and I noticed that
everyti
On Sat 05 Apr 2008, Arno van Amersfoort wrote:
>
> I have my /tmp mounted on a seperate partition and I noticed that
> everytime fsck runs, the lost+found directory for this filesystem is
> missing. Now it turns out that tmpreaper is responsible for this.
> Although tmpreaper should exclude t
Package: tmpreaper
Version: 1.6.7
I have my /tmp mounted on a seperate partition and I noticed that
everytime fsck runs, the lost+found directory for this filesystem is
missing. Now it turns out that tmpreaper is responsible for this.
Although tmpreaper should exclude the lost+found directory,
4 matches
Mail list logo
