Title says it all!

Where do I find my Weak Key for Rosetta@home? Seems in 2011, there was a mention of upgrading the server software to support them.

So how do I find it?

boinccmd --lookup_account URL email passwd
boinccmd --project_attach URL auth

today rosetta linux participants could only basically run the jobs/tasks with little clue as to what is going on. unlike windows participants who benefits from a cool gui, it'd be great if rosetta@home project could develop a gui say based on java so that more platforms could benefit with a gui of this state-of-the-art project :)

3424: 08-Apr-2014 20:07:11 (low) [rosetta@home] Sending scheduler request: To fetch work.
3425: 08-Apr-2014 20:07:11 (low) [rosetta@home] Requesting new tasks for CPU
3426: 08-Apr-2014 20:07:15 (low) [rosetta@home] Scheduler request completed: got 0 new tasks
3427: 08-Apr-2014 20:07:15 (low) [rosetta@home] No work sent

Computer is connected to the Internet about every [2.0] days
Maintain enough work for an additional [0.0] days

Sounds like a good question for the BOINC message boards.

When you get work loaded, does it process in something pretty close to the initially estimated time? If you recently changed your Rosetta runtime preference that might throw off the BOINC Manager's estimates and cause it not to realize it is going to need work.

I'd suggest adding another day to your work buffer (which is done in the network preferences).

[Unit]
Description=For Rosetta@Home, forces a scheduler request.

[Service]
Type=oneshot
ExecStart=/usr/bin/boinccmd --passwd [from /var/lib/boinc/gui_auth_rpc.cfg] --project http://boinc.bakerlab.org/rosetta/ update

[Unit]
Description=the timer for daily BOINC project updates (currently pegged to the start of the network availability window at slightly after 3am)

[Timer]
OnCalendar=*-*-* 03:01:00
Unit=boinc-scheduler-update.service

[Install]
WantedBy=basic.target

Agreed, but that is more of a BOINC Manager question than Rosetta.

If it gets started on downloads and the network window ends, then it should pick up where it left off the next night (assuming you allow the same time window each night??)

for url in $(boinccmd --get_project_status | sed -n 's/s*master URL: //p'); do
  boinccmd --project ${url} update;
done

If you are running out of work, with a small network window like that, I'd suggest configuring BOINC Manager to keep more days of work on hand setting a larger value in the additional work buffer.