Who currently has the longest running cow?

GeoffS

Lifer
Oct 10, 1999
11,583
0
71
I've got a c2-633@1g and a c2-566@850 that have been running Klinux uninterupted now for 63 days (the last power outage here!). :)

Geoff
 

TwoFace

Golden Member
May 31, 2000
1,811
0
0
you beat me at least hands down...

<< Dec 10 21:23:10 UTC] RC5: Summary: 2912 packets (12069.00 stats units)
47.13:18:05.50 - [788,509 keys/s
>>

:p

TF
 

GeoffS

Lifer
Oct 10, 1999
11,583
0
71
right on the summary line... Two Face has been running 47 days 13 hours 18 minutes 05.50 seconds (47.13:18:05.50) :)

Geoff
 

GeoffS

Lifer
Oct 10, 1999
11,583
0
71
My full line reads:

Summary: 20858 RC5 packets (54489*2^28 keys)
63.03:00:49.43 - [2.68Mkeys/s]

:)
 

networkman

Lifer
Apr 23, 2000
10,436
1
0
Well, if the term "cow" is referring exclusively to the RC5 project, then I don't have anything running; however, if "cow" can also apply to SETI producers, then I've got one (a dual p3-600) that's been up and going for over six months! :D

 

Eponymous

Golden Member
Jun 7, 2001
1,186
0
0
Sounds like you guys need to run patches on your machines. ;)


Patches??? We don't need no stink'n Patches!
 

TwoFace

Golden Member
May 31, 2000
1,811
0
0
Oh we're talking uptime now? I was certain we were talking cows...

<< # uptime
11:48pm up 102 days, 10:15, 1 user, load average: 1.10, 1.24, 1.18
>>

of course I don't come close to NWM's 6 months or HI's year... but I'm quite satisfied considering that that comp couldn't stay up 12 hours in win9x ;)

Oy, forgot the patch thingie... running debian Eponymous... apt-get update apt-get dist-upgrade and I'm all patched up. No reboot needed for "real" OS's you know ;)

TF
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0


<< Oh we're talking uptime now? I was certain we were talking cows...

<< # uptime
11:48pm up 102 days, 10:15, 1 user, load average: 1.10, 1.24, 1.18
>>

of course I don't come close to NWM's 6 months or HI's year... but I'm quite satisfied considering that that comp couldn't stay up 12 hours in win9x ;)

Oy, forgot the patch thingie... running debian Eponymous... apt-get update apt-get dist-upgrade and I'm all patched up. No reboot needed for "real" OS's you know ;)

TF
>>



My uptimes suck, so I wont post them. Recent installs thats why :p

Anyhow, To upgrade the OS you will need to reboot right now. There are some people working on ways to bring up a new kernel, but its not perfect yet. So even "real" OSes need to be rebooted for a complete upgrade (even without kernel, some running, necessary processes may be updated).
 

GeoffS

Lifer
Oct 10, 1999
11,583
0
71
Well, *I* was talking about cows... RC5/OGR... I don't participate in the other projects... yet! ;)

Geoff
 

BGod

Golden Member
Oct 9, 1999
1,373
35
91
One of my Win2K boxes in the basement:
[Dec 11 01:26:52 UTC] Summary: 50972 RC5 packets (212037*2^28 keys)
142.04:02:24.00 - [4.63 Mkeys/s]

One of my Win98se boxes in the basement:
[Dec 11 01:29:56 UTC] Summary: 32646 RC5 packets (135238*2^28 keys)
141.18:34:31.98 - [2.96 Mkeys/s]

Who ever said that Windows 98 isn't a stable operating system is full of crap!!! :p
 

TwoFace

Golden Member
May 31, 2000
1,811
0
0
Actually n0cmonkey the only reasons I've ever had to reboot my linux box is a new kernel... oh there's ONE other thing I've discovered that requires a reboot, but I didn't have to do it... when using an ide cd-burner in linux it emulates scsi with a line in lilo.conf that you have to reboot to enable... but that line was already in mine before I knew I needed it (one of the few blessings of mandrake ;))

/me will point out this thread to HI so he can put the smackdown on us all with his cow

btw &szlig;G&oslash;d AWESOME 9x uptime!!

TF
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0


<< Actually n0cmonkey the only reasons I've ever had to reboot my linux box is a new kernel... oh there's ONE other thing I've discovered that requires a reboot, but I didn't have to do it... when using an ide cd-burner in linux it emulates scsi with a line in lilo.conf that you have to reboot to enable... but that line was already in mine before I knew I needed it (one of the few blessings of mandrake ;))/me will point out this thread to HI so he can put the smackdown on us all with his cowbtw &szlig;G&oslash;d AWESOME 9x uptime!!TF >>



You're lucky. Of course with linux not having a decent make world you probably dont compile the entire system often do you ;)
 

Crow

Senior member
Nov 17, 1999
218
0
0
Hi

Some details of my 3 dual BP6 comps running on NT4

[Apr 22 02:04:01 UTC] Loaded RC5 32*2^28 packet 251EEB20:70000000
[Apr 22 02:04:01 UTC] Summary: 14922 RC5 packets (183094*2^28 keys)
194.17:49:24.82 - [2.92 Mkeys/s]

[Apr 26 07:37:38 UTC] Loaded RC5 32*2^28 packet 28D4E4A8:70000000
[Apr 26 07:37:38 UTC] Summary: 19128 RC5 packets (212285*2^28 keys)
209.16:12:12.79 - [3.14 Mkeys/s]

[Apr 26 08:15:57 UTC] Loaded RC5 32*2^28 packet 28D547BC:70000000
[Apr 26 08:15:57 UTC] Summary: 19537 RC5 packets (209007*2^28 keys)
209.16:52:34.43 - [3.09 Mkeys/s]

Dual PII 333 running at work

[Apr 17 09:50:06 UTC] 12 RC5 packets (84 work units) remain in buff-in.rc5
[Apr 17 09:50:06 UTC] Projected ideal time to completion: 0.03:19:30.00
[Apr 17 09:50:06 UTC] 1 RC5 packet (16 work units) is in buff-out.rc5
[Apr 17 09:55:59 UTC] *Break* Shutting down...
[Apr 17 09:55:59 UTC] Saved RC5 16*2^28 packet 20A3342A:70000000 (7.70% done)
[Apr 17 09:55:59 UTC] Saved RC5 16*2^28 packet 20A3378B:40000000 (81.40% done)
[Apr 17 09:55:59 UTC] Summary: 17956 RC5 packets (122789*2^28 keys)
203.23:58:23.26 - [1.86 Mkeys/s]
[Apr 17 09:55:59 UTC] 14 RC5 packets (116 work units) are in buff-in.rc5


A lot of the comps at work are over 100 days as we never shut them down.


 

HeavyIron

Senior member
Jan 6, 2000
440
0
0
I smelled some uptime's being thrown around in here and thought I may be able to compete.

I have a little P2-266 running linux and crunching RC5 for the federation that has been running for a little while:
[Dec 11 16:25:13 UTC] Completed RC5 packet D471DB5A:40000000 (2*2^28 keys)
0.00:12:36.07 - [710,080.98 keys/sec]
[Dec 11 16:25:13 UTC] Loaded RC5 1*2^28 packet D471DB5D:00000000
[Dec 11 16:25:13 UTC] Summary: 9261 RC5 packets (54813*2^28 keys)
260.07:44:38.07 - [653.59 kkeys/s]
[Dec 11 16:25:13 UTC] 7 RC5 packets (19 work units) remain in buff-in.rc5
[Dec 11 16:25:13 UTC] Projected ideal time to completion: 0.01:53:22.00
[Dec 11 16:25:13 UTC] 10 RC5 packets (29 work units) are in buff-out.rc5
.....10%.....20%.....30%.

That same box runs a pproxy too:
rc564 r=84983/85000, d=11/100, 22.2 Mkeys/sec, tot=5317796
ogr r=0/0, d=0/0, 4.0 Mnodes/sec, tot=1049 stubs
Status: Uptime: 190.02:02:29, 2 listeners, 0 uplinks
Status: 0 active clients (peak: 8, mean: 0.08)

It also has an uptime of:
[root@stats heavyiron]# uptime
8:35am up 306 days, 20:29, 2 users, load average: 1.21, 1.48, 1.31

I have another linux box with 186 days and running.

Here's a line out of my LAN's setiq:
SetiQueue 3.03.1.7 was last restarted on Mon 2001 Aug 13 8:59:59am (120 days 0 hr 26 min ago)
That's on an NT4 box.
This same box is also crunching for the federation:
[Dec 11 16:10:58 UTC] Completed RC5 packet 9F729D12:C0000000 (1*2^28 keys)
0.00:06:27.96 - [691,901.04 keys/sec]
[Dec 11 16:10:58 UTC] Loaded RC5 6*2^28 packet 9FF23DC8:A0000000
[Dec 11 16:10:58 UTC] Summary: 8143 RC5 packets (26639*2^28 keys)
119.23:03:26.70 - [689.80 kkeys/s]
[Dec 11 16:10:58 UTC] 2 RC5 packets (3 work units) remain in buff-in.rc5
[Dec 11 16:10:58 UTC] Projected ideal time to completion: 0.00:19:15.00
[Dec 11 16:10:58 UTC] 2 RC5 packets (3 work units) are in buff-out.rc5
It is a P2-266 also.

Notice how much better Linux does RC5 over NT4 on these two P2-266's?
Linux = [710,080.98 keys/sec]
NT4 = [691,901.04 keys/sec]
That's +18kkeys/sec ;)
The only reason the overall rate is below the NT's box is because the linux box processes over a years worth of ppstats logs every 15 minutes, kinda pulls down on the available CPU cycles :p

I remember in IRC some time back, SyZ pulled out one or two linux boxes with 400+ days of uptime on 'em
 

RaySun2Be

Lifer
Oct 10, 1999
16,565
6
71
Hiya HeavyIron! :D

You still da man! :D

I'm not even going to publish my feeble uptimes...... ;);)