Philip Meyer Wrote: > I had problems about a week ago with rescanning. There were some > problems where slimserver would somehow start iterating through all > files on every hard disk/partition. For me, this was due to badly > formed .m3u or .cue files. > > You could try turning on d_scan and/or d_files to get more debug > information, and looking at the log. This should identify at what > point scanning goes wrong, or you might see it repeating the scan over > the same files if there's some form of circular link in the filesystem.
Good call, that appears to be exactly what's going on for me (I'm actually still on 6.1.1). I'm not sure how the transition happens, though: 2005-09-26 10:30:37.1908 itempath: file:///#CURTRACK%2071 and file:///Users/ert/Music/Playlists/Mellow%201-22-04.m3u made file:///#CURTRACK%2071 2005-09-26 10:30:37.2035 isList(file:///#CURTRACK%2071) == dir 2005-09-26 10:30:37.5583 Scan::readList gonna read file:///#CURTRACK%2071 2005-09-26 10:30:37.5609 Gonna try to open playlist file:///#CURTRACK%2071 2005-09-26 10:30:37.5902 *** didn't find file:///#CURTRACK%2071 in playlist cache *** 2005-09-26 10:30:37.5924 Treating directory like a playlist 2005-09-26 10:30:37.6192 directory entry: file:///.Spotlight-V100 2005-09-26 10:30:37.6557 directory entry: file:///.vol 2005-09-26 10:30:37.6912 directory entry: file:///Applications 2005-09-26 10:30:37.7264 directory entry: file:///Developer ...etc. etc. It *looks* like it hit the "#CURTRACK 71" entry at the top of one of my playlists and decided it was a file, but I'm not sure. - Ert -- ert _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
