View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000280 | MMW v4 | DB/FileMonitor | public | 2003-04-16 15:19 | 2007-02-15 18:37 |
| Reporter | rusty | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Summary | 0000280: New feature: ability to run the File Monitor manually | ||||
| Description | Currently, if the user has 'Scan at Startup' disabled for a folder, the information about what changes occured in that folder prior to startup is lost. This can be very disconcerting to the user who has disabled this function because it takes too long on their collection. One way around this would be to allow the user to initiate the File Monitor manually e.g. a 'Start File Monitor Now' button on the configuration panel. Another possible solution would be to minimize the usability impact of enabling the File Monitor by allowing the user to set the priority of the File Monitor process, so that it doesn't slow down their machine at startup. What do you think? | ||||
| Additional Information | Note: bug #325 supercedes this bug. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
