I run lxr indexation on regular basis. I would like to know if run was successful or not. Would it be possible to add date/time of last successful run somewhere on the page? Or have a separate page with history of successful/failed runs.
Actually "Or maybe warning on directory
listing page, that not all files are indexed?" might not be so easy to do. Forget it. :)
1- I understand that your main concern is determining if genxref is still running or not. I needed it also. That's why I changed genxref log so that work on a file is only one line long, with colours indicating status (or type of indexing). To quickly have an idea of where genxref is, directory name is repeated every so often the purple lines) so that it remains visible even with scrolling.
Of course, if genxref is launched in the background (or on a remote computer as a batch or cron job), there is no associated terminal and you have no progress output. In that case, you can try 'top' utility (or at least 'ps', but it is not very user-friendly). On Windows, I think your choice is limited to the 'Task manager'.
2- In my test implementation, I record the current time when reference collection terminates. Definition collection is supposed to have been done in a previous pass (the one handled by ctags). Since this previous pass with ctags is quite fast, I thought it was not necessary to log its completion time.
This time-stamp is an individual file property. Consequently, you can use your browser to monitor indexing progress by refreshing a directory page. You'll see the changes in the "Last indexed" column.
As presently implemented, different versions for a file have their own timestamp which are shown if they are OK. With a small smart test, I can make the difference between a file which cannot be indexed because there is no scanner for its language (marked as - in the 'last indexed' column) and a file modified since last genxref (marked as 'Not valid' since displaying the date would need a careful visual comparison between last modification and last indexed dates -- I chose this indication because the date is not important for me if it is stale).
Visually, it is very fast to see which files will give questionable cross-reference results.
3- As soon as I've checked the feature reliability, I'll also implement some flagging in identifier results where it is much more important to know indexing might be wrong when clicking on a line number (which might not jump on the identifier line!).
4- I have not yet reindexed a kernel to measure the performance impact. On my small text cases, it seems negligible but duration is too short to create a real botherance.
I've done the kernel test. Reported time by 'time ./genxref ...' is 2:40:12 instead of 2;39;40, i.e. it is the same within the uncertainty of the measurement. It is quite fun to monitor indexing progress in real time in directory display with a browser.
I proceed with other tests, then I'll implement the warning flag in identifier search.
Implemented in CVS - will be available in release 1.1
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.