On a related note, has anybody tried if MISFIT would get assignments from James' site? I don't see why not, with the right settings in the config file, so you don't need batch files and all the stuff. There may be some troubles with the format of the returned file (maybe MISFIT won't parse it properly) but in this case, Scott is known to fix bugs just before we report them... (no joke, hehe, it happened in the past), just PM him.

James has also been known to be happy to modify his site as needed, and could easily tweak the output to be MISFIT-friendly if told what needs to be changed.

Since it doesn't seem to have been mentioned, on Linux/most-or-all other Unices, Ctrl+Z in a terminal will pause the current running job (technically: move it to background), which can be resumed at any time with the command [c]fg[/c]. I use this frequently and for a wide variety of programs in use on this forum, including mfaktc back when I ran that.

[QUOTE=James Heinrich;472904]James has also been known to be happy to modify his site as needed, and could easily tweak the output to be MISFIT-friendly if told what needs to be changed.[/QUOTE]
:tu: Why not? We notified Scott, he can take over if his time allows, I know he is a busy guy right now... Maybe this could be seen like a "re-launch" of MISFIT, with some new publicity, that could attract some guyz and galz who want to find lots of factors, and want to give some utility to their long-forgot 580s.

[QUOTE=Mark Rose;472898]I wrote scripts that stop mfaktc on my primary GPU when I unlock my screensaver and resume on lock.[/QUOTE]
I don't use screensaver at home because I prefer to use all the available resources for BOINC. I type Alt+Ctrl+F1 too, I think it should help, but I'm not sure. Maybe I should turn xorg off in some way.
Anyway could you link your command or script?

[QUOTE=Dubslow;472911]Since it doesn't seem to have been mentioned, on Linux/most-or-all other Unices, Ctrl+Z in a terminal will pause the current running job (technically: move it to background), which can be resumed at any time with the command [c]fg[/c]. I use this frequently and for a wide variety of programs in use on this forum, including mfaktc back when I ran that.[/QUOTE]
Good! You confirm what I found yesterday: [url]https://askubuntu.com/questions/277714/is-there-a-super-break-key-for-bash[/url]
I didn't tried it though because I was waiting for a new TF test to test those commands. I didn't want to mess a running test.

[QUOTE=Dubslow;472911]Since it doesn't seem to have been mentioned, on Linux/most-or-all other Unices, Ctrl+Z in a terminal will pause the current running job (technically: move it to background), which can be resumed at any time with the command [c]fg[/c]. I use this frequently and for a wide variety of programs in use on this forum, including mfaktc back when I ran that.[/QUOTE]

No, it merely pauses the program.

It can be run in the background with the command [c]bg[/c]. This is the same as if the program had originally been started with [c]&[/c] at the end of the command line.

If you pause multiple programs you can run the command [c]jobs[/c] to see them as a numbered list. The [c]fg[/c] and [c]bg[/c] commands can specify a particular paused program out of the list, for instance [c]fg %1[/c]

[QUOTE=GP2;472940]No, it merely pauses the program.

It can be run in the background with the command [c]bg[/c]. This is the same as if the program had originally been started with [c]&[/c] at the end of the command line.

If you pause multiple programs you can run the command [c]jobs[/c] to see them as a numbered list. The [c]fg[/c] and [c]bg[/c] commands can specify a particular paused program out of the list, for instance [c]fg %1[/c][/QUOTE]

Ah, my ad hoc "understanding" rears its ugly head :smile:

So what you're saying is that the name "fg" is overloaded to perform the two very-similar-if-technically-not-identical tasks of resuming a paused program and restoring a background-ed (but still running) task to foreground/direct attachment to the terminal?

[QUOTE=Dubslow;472943]So what you're saying is that the name "fg" is overloaded to perform the two very-similar-if-technically-not-identical tasks of resuming a paused program and restoring a background-ed (but still running) task to foreground/direct attachment to the terminal?[/QUOTE]

Yes, exactly.

If you run the [c]jobs[/c] command, the paused programs have the status "Stopped", while the programs running in the background have the status "Running". Either way, they can be made to run in the foreground with [c]fg[/c]


On a related note, programs that aren't attached to a terminal can also be paused and resumed. For example, if you have mprime start up automatically when the system boots.

First find out the process id, for example [c]ps -C mprime[/c] and let's assume it's 9876. Then you can do [c]kill -s SIGSTOP 9876[/c] to pause it, and [c]kill -s SIGCONT 9876[/c] to resume it.

You can check the state, for example with [c]ps -C mprime -o pid=,state=[/c] and the result will usually be S (for sleeping) or R (for running). After you send the SIGSTOP, the state will be T (stopped by job control signal).

Suspending the mprime program that runs automatically at system initialization can be useful if, for instance, you want to start up another mprime manually in order to run a benchmark. Just don't forget to resume it later with SIGCONT.

[QUOTE=GP2;472962]Either way, they can be made to run in the foreground with [c]fg[/c][/QUOTE]

Somewhat related... You can STOP a job from another console using the [c]kill -STOP [PID][/c] command. When I am going to be away from my main workstation for a while I often run [c]killall -STOP "Web Content"[/c] to prevent the Firefox rendering process from eating unnecessary cycles. When I return I run [c]killall -CONT "Web Content"[/c].

Edit: LOL... Cross post with GP2.

[QUOTE=Luis;472934]I don't use screensaver at home because I prefer to use all the available resources for BOINC. I type Alt+Ctrl+F1 too, I think it should help, but I'm not sure. Maybe I should turn xorg off in some way.
Anyway could you link your command or script?[/QUOTE]

Not much to share. I have a simple shell script that starts mfaktc in a screen session and another simple shell script that runs killall. I execute these though KDE events.

[QUOTE=James Heinrich;472855]If you do translate it please send me a copy so I can make it available for others.[/QUOTE]

Here it is.

It works for me (Xubuntu). It should work for Debian-like OS's.

I have started to implement an option for ramdisk.
I don't know how to manage ctrl-C. I should delete some important files from ramdisk:
-worktodo.txt: unreserve exponents or copy to mfaktc original directory?
-results.txt: upload, but what if curl would fail? Or copy to mfaktc original directory?

If someone wants to modify it, he/she is welcome.