Only during nights

I want mprime to run only from 5pm to 7 am. What should I do.
mprime -m does not help me

[cheesehead]

Which version are you running? (Recently there were changes in the way schedules are specified.)

The version I used is
Mersenne Prime Test Program, Version 25.7.8

Actually this is since I installed this new version I am no more able to schedule...

[Uncwilly]

Originally Posted by Unregistered

The version I used is
Mersenne Prime Test Program, Version 25.7.8

Actually this is since I installed this new version I am no more able to schedule...

Version 25.7 was the first to drop the time command.

As a non-linux user:
[free advice] you should be able to set up a chron job to start and kill mprime[/free advice].
Hopefully George will set-up the new while/else structure to enable a run/don't run state.

[Prime95]

Use PauseWhileRunning and during/else described in undoc.txt. You want to use the "*" value to match any program. I don't remember the exact syntax.

Thank you for your replies. I am on linux and used crontab with the following table (I want mprime running all the time except between 8am and 17pm on the week days)

00 17 * * 1-5 /home/myself/mprime/mprime
00 08 * * 1-5 /home/myself/bin/kill_mp

My only difficulty was to kill mprime without knowing the job number. I made a script called kill_mp containing

#!/bin/bash
kill -9 $(ps -C mprime -o pid=)

[Brian-E]

Originally Posted by Unregistered

Thank you for your replies. I am on linux and used crontab with the following table (I want mprime running all the time except between 8am and 17pm on the week days)

00 17 * * 1-5 /home/myself/mprime/mprime
00 08 * * 1-5 /home/myself/bin/kill_mp

My only difficulty was to kill mprime without knowing the job number. I made a script called kill_mp containing

#!/bin/bash
kill -9 $(ps -C mprime -o pid=)

I would not advise killing mprime with signal 9. It will not write its save files for one thing, so you will lose work when it restarts, and if it is in the middle of something hefty the results could be disastrous. Just use the default (which is signal number 15, SIGTERM) with the kill statement.

Good, so it is sufficient then that my kill_mp file contains

#!/bin/bash
kill -15 $(ps -C mprime -o pid=)

isn't it?

[jrk]

killall mprime

should suffice.

[Kevin]

In rare cases, users have reported the program can interfere with the
performance of some programs such as disk defragmenters and some games.
You can pause prime95 automatically when these programs are running by
adding this line to prime.txt:
	PauseWhileRunning=prog1[n1],prog2[n2],etc
The [n1], [n2] values are optional and indicate the number of worker threads
to pause when prog1 and prog2 are running.  The default value for n1 and n2
is to pause all worker threads.  Note that prime95 will pause if the program
name matches any part of the running program's file name.  That is "foobar"
will match "c:\foobar.exe", "C:\FOOBAR\name.exe", and even "C:\myfoobarprog.exe".
Also, if prog1 is "*" prime95 will pause no matter what.  Examples:
	PauseWhileRunning=*[1] during 6-7/2:00-3:00
	PauseWhileRunning=* during 23:00-24:00 else decomp[1],mygame[2]
The first example pauses one worker thread on Saturday and Sunday between
2AM and 3AM.  The second example pauses all workers between 11PM and 12AM and
pauses 1 worker if decomp is running and 2 if mygame is running.

[Uncwilly]

Originally Posted by Kevin

In rare cases, users have reported the program can interfere with the

That modification is new since the latest help file I have.