Menu
▾
▴
#9 split_path() err in editLoadAutoscanDirectory()
[ from both Debian etch i386 pkg, and self-compiled ppc
mediatomb ]
Under 'Filesystem', choose the circled '+' to configure scan options for a selected directory. When choosing either 'Timed' or 'Inotify', then the 'Set' button, an error dialog box with the message 'Error: relative path given to split_path()', forcing an 'OK' response to do anything else.
Logged In: YES
user_id=1846577
Originator: YES
ps - this is with the current mediatomb 0.10.0
Logged In: YES
user_id=1205152
Originator: NO
Does that happen for any path or only with specific ones?
Do you know what path it is, where it is failing? (i.e. what's the name of it?)
What does the console say, do you see an exception or an ERROR printout?
I think that it probably throws an exception, if you compile with --enable-tombdebug you could use the traceinfo script to get a nice trace, that would help us a lot.
Thanks for the bug report!
Jin
Logged In: YES
user_id=1846577
Originator: YES
On further investigation, it appears this is only with the / ( /Filesystem ) node. Of course, since this is
the one I'm most interested in at the moment, it's also the most problematic :=)
Logged In: YES
user_id=1205152
Originator: NO
OK, I think now I understand your problem. Originally we did not want to allow adding the root as autoscan, I think we forgot to remove the icon when filesystem root is selected.
The error message should also not be that cryptic...
It makes no sense to add the whole root as autoscan, you would be adding tons of files and directories to the server that are actually not media files - why would you want to do that? The size of the directory tree that you are setting to watch may also have an impact on memory use and performance, so I would not "add everything as autoscan" but rather carefully select the directories that hold your media.
I am not sure what we decided (regarding the FS root and autoscan), but for sure it should either allow it, or print an appropriate error message.
Logged In: YES
user_id=1846577
Originator: YES
But if I #define FS_ROOT_DIRECTORY "/nethdd/" to be something other than "/" (say, for an embedded NAS box where the OS partition is to be excluded), then the user's data partition (eg; "/nethdd") may indeed be an appropriate pseudo-root to autoscan,
Logged In: YES
user_id=1205152
Originator: NO
Well, that's a whole different topic ;)
We plan to add a "chroot" feature which will handle stuff like that correctly. But that's for the future :> Actually not sure if everything will work correctly if you change the FS_ROOT_DIRECTORY define, I do not think that this has been fully tested.
This specific problem has been fixed, but an autoscan on "/" still won't work. see bug #2938866 for that