From 03db05d7a1403392f620fc59111dff35e910b361 Mon Sep 17 00:00:00 2001
From: azurecloudminingscript <azurecloudminingscript@gmail.com>
Date: Sun, 12 May 2019 21:55:58 +0200
Subject: [PATCH]
---
Run_Folding_At_Home_in_the_Azure_Cloud.html | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/Run_Folding_At_Home_in_the_Azure_Cloud.html b/Run_Folding_At_Home_in_the_Azure_Cloud.html
index 6624ac3..60ef861 100644
--- a/Run_Folding_At_Home_in_the_Azure_Cloud.html
+++ b/Run_Folding_At_Home_in_the_Azure_Cloud.html
@@ -276,11 +276,18 @@
</samp>This shows the progress of the work-unit this node is currently
working on. Note that the VMs need some time to setup everything so it
will take several minutes after the start of the node before you can
- see this output in the log. <br>
- </p>
- <h2><strong> </strong> </h2>
+ see this output in the log. </p>
+ <p>You can also have a look at <a href="https://folding.extremeoverclocking.com/">https://folding.extremeoverclocking.com/</a>
+ to see your place in the ranking: if you enter your username in the
+ search-box on the left side your data should show up once you have
+ completed a few WUs.</p>
+ <br>
<h2>Important Notes</h2>
<ul>
+ <li>On the overview-page of your pool your nodes will always show up
+ with the status 'idle'. This is normal (all the work is done through
+ the startup-script, so from Azure's point of view the nodes are idle
+ because there are no individual 'tasks').</li>
<li>Once setup, the VMs will keep on running indefinetely. However, if
you start too many nodes then your free credits will get exhausted
before the end of the month and azure will delete your pools. If
--
GitLab