Bugzilla – Bug 3604
UNC paths converted to mapped drive letters when run from console
Last modified: 2008-09-15 14:39:24 UTC
6.5 r8049, Perl version on Windows XP. Running the server from the command line and trying to save a UNC path in the web UI, SlimServer always saves the path using a mapped drive for the user logged in. If I were to subsequently run SlimServer as a service then using this mapped drive version of the path would fail. It does the same thing with the Playlists Folder pref. Also, this isn't just the behavior of the web UI. If I stop the server and manually edit the prefs file, changing paths to their UNC version, then upon startup, SlimServer overwrites UNC paths in the prefs file with mapped drive versions. If I unmap the drive letter for the user account, SlimServer saves the UNC paths correctly, without altering them.
Jim - this is actually a feature. Most of it anyways.. we were finding a lot of people had playlists created by other programs that used the drive letter, but people were entering UNC paths in their music folders.. we need to normalize the path to the drive letter. However - we shouldn't be mapping those UNC paths to drive letters when running as a service. Change 8209 fixes that.
> Jim - this is actually a feature. Most of it anyways.. we were finding a lot of > people had playlists created by other programs that used the drive letter, but > people were entering UNC paths in their music folders.. we need to normalize > the path to the drive letter. I can understand doing that internally, but I think the preference itself should be saved verbatim. > However - we shouldn't be mapping those UNC paths to drive letters when running > as a service. Change 8209 fixes that. Didn't notice that. What happens when someone runs the server from the console with the UNC path mapped to a drive letter for the user, and they run a scan. Won't all paths in the db use the mapped drive letter? Then they fire up SlimServer as a service where the OS no longer understands the mapped drive. Won't all the file paths be invalid?
Subject: Re: UNC paths converted to mapped drive letters when run from console >I can understand doing that internally, but I think the preference itself >should be saved verbatim. Unfortunately not. Again - people enter paths with mixed cases, etc. We need to turn that into a canonical path. >What happens when someone runs the server from the console with the UNC path >mapped to a drive letter for the user, and they run a scan. Won't all paths in >the db use the mapped drive letter? Then they fire up SlimServer as a service >where the OS no longer understands the mapped drive. Won't all the file paths >be invalid? Yes they will be. But how often will that happen? How often will you actually be switching back and forth? If you're keeping up with the latest, I would consider you to be a developer.. just run one or the other. -D -- Sir, are you classified as human? Uhh, negative, I am a meat popsicle.