![]() |
screen running mprime disappears
I've been running the dream machine for a year. It was recommended that I use crontab and screen to start mprime:
[CODE]@reboot screen -S mprime -d -m /home/george/prime95/mprime -d[/CODE] On 6 CPUs I've had nary a problem. On the 7th CPU, four times I've discovered that screen is not running. Three of those times was after a reboot. One of those times it was after the machine was running for 7 days. How can I figure out why mprime or screen is aborting without a trace? |
[QUOTE=Prime95;454066]How can I figure out why mprime or screen is aborting without a trace?[/QUOTE]
Unless you need interactive console control of the process, screen is a bit of overkill; and it doesn't provide great logging. I usually run mprime something like:[CODE]./mprime -d </dev/null >>mprime.log 2>>mprimee.log &[/CODE] You can then tail / grep through the log files at any time for diagnostics. |
[QUOTE=Prime95;454066]
How can I figure out why mprime or screen is aborting without a trace?[/QUOTE] Have you tried enabling logging? something along [CODE]@reboot screen [B][COLOR="Red"]-L[/COLOR][/B] -S mprime -d -m /home/george/prime95/mprime -d[/CODE] This should turn on automatic output logging for the windows, and direct it to a screenlog.n (n = window number) in your home folder - and maybe give you some hints about what happens |
[QUOTE=ric;454173]Have you tried enabling logging? [/QUOTE]
Thanks, I'll try that. It could be months before it happens again, so success/failure feedback may be a bit slow! |
| All times are UTC. The time now is 08:58. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.