PDA

View Full Version : Bring 'server is still scanning' back



Christian Pernegger
2005-03-13, 04:11
>This shoudlnt' be happening. the 'still scanning' checks the import count
>and
>if there is any, then it should be reporting 'still scanning'

Ah, k. I thought it had been removed.

>can you supply some details on what importers you use (and this includes
>music
>folder).

OS is Debian testing, I have the tarball "installed" under
/opt/slimserver-test and start the server as follows:
"HOME=/opt/slimserver-test ./slimserver.pl --logfile
"/opt/slimserver-test/slimserver.log" --daemon --user slimserver --group
slimserver --prefsfile "/opt/slimserver-test/slimserver.conf" --priority
-10"

The only source of tracks is the music folder, which does have symlinks to a
few other folders, all on the same filesystem and non-circular of course.

>was your slimserversql.db file erase?

I started with an empty directory and no DB and wiped cache in subsequent
test but I didn't erase it as such.

C.

kdf
2005-03-13, 04:19
Quoting Christian Pernegger <pernegger (AT) hotmail (DOT) com>:

> >This shoudlnt' be happening. the 'still scanning' checks the import count
> >and
> >if there is any, then it should be reporting 'still scanning'
>
> Ah, k. I thought it had been removed.

not intentionally :) but if you've seen it, there is clearly a case where it
fails. I'm not able to reproduce it myself in recent builds, but I did see
cases that could cause it while testing imports.


> >can you supply some details on what importers you use (and this includes
> >music
> >folder).
>
> OS is Debian testing, I have the tarball "installed" under
> /opt/slimserver-test and start the server as follows:
> "HOME=/opt/slimserver-test ./slimserver.pl --logfile
> "/opt/slimserver-test/slimserver.log" --daemon --user slimserver --group
> slimserver --prefsfile "/opt/slimserver-test/slimserver.conf" --priority
> -10"
>
> The only source of tracks is the music folder, which does have symlinks to a
> few other folders, all on the same filesystem and non-circular of course.

> >was your slimserversql.db file erase?
>
> I started with an empty directory and no DB and wiped cache in subsequent
> test but I didn't erase it as such.

I'm not sure what wipe cache does any more. I may not have covered that case
properly (still scanning is an 'import' parameter) If you erase the
slimserversql.db file specifically, so you still see the same problems?

my apologies if this has caused you inconvenience.

-kdf