Help understanding "Anacron job 'cron.daily'"

[ghcbc@yahoo.com]

This is pure curiosity.  After boot I got the following message in my
mailbox.  I was curious as to what maintenance job would be looking in user
netscape caches.  I've looked at /etc/cron.daily/standard, the script that
was apparently generated this message, but I don't see where it looks for
anything in /home.  In fact, in the part where the "find" command is used, I
don't really understand what directory it is looking for lost+found stuff.

Can anyone explain this to me ? The contents of /etc/cron.daily/standard
follow the forwarded message.

Thanks, 

Ger

----- Forwarded message from Anacron <root@popcorn> -----

Subject: Anacron job 'cron.daily'
Date: Thu, 26 Aug 2004 
From: root@popcorn (Anacron)
To: root@popcorn

/etc/cron.daily/standard:
find: /home/peanut/.netscape/cache/16/cache412BB9D602B129E.gif: No such file or directory
find: /home/peanut/.netscape/cache/16/cache412BB9D602B129E.gif: No such file or directory
find: /home/peanut/.netscape/cache/16/cache412BB9D602B129E.gif: No such file or directory

----- End forwarded message -----




----- Begin dump of /etc/cron.daily/standard ------
#!/bin/sh
# /etc/cron.daily/standard: standard daily maintenance script
# Written by Ian A. Murdock <imurdock@gnu.ai.mit.edu>
# Modified by Ian Jackson <ijackson@nyx.cs.du.edu>
# Modified by Steve Greenland <stevegr@master.debian.org>

bak=/var/backups
LOCKFILE=/var/lock/cron.daily
umask 022

#
# Avoid running more than one at a time -- could happen if the
# checksecurity script lands on a network drive.
#

if [ -x /usr/bin/lockfile-create ] ; then
    lockfile-create $LOCKFILE
    if [ $? -ne 0 ] ; then
	cat <<EOF

Unable to run /etc/cron.daily/standard because lockfile $LOCKFILE
acquisition failed. This probably means that the previous days
instance is still running. Please check and correct if necessary.

EOF
	exit 1
    fi

    # Keep lockfile fresh
    lockfile-touch $LOCKFILE &
    LOCKTOUCHPID="$!"
fi

#
# Backup key system files
#

if cd $bak
then
	cmp -s passwd.bak /etc/passwd || cp -p /etc/passwd passwd.bak
	cmp -s group.bak  /etc/group  || cp -p /etc/group  group.bak
        chmod 600 passwd.bak group.bak
        if [ -f /etc/shadow ] ; then
	  cmp -s shadow.bak  /etc/shadow  || cp -p /etc/shadow  shadow.bak
          chmod 600 shadow.bak
	fi
        if [ -f /etc/gshadow ] ; then
	  cmp -s gshadow.bak  /etc/gshadow  || cp -p /etc/gshadow  gshadow.bak
	  chmod 600 gshadow.bak
	fi
fi

cd /var/lib/dpkg
if cmp -s status.yesterday.0 status
then
    :
else
	cp -p status status.yesterday
	savelog -c 7 status.yesterday >/dev/null
fi

cd /var/log
umask 027
savelog -c 7 -m 640 -u root -g adm setuid.changes >/dev/null
checksecurity >setuid.changes

#
# Check to see if any files are in lost+found directories and warn admin
#
if [ -d "/lost+found" ] ; then 
  lost_found=`find '/lost+found' |grep -v 'lost+found$'`
else
  lost_found=""
fi
if [ "$lost_found" ]; then
    cat << EOF
Files were found in lost+found directories. This is probably
the result of a crash or bad shutdown, or possibly of a disk
problem. These files may contain important information. You
should examine them, and move them out of lost+found or delete
them if they are not important.

The following files were found:
$lost_found
EOF
fi

#
# Clean up lockfile
#
if [ -x /usr/bin/lockfile-create ] ; then
    kill $LOCKTOUCHPID
    lockfile-remove $LOCKFILE
fi

----- End dump of /etc/cron.daily/standard --------

Thanks,

Ger