mherger wrote:
> > What exactly happens during the database optimization phase of
> scanning?
>
> It does run a "vacuum" on the database:
> --
>
> Michael
Hi Michael,
my maintenance script (triggered by my rescan script) always vacuum the
databasefiles and thats the output...
> start : Mo 11. Dez 18:18:44 CET 2017
> -rw-r--r-- 1 squeezeboxserver nogroup 177694720 Dez 11 18:18 artwork.db
> -rw-r--r-- 1 squeezeboxserver nogroup 259568640 Dez 11 18:17 cache.db
> -rw-r--r-- 1 squeezeboxserver nogroup 215212032 Dez 11 18:18
> imgproxy.db
> -rw-r--r-- 1 squeezeboxserver nogroup 211119104 Dez 11 18:18 library.db
> -rw-r--r-- 1 squeezeboxserver nogroup 45911040 Dez 11 18:18 persist.db
> end :Mo 11. Dez 18:19:48 CET 2017
> -rw-r--r-- 1 squeezeboxserver nogroup 177580032 Dez 11 18:19 artwork.db
> -rw-r--r-- 1 squeezeboxserver nogroup 259453952 Dez 11 18:19 cache.db
> -rw-r--r-- 1 squeezeboxserver nogroup 215136256 Dez 11 18:19
> imgproxy.db
> -rw-r--r-- 1 squeezeboxserver nogroup 206803968 Dez 11 18:19 library.db
> -rw-r--r-- 1 squeezeboxserver nogroup 45006848 Dez 11 18:19 persist.db
>
Thats the part of the maintenance script:
Code:
--------------------
service logitechmediaserver stop
cd /var/lib/squeezeboxserver/cache
ls -l *.db>>/tmp/maintenance.log
for file in $(find -iname '*.db' | sort)
do
echo "processing $file"
sudo sqlite3 $file "vacuum";
sudo chown squeezeboxserver:nogroup $file
done
service logitechmediaserver start
echo "end :$(date)">>/tmp/maintenance.log
ls -l *.db>>/tmp/maintenance.log
--------------------
If the rescan also does a vacuum i wonder why there is such a difference
in the filesize?
------------------------------------------------------------------------
DJanGo's Profile: http://forums.slimdevices.com/member.php?userid=1516
View this thread: http://forums.slimdevices.com/showthread.php?t=108377
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
