From: tackenhu@fnal.gov
Date: Wed Nov 20 2002 - 14:23:49 EST
We just upgraded one of our AlphaServers from 4.0F to 5.1A. Since the
upgrade, we receive nightly messages from a root cron job stating:
dirclean: Cannot unlink /tmp/quota.user: Permission denied
dirclean: Cannot unlink /tmp/quota.group: Permission denied
*************************************************
Cron: The previous message is the standard output
and standard error of the following crontab command:
/usr/sbin/dirclean -t +2 -o -k s /tmp/
This problem was introduced by the fact the 5.1A adds a new crontab entry
for root (actually, 4 entries using dirclean, but only one is causing this
problem) of the form:
20 4 * * * /usr/sbin/dirclean -t +2 -o -k s /tmp/
I believe a contributing factor to this problem is the fact we use a
dedicated filesystem for /tmp - so /tmp is the root of the filesystem and
therefore contains quota.user and quota.group files.
Short of either not having /tmp be the root of the filesystem, disabling
this cleanup cron job, or rewriting this cron entry to use find and rm or
some such, is there any way of getting "dirclean" to not mess with these
quota files? Would just touching the files (updating the timestamps and
thereby making them no longer meet the trimming criteria) work - I realize
this would have to be done a periodic basis.
Thanks,
Tom
=================================================================
Tom Ackenhusen tackenhu@fnal.gov
Business Systems Technical Services
Fermi National Accelerator Laboratory Batavia, IL, USA
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:00 EDT