On Tue, 5 Oct 1999 11:49:33 -0400, Bill Nottingham <[EMAIL PROTECTED]>
wrote:
>Kevin Vajk ([EMAIL PROTECTED]) said:
>> > /usr/sbin/tmpwatch -v -v --test 48 /tmp /var/tmp
>>
>> Just tried it...
>>
>> > found directory entry rc.d
>> > cleaning up directory rc.d
>> > found directory entry init.d
Kevin Vajk ([EMAIL PROTECTED]) said:
> > /usr/sbin/tmpwatch -v -v --test 48 /tmp /var/tmp
>
> Just tried it...
>
> > found directory entry rc.d
> > cleaning up directory rc.d
> > found directory entry init.d
> > cleaning up directory init.d
>
> ...and saw all this too. I nearly had a heart-a
On Tue, 5 Oct 1999, Albert E. Whale wrote:
> /usr/sbin/tmpwatch -v -v --test 48 /tmp /var/tmp
Just tried it...
> found directory entry rc.d
> cleaning up directory rc.d
> found directory entry init.d
> cleaning up directory init.d
...and saw all this too. I nearly had a heart-attack. :)
T
I want to use tmpwatch to eliminate files in /tmp and /var/tmp after 48
hours. When I attempted this operation, here's what I got!
/usr/sbin/tmpwatch -v -v --test 48 /tmp /var/tmp
Can anyone tell me why the utility has scanned this much of the
Server
I am using the latest version of tmpwa
