| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
For BOINC running on Linux, how much of a problem would the over-writing of a swap file cause? For example, if there is some kind of system problem requiring booting from a Live USB to do system repair, the swap file would likely be over-written by the Live USB boot, clobbering any BOINC stuff on the swap file. What, if anything, would need to be done to recover from this?
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Nothing would need to be recovered. When the system restarts after the repair the BOINC WUs would restart from their last checkpoint. BOINC doesn't use swap directly, it's used by the OS to back main memory frames.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks - that simplifies things. With 20-20 hindsight, I see that according to my system monitor, that 0% of swap is being used, even when boinccmd shows all tasks being "suspended". So the boinc "suspend" uses a different mechanism than the system suspend / hibernate. Good to know.
|
||
|
|
|