> Developer andyg said in that old thread that "There is already some code
> to deal with loops of shortcuts/symlinks". But it's not working even
> with the most minimal test case I could think of: create two folders,
> each containing a symlink to the other, and scan the parent folder.
Can you set logging options for scan.* to debug, re-run that minimum
test scan, then upload the resulting scanner.log file?
And please provide some more information about your system: where are you running
LMS? What OS version? What exact LMS build?
--
Michael
> to deal with loops of shortcuts/symlinks". But it's not working even
> with the most minimal test case I could think of: create two folders,
> each containing a symlink to the other, and scan the parent folder.
Can you set logging options for scan.* to debug, re-run that minimum
test scan, then upload the resulting scanner.log file?
And please provide some more information about your system: where are you running
LMS? What OS version? What exact LMS build?
--
Michael