2011-09-30, 01:02
Hi guys,
I did a quick search and didn't see this logged, so please let me know if this has already been logged/addressed, and, of course, if you think this is just not required.
I like to automate updating the library and cleaning the library so I don't have to manually do it.
However, you can run into issues if using network shares for your sources, and Windows, for some reason, can't reconnect the shares (either on boot / coming out of suspend/sleep etc..).
If your sources are now down, xbmc can't get to them on start, and will update/clean your library accordingly (i.e. empty the database if you have update & clean on startup set).
What do you think about using the following process instead?
If update/clean libary on startup is enabled, but the added sources are not found, then do nothing.
Or preferably, notify the user that the sources are missing and ask if he/she wants to reset the library, or cancel the update/clean.
Or something to that effect.
Just as a safeguard against having to rebuild the database in case networked drives don't connect.
Your thoughts?
I did a quick search and didn't see this logged, so please let me know if this has already been logged/addressed, and, of course, if you think this is just not required.
I like to automate updating the library and cleaning the library so I don't have to manually do it.
However, you can run into issues if using network shares for your sources, and Windows, for some reason, can't reconnect the shares (either on boot / coming out of suspend/sleep etc..).
If your sources are now down, xbmc can't get to them on start, and will update/clean your library accordingly (i.e. empty the database if you have update & clean on startup set).
What do you think about using the following process instead?
If update/clean libary on startup is enabled, but the added sources are not found, then do nothing.
Or preferably, notify the user that the sources are missing and ask if he/she wants to reset the library, or cancel the update/clean.
Or something to that effect.
Just as a safeguard against having to rebuild the database in case networked drives don't connect.
Your thoughts?