Those three lines will tell us wether the user is running Notes 7 or 8, how recent the log is and what MarvelClient release the user is on. C:20110414T101124 B:20110414T102608 //MarvelClient release 02now: 20110425T131632Z //when was the log file started in UTC time - a quick peek tells you whether this is a rather recent log or quite an outdated one 02client: Release 8.5.2FP1|Novem//The exact notes release 2732before login done duration: 63 22832LDR::MCAfterLoginwaiting for local replica scan to finish 22832LDR::MCAfterLoginthread doneĪlso note that at the beginning of each log.xml file, you will find the following important lines:Ġ2 Version 2. Looking at a log file, each line has a millisecond indicator at the beginning, showing the number of milliseconds that have elapsed since the log was started: If you still experience long startup times after updating to >= MarvelClient 2.0.8, then you should look at log.xml of selected end users (it'll be easier if you add log.xml to the backup to analyze job to simply look at log.xml files from within the analyze database).
#Lotus notes 8.5 workspace install
An Eclipse client install typically consists of 3,000 files in the Notes Data\workspace directory in 2,400 directories (out of which 1,850 are empty) - from 2.0.8 on MarvelClient will no longer scan the following directories: Notes Data\Domino, Notes Data\workspace, and Notes Data\IBM_TECHNICAL_SUPPORT, thereby all in all scanning roughly 97% lesser files for a normal end user. For all users with standard Notes 8 clients (=Eclipse client installs), MarvelClient used to scan the entire data directory and everything underneath.Because those databases are often far away or require the client "to find its way through the network to them", this significantly prolongued startup times for admins prior to MC 2.0.8 from 2.0.8 on, MarvelClient by default no longer scans UNC paths For administrators who often have links to UNC paths on the workspace/desktop and/or bookmarks, MarvelClient always scanned those (usually distant or disconnected) databases along with all other local databases.There are several possible causes for why customers may experience longer startup times after deployment of MarvelClient.Ībove all, if you're not yet on at least MarvelClient release 2.0.8: update! MC 2.0.8 and up introduced significant startup time improvements - for details see release notes.
0 kommentar(er)
