rickert@CS.NIU.EDU (Neil Rickert) (06/12/90)
Warning to new users of Umax 4.3
The version of '/usr/lib/crontab' contains the following records:
10 4 * * * root find /usr/preserve -atime +7 -exec /bin/rm -f {} ';'
20 4 * * * root find /usr/tmp -atime +7 -exec /bin/rm -f {} ';'
Since /usr/tmp is now a symbolic link /var/tmp, these 'cron' commands
are likely to remove that link, leaving you with neither a /usr/tmp nor
a /usr/preserve.
Solution: Instead, run a shell script, and include something like -
if cd /usr/tmp ; then
find . -atime +7 -exec /bin/rm -f {} ';'
fi
(and, of course, a similar script for /usr/preserve).soper@maxzilla.encore.com (Pete Soper) (06/12/90)
From article <9006121234.AA04553@cs.niu.edu>, by rickert@CS.NIU.EDU (Neil Rickert): > > Warning to new users of Umax 4.3 > > The version of '/usr/lib/crontab' contains the following records: > > 10 4 * * * root find /usr/preserve -atime +7 -exec /bin/rm -f {} ';' > 20 4 * * * root find /usr/tmp -atime +7 -exec /bin/rm -f {} ';' > > Since /usr/tmp is now a symbolic link /var/tmp, these 'cron' commands > are likely to remove that link, leaving you with neither a /usr/tmp nor > a /usr/preserve. > > Solution: Instead, run a shell script, and include something like - > > if cd /usr/tmp ; then > find . -atime +7 -exec /bin/rm -f {} ';' > fi > > (and, of course, a similar script for /usr/preserve). I discovered this on one of our internal systems just a few days ago. The change that the system administrator made here was to add a "/" to the above paths in the original crontab lines ( /usr/tmp becomes /usr/tmp/ and /usr/preserve becomes /usr/preserve/ ). - - - - - - - - - - - - - - - - - - - - ---------- Pete Soper (soper@encore.com) +1 919 481 3730 Encore Computer Corp, 901 Kildaire Farm Rd, bldg D, Cary, NC 27511 USA