Keyserv exit without any error message

Michael Thalmann iceman at s.netic.de
Mon Aug 13 16:10:55 EST 2001


Hello!

Something very strange happens when I run the standard cron script.
Keyserv exits. If I disable this script keyserv keeps up for days.
I tried to find out which part of the script is the problem, but I didn't
manage to get any closer. If I run the script myself, when I am logged on
keyserv does not exit. I ran the script by cron at 9 o'clock, 10, 6... and
so on.
After the script finished his work keyserv does no longer exist.

I am using Debian 2.2 (potato), Nisutilities 1.4.1.

Thanks for any hints.

I added the standard script as attachment.

Greetings
        Michael

-------------- next part --------------
#!/bin/sh
# /etc/cron.daily/standard: standard daily maintenance script
# Written by Ian A. Murdock <imurdock at gnu.ai.mit.edu>
# Modified by Ian Jackson <ijackson at nyx.cs.du.edu>
# Modified by Steve Greenland <stevegr at 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


More information about the linux-nisplus mailing list