Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 3
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1231 times and has 2 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
BOINC swap file over-writing - how much of a problem?

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?
[Mar 21, 2018 3:11:11 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: BOINC swap file over-writing - how much of a problem?

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.
[Mar 21, 2018 3:34:19 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: BOINC swap file over-writing - how much of a problem?

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.
[Mar 22, 2018 6:22:32 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread