lkml.org 
[lkml]   [1996]   [Jul]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Current 2.0.0 stability indicator -- FYI
Date
>>>>> "Malcolm" == Malcolm Beattie <malcolm.beattie@computing-services.oxford.ac.uk> writes:

> In article
> <Pine.LNX.3.91.960628200938.15516Y-100000@inorganic5.chem.ufl.edu>,
> Jon Lewis <jlewis@inorganic5.fdt.net> wrote:
>> On Fri, 28 Jun 1996, LD Landis wrote:
>>
>>> 8:48am up 12 days, 21:28, 4 users, load average: 0.07, 0.03, 0.00
>> So?
>>
>> Linux crash 2.0.0 #1 Wed Jun 12 17:16:21 EDT 1996 i486 8:24pm up 16
>> days, 1:14, 1 user, load average: 0.13, 0.03, 0.01
>>
>> But can it run a few months _with_ heavy load without tripping up?
>> I don't think so...since a number of 2.0.0 bugs are already known.

> # uptime 10:52am up 47 days, 21:46, 3 users, load average: 0.01,
> 0.00, 0.00 # uname -v #3-pre-2.0 Tue May 14 12:25:10 BST 1996

> Web server with 50000 hits/day; NFS serving to 1000 users with web
> pages.


[root@opera ~]# uptime
6:22pm up 1 day, 3:02, 35 users, load average: 2.53, 2.34, 2.82
[root@opera ~]# uname -a
Linux opera.iinet.net.au 2.0.0 #25- Fri Jun 14 02:45:26 WST 1996 i586
[root@opera ~]# free
total used free shared buffers cached
Mem: 160152 158344 1808 59124 27448 40084
-/+ buffers: 90812 69340
Swap: 259012 35580 223432


Crashed at least 4 times so far. Currently all kernel panics in
skput(). 2 of the other servers running 2.0 have crashed as well, same
thing.

Michael.


\
 
 \ /
  Last update: 2005-03-22 13:37    [W:0.064 / U:3.520 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site