ph33r my idle process

heh.. I just had to post this ... Im not sure why it ammused me so much, but there ya go.. its a snapshot of the SQL boxen at work.

Yes, we are talking "hours"..

https://forums.windrivers.com/

[quote]Originally posted by EvilCabbage:
<strong>heh.. I just had to post this ... Im not sure why it ammused me so much, but there ya go.. its a snapshot of the SQL boxen at work.

Yes, we are talking "hours"..

http://evilcabbage.freeservers.com/heh.jpg</strong><hr></blockquote>

Can't see the pic? Go <a href="http://evilcabbage.freeservers.com/heh.jpg" target="_blank">here</a>

??? And now I can see it? <img src="confused.gif" border="0">

humm yup thats why you dont use m$ as a server. M$ is not ment for server use.

Actually, that stat looks good to me. 75 days without having to restart is OK, I sometimes have to do a server restart every few weeks to every few months, but you want that Proc idle time to be high, you need to get worried when it's consistently under 40-50, that means other processes are either stuck, misbehaving, hijacking your system or overwhelming your processor and it's time for an upgrade.

[quote]Originally posted by DigitalExpl0it:
<strong>humm yup thats why you dont use m$ as a server. M$ is not ment for server use.</strong><hr></blockquote>

???????

That's like saying Fords were never meant for driving use.

:confused: :confused: :confused:

Chipcreep is right. High idle time means that a fair amount of CPU resources are available for long periods of time. I've seen DC's, PDC's and BDC's have hundreds/thousands of hours in the system idle time before they were bounced. And that was only because company IT policy required them to be rebooted at least once every month or so.

[quote]Originally posted by TTTTTHHHHIIIIISSSLLLOOOONNNNGGGG:
<strong>

???????

That's like saying Fords were never meant for driving use.

:confused: :confused: :confused:

Chipcreep is right. High idle time means that a fair amount of CPU resources are available for long periods of time. I've seen DC's, PDC's and BDC's have hundreds/thousands of hours in the system idle time before they were bounced. And that was only because company IT policy required them to be rebooted at least once every month or so.</strong><hr></blockquote>

M$ = bloated weak server
linux = 1337 server

any questions?

[quote]
<strong> I sometimes have to do a server restart every few weeks to every few months, </strong><hr></blockquote>

See thats the problem, M$ should not be in the server OS. Reboot once a week, once a month come-on. I have 4 unix based system and they hae never been rebooted. Unix server #1 468days uptime. Runs like it was when it was first installed.

<strong> [quote]
That's like saying Fords were never meant for driving use.</strong><hr></blockquote>

Well no, a car is a transporting 4 wheel motorized vehicle. Not a server so there in 2 different worlds, you cannot compare them.

though if you wanted to compare them then say this

M$ = GEO
Unix Based OS = BMW

(as the way they run, not how much they are)

Another thing, why use a non true multi tasking server? wouldnt you want a multi tasking server, makes the loads better.

Damn, I still cant see the pic

I can't see it anymore either..

me neither ......

I can see it.. 1784 hours in the iddle proccess.. Not bad.

[quote]Originally posted by Mayet:
<strong>me neither ......</strong><hr></blockquote>

Um.. works for me? *shrug*

Christ people, forget the M$ VS Linux debate, I realise the limitations of packages just as much as the next guy, but damn, the idle process time ammused the hell out of me...

I still see it. 1784 hours seems a long time to be idle but idle M$ servers don't crash. M$ products get unstable when worked anywheres close to 20% usage of time or resources.

Think that's impressive? check these winning entries from Novell's Netware server uptime contest:

http://www.novell.com/coolsolutions/...rtb_uptime.gif
http://www.novell.com/coolsolutions/...enj_uptime.gif

And yes, we're talking uptime measured in the order of YEARS.

NetWare = rock solid reliability

Good old NetWare 3.1x... if only modern O/Ss were made of the same stuff. Forget Windows 2000 for 99.999% uptime, this one had it ten years ago.

I am with MacGyver on this one. We have one Novell box and one NT box. In the seven months I have been here the Novell was rebooted three times, one because they took electricity out of the whole building, once because we put in 2 new harddrives, and one other because one of those drives went bad. NT, well that gets rebooted on average of once every 2 to 3 weeks. I think I will stick with my Novell thank you very much, too bad M$ pushes their product better than any one else.