I would hope that if you have an R script that is running for a month that you have built in periodic checkpoints so that you can recover what is happening. In cases where I want to be able to restart an R script at some point downstream, I will "save.image", or just the objects that are important, and then I can reload at that point and carry forward. Also you will have the objects that you need to examine if you have too. If I had something running that long, I would at least take a checkpoint every hour to help in the debugging/recovery process.
Jim Holtman Data Munger Guru What is the problem that you are trying to solve? Tell me what you want to do, not how you want to do it. On Sun, Dec 18, 2016 at 2:22 PM, Ragia . <ragi...@hotmail.com> wrote: > > Dear group > I had a tmux session, on it an R script is running before the program > should ends > > on the screen written "killed" and the script terminated and returned bake > to bash (in the same tmux window) > > Q: how can I re attach into the killed R session and check it? can I > recover what was the script doing for more than a month now ? > any ideas? > THANS > > > Ragia A. Ibrahim > > > > [[alternative HTML version deleted]] > > ______________________________________________ > R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see > https://stat.ethz.ch/mailman/listinfo/r-help > PLEASE do read the posting guide http://www.R-project.org/ > posting-guide.html > and provide commented, minimal, self-contained, reproducible code. > [[alternative HTML version deleted]] ______________________________________________ R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.