Hi,
Mathias Bauer wrote on 2010-02-01 09.19:
From a remote view it seems close to impossible that such performance
bug has been introduced. I rather expect that something blocks OOo on
startup until a timeout allows it to proceed.
didn't follow the thread, but just a spontaneous idea if that didn't
come up before:
When the last file path used in OOo is a UNC pathname like
\\myserver\myshare and Windows can't access that path anymore (server
unreachable, name resolution not working etc.), there's usually a
timeout of about 30 seconds. Workaround is to map the UNC patch to a
drive letter, then the timeout occurs immediately.
Florian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
