• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

D²OL - Question

Don't think you can.
But you could always try using DSpy (here)
It has a logging option and you can view your production as a bar graph, monitor up to 10 remote machines, among other things.

 
No, I don't think you can either. What I did when the client was troublesome was set up an ftp server on my main machine, and a ftp script on each of my nodes running hourly that ftped the stats file (I think) to my server (renamed the existing one to bak first), then compared the two files. I had this running once a day (since I couldn't be bothered to check it more often with the number of nodes I had) and easily identified the stuck machines because the stats file wouldn't have changed over the 1 hour. I used the node number as the file (eg, in the ftp script I had something like this:

delete 12345.bak
rename 12345 12345.bak
put stats.prp 12345

Obviously, on each machine I did this, I needed to tinker just a bit with the ftp script. You can get ftp to use a script by calling

ftp -s scriptname <server-ip>

and put it in the Windows scheduler to run hourly 🙂

Geoff
 
My own solution was a little less technical.. I created a spreadsheet to track all of the rigs with their node numbers, as well as their configurations and such. 😉
 
Back
Top