Ticket #192 (closed defect: duplicate)
Scheduler stops if a file in the queue is locked
| Reported by: | jackjack | Owned by: | Joel |
|---|---|---|---|
| Priority: | blocker | Milestone: | Eraser 6.0 |
| Component: | Core | Version: | 6.0.4.875 |
| Keywords: | Cc: | ||
| Processor Architecture: | Blocked By: | ||
| Blocking: | Operating System: |
Description
If a folder listed in schedule contains a file that is locked by another program, eraser will stop the scheduled task rather than skip over the file and erase all other files in the folder.
Eraser should be able to intelligently handle locked files by either 1 skipping over them or 2 being scheduled for removal on reboot before continuing on to remove the remainder of files in the scheduled task
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #192 | └ Scheduler stops if a file in the queue is locked | Eraser 6.0 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #192 | └ Scheduler stops if a file in the queue is locked | Eraser 6.0 |
Change History
Note: See
TracTickets for help on using
tickets.
Confirmed. This is really dangerous. Sensitive data can be left unerased unnoticed while the user is away. This mustn't be in the final release. Therefore changing priority to blocker.
Example dir where this will certainly lead to data being left unerased "C:\Users\<username>\AppData?\Local\Temp\"
Eraser will also stop when sending a list of files via the shell extension to Eraser, the task will stop at the locked file leaving the following files untouched.