Ticket #4710 (assigned)
Change the drop out time for when a network is down.
Reported by: | Robert Whitley | Owned by: | Anyone |
---|---|---|---|
Priority: | minor | Milestone: | Backlog |
Component: | Framework | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
Recently '
musr\data' network folder has been down. During that time Mantid took a very long time to start because '
musr\data' was one of the managed directory paths.
Users have told me that during this period they thought Mantid was crashing because it took such a long time.
Investigate why Mantid looks through the managed directory paths at start-up and see if you can change the time taken before ignoring the path and giving a suitable error message.
Change History
comment:1 Changed 9 years ago by Nick Draper
- Owner set to Anyone
- Status changed from new to assigned
comment:2 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:4 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to release 2.4
comment:5 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.4 to Release 2.5
Moved at the code freeze for release 2.4
comment:9 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to the Backlog after the code freeze for R2.6
comment:10 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
bulk move to assigned at the into of the triage step
comment:11 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 5557