Unitinfo.txt

RobOC · 28 Jul 2006 at 23:55

Anyone know if there is a standard time for how often unitinfo.txt is updated, or whether it is down to individual cores? Seems pretty random. Anyone know of a way to make it update more often?

RobOC · 29 Jul 2006 at 00:01

Oh ok so if I am on a long WU it could take a while between updates.

RobOC · 29 Jul 2006 at 00:08

It might seem a random question. The reason i ask is because on my stats page (link at the bottom) I am putting all the threads I am running, and I detect if they are down by the create time on the unitinfo.txt. But I keep getting them displaying as 'down' because I am using an hour as the stale data time before setting them as down. Apparently some unitinfo.txt updates take longer than an hour. I'll have to think of a better way to detect the process status. Means actually doing something proper though

RobOC · 29 Jul 2006 at 00:10

At present one of the unitinfo.txt's hasn't updated since 22:45 and it is 00:09... so some cores must take quite some time per %/frame.

RobOC · 29 Jul 2006 at 00:18

Hmm those 600pt units should only take a max of a couple of days on those rigs. The reasoning behind that page is that one of those machines was remotely restarted a couple of days ago and the processes didn't start up again properly and I didn't notice. A good couple of days lost crunching. That might be why it looks like they'll take ages to finish, they've been down for a while :rolleyes:

RobOC · 29 Jul 2006 at 00:26

Ahhh I like your style. Good idea

I was just getting into doing px aux | greps to see if the process is running etc. I'll give that a go.

RobOC · 29 Jul 2006 at 00:33

That worked a treat. FAHlog is a bit bigger to upload but not by much. Good stuff, it'll do for my purposes.

ta!

RobOC · 29 Jul 2006 at 13:11

Hey, yeah that's useful thanks. Might add some kind of service bouncing to the scripts which SCP the files in, to maintain the log file sizes.