Hi, same problem here.
Am 16.03.2012 12:49, schrieb Kristian Fiskerstrand: > On 16.03.2012 08:57, Michael Nausch wrote: > First of all, I presume you have tried just rebuilding the ptree, but > this is a recurring problem ? of course, but this does not solve problem. At this time I am using following script, to recover from that problem: #!/bin/bash PID='/var/run/sks-rebuild.pid' if [ -e $PID ]; then echo "$PID exists" echo "rebuild-sks already running" exit 1 fi echo $$ > "$PID" cd /var/lib/sks || exit 1 /etc/init.d/sks stop rm -rf dump > /dev/null 2> /dev/null mkdir dump sks dump 15000 dump rm -rf DB PTree /usr/local/bin/sks_build.sh chown -R debian-sks:debian-sks DB PTree /etc/init.d/sks start rm -f "$PID" After that sks recon works. > Anyhow, I'd check /sys/devices/system/clocksource/clocksource0/ where > I'd expect to see the files (i) available_clocksource, and (ii) > current_clocksource. # cat /sys/devices/system/clocksource/clocksource0/available_clocksource kvm-clock tsc hpet acpi_pm # cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock clock is synchronized to DCF reference. Christian _______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
