XnView MP 0.68 unusable slow on startup and image move

[stmork]

XnView MP is really a nice tool since it supports a lot of image formats and is platform independent. I have thousands of images to process but on startup it takes several minutes to get to work. It seems that XnView MP is doing a directory scan of "/". I started XnView from shell so I can recognize always the same output when a delay occures:

Code: Select all

... 
###### onChildrenChecked 0 <actual>
###### onChildrenChecked 6 <svndump>
###### onChildrenChecked 5 <lib32>
###### onChildrenChecked 3 <include>
###### onChildrenChecked 2 <games>
###### onChildrenChecked 1 <bin>
###### onChildrenChecked 9 <sbin>
###### onChildrenChecked 7 <libexec>
###### onChildrenChecked 2 <games>
###### onChildrenChecked 27 <stick>
###### onChildrenChecked 25 <selinux>
###### onChildrenChecked 24 <sbin>
 AFTER WAIT

I assume that XnView MP tries to scan a NFS auto mount point of a machine which is not always online. How can I configure XnView MP in such a way, that it does not scan "/"? Can I configure exclusions?

I'm using the 64-Bit Debian variant of XnView MP 0.68.

[xnview]

yes XnViewMP checks the mount table, so you need a setting to not check it, right?

[qpkorr]

Sorry for reopening an old thread but I think this is exactly my issue - I've got network drives that aren't always accessible, and xnview takes forever to start (running "ls" on "/mnt" is taking 10 seconds and reporting one host timeout so it's clearly not xnview's fault, however...) would it be possible to get that setting to not check the mount table - or perhaps it's already there?

I suppose ideally the mount list would be visible (problematic when running ls takes 10 seconds - but xnview is taking over 5 minutes to bring up its window). xnview shouldn't check any mounted locations until you actually select one since it doesn't matter if they're not accessible if you're not going to select them. I'm not sure how it does it, but doublecmd seems to start immediately and display the full list of mount points, despite "ls" taking 10s for me.

Actually that 5 minutes was somewhere between 5:14 and 5:44 - and I've got 24 shares in fstab that won't come up now. 24 x 10s each = not quite 5 minutes... but might be related?

A setting for this would be much appreciated (since like many now I imagine, I'm working from home and SOMETIMES have work network shares connected via a vpn). Thanks for anything you can do!