Message boards :
Number crunching :
Setting up when boinc should run via command line
Message board moderation
Author | Message |
---|---|
elec999 ![]() Send message Joined: 24 Nov 02 Posts: 375 Credit: 416,969,548 RAC: 141 ![]() ![]() |
Is there anway to setup when boinc should run via command line? |
![]() ![]() ![]() Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 ![]() ![]() |
Is there anyway to setup when boinc should run via command line? Yes. When do you want it to run? Do you want it autostarted via the daemon? Run the binstall.sh script to install the service and start the daemon. Do you want it started as one of your Startup Applications? Use that utility. Are you running headless without the Desktop? Seti@Home classic workunits:20,676 CPU time:74,226 hours ![]() ![]() A proud member of the OFA (Old Farts Association) |
elec999 ![]() Send message Joined: 24 Nov 02 Posts: 375 Credit: 416,969,548 RAC: 141 ![]() ![]() |
sorry i meant to set the days and time to run. |
![]() ![]() ![]() Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 ![]() ![]() |
sorry i meant to set the days and time to run. You would set that normally in the BOINC Manager program Options >> Computing Preferences >> Daily Schedules interface. I don't know if you can set that via the command line. I don't see any mention of that feature in the boinccmd tool cheat sheet. https://boinc.berkeley.edu/wiki/Boinccmd_tool You could just setup a crontab and run the cron job. That is a general tool within Linux and has nothing specific to do with BOINC. Seti@Home classic workunits:20,676 CPU time:74,226 hours ![]() ![]() A proud member of the OFA (Old Farts Association) |
![]() Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 ![]() |
That's part of the global_prefs_override.xml file with this format: <global_preferences> <day_prefs> <day_of_week>0</day_of_week> <start_hour>0.00</start_hour> <end_hour>24.00</end_hour> </day_prefs> <day_prefs> <day_of_week>1</day_of_week> <start_hour>0.00</start_hour> <end_hour>24.00</end_hour> </day_prefs> <day_prefs> <day_of_week>2</day_of_week> <start_hour>0.00</start_hour> <end_hour>24.00</end_hour> </day_prefs> <day_prefs> <day_of_week>3</day_of_week> <start_hour>0.00</start_hour> <end_hour>24.00</end_hour> </day_prefs> <day_prefs> <day_of_week>4</day_of_week> <start_hour>0.00</start_hour> <end_hour>24.00</end_hour> </day_prefs> <day_prefs> <day_of_week>5</day_of_week> <start_hour>0.00</start_hour> <end_hour>24.00</end_hour> </day_prefs> <day_prefs> <day_of_week>6</day_of_week> <start_hour>0.00</start_hour> <end_hour>24.00</end_hour> </day_prefs> </global_preferences> Day 0 is Sunday, day 6 is Saturday If you also want to set when BOINC can use the internet add: <global_preferences> <day_prefs> <day_of_week>0</day_of_week> <start_hour>0.00</start_hour> <end_hour>24.00</end_hour> <net_start_hour>0.00</net_start_hour> <net_end_hour>24:00</net_end_hour> </day_prefs> </global_preferences> |
![]() ![]() ![]() Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 ![]() ![]() |
Wow, cool tip Jord. Didn't know that mechanism at all. So there you go, you have the ability write out that file to run the client when you want from the command line. Seti@Home classic workunits:20,676 CPU time:74,226 hours ![]() ![]() A proud member of the OFA (Old Farts Association) |
![]() Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 ![]() |
I see I made a typo in the latter part. 24:00 should be 24.00 with a decimal point, not a colon. 23:00 is 23.00 23:15 is 23.25 23:30 is 23.50 23:45 is 23.75 23:59 is 23.98 You can extrapolate all times from that. |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.