Uptime Program

[Benjamino]

I did a search... but I can't find the uptime thing that you guys are using to display on the forum. Where was that thing?

[MechCD]

tuxtime :D

[verT]

Tuxtime (http://www.tuxtime.dk)

[Miles]

Tuxtime=good :)

[Benjamino]

Alright, teach the bb impaired... What am I doing wrong with the commands?

Edit: I got it... I'm still new at this! :D :rolleyes: :o
Look at that uptime though!!!:) :eek: :p

[verT]

http://www.tuxtime.dk/cgi-bin/uptime.pl?computerid=2320&image=006

To get that you need to do this;

(IMG)http://www.tuxtime.dk/cgi-bin/uptime.pl?computerid=2320&image=006(/IMG)

and replace all round brackets with square ones

[Benjamino]

Thanks man, I wish I had seen your post before I lost all my hair getting it myself.;)
New question then. I can't find a service manager for 2K. I know that it's there somewhere, but it's been too stinkin long. Does Tuxtime load in startup or do I have to tell it to?
:confused: :o

[phil]

Create a shortcut to tuxtime and place it in your startup folder :) Oh, and the secret of a decent uptime is not to use windows.....the damn windows update site makes me reboot everytime :banghead: :banghead:

[Benjamino]

Gee Phil, I'm not an idiot. ;) Is there a Service Manager like on NT though?

BTW: I looked at the top 100 uptimes on Tuxtime... not one M$ machine. Hahahaha...
:rofl: :rofl: :rofl:
:baa:

[verT]

Use Firedaemon, it works really well for creating new services.

[phil]

Originally posted by Benjamino_acid
Gee Phil, I'm not an idiot. ;) Is there a Service Manager like on NT though?

BTW: I looked at the top 100 uptimes on Tuxtime... not one M$ machine. Hahahaha...
:rofl: :rofl: :rofl:
:baa:


LOL!! Ok, you could try Firedaemon as verT suggested - I never really thought about trying that as it starts fine from the startup folder :)

[Benjamino]

When you go to the website, you get these three options.
1.) Latest FireDaemon Release:
v0.09c + UI v1.0R3 Windows NT/2K only

2.) Latest FireDaemon UI:
UI v2.0R12 Windows NT/2K only

3.) Latest FireDaemon Alpha:
v1.5 ARC2 No UI Windows NT/2K/XP March 14 2002

Which one do I want? :confused: :o :ssh:

[phil]

Number 1 :D

[siggy]

Phil what happened to your uptime?

[phil]

Click the "My Farm" link in my sig ;)

[Cherubim]

eeek!
let me guess ... you've got a favor for dual-CPU machines? ;)

Any spare money left?
Just spend it to me, my account has dropped near to ground-zero.

[phil]

LOL!! Any spare money goes on the nectar of the gods (beer) :D

[siggy]

Originally posted by phil
Click the "My Farm" link in my sig ;)
Way cool Phil. :hugz:

[Benjamino]

It's my thread, I can jack it if I want! :D
So I install FireDaemon... I'm smart enough to even get Genome going as a service. But when I rebooted, Genome no starty starty... What gives? Is this more aimed at the long-haul-big-uptime rigs? The ones that are up and nonet for weeks at a time, but folks still work with daily so they don't want to see the winda? (That was a run-on sentence wasn't it? ;))

Once I get all my software situated on 2K then I have resolved to leave the machine up and nonetting for at least a week at a time... but until then I think I just need to stick with seeing the window, it takes too long to make it a service everytime.

BTW: If there is a way to make it start everytime... then let me know. But I also can't end it when it is going. Tells me that access is denied, but I am logged in as Administrator. Although annoying at times, this is kind of a fun project don't you think? Hahaha :D

[Billy_Bat]

Try GenomeSpy, it will tell you that it is running, and lots more info as well. As long as you have g@h set as automatic for start up, it should fire up fine, and be invisible. Pretty fun. I wish there was a program to let me check someof the other machines I have running it via the net.

[phil]

Hey Ben, you don't need to install genome as a service everytime. Once it is installed, you can change it's status via Start > Control Panel > Admin tools > Services. Highlight the service name and right click. Select "Properties" - here you can select the startup type....I recommend "Automatic" which will automatically start the service at boot up. Click start to start the service :rolleyes:. It will keep running even if you log out etc. In fact, you can have a look at this thread for easy to use instructions: http://www.thegenomecollective.com/forum/showthread.php?s=&threadid=1724

HTH :)

[verT]

And if you need to make sure it is running check your Task Manager you'll find that "ghclient" takes 99 percent of CPU resources. To stop the client open a command prompt type "net stop (enter service name here)"

[Louis_Berding2002]

Okay, okay...I'm going to try this tux time for a while and see how I like it....sheesh, anyone have magic beans for sale? Or, maybe a bridge? :rolleyes: :D
:baa: :baa:

[Benjamino]

I'm dumb guys... I found the service about two seconds after posting that. It listed it under FireDaemon - Genome. I was looking for just "Genome". This why I regrett asking questions here...:rofl: :rofl:

[phil]

Originally posted by Benjamino_acid
I'm dumb guys... I found the service about two seconds after posting that. It listed it under FireDaemon - Genome. I was looking for just "Genome". This why I regrett asking questions here...:rofl: :rofl:

:D I did that when I first used Firedaemon....I had like 4 genome services installed before I noticed what had happened :o

[Bruce]

Originally posted by Benjamino_acid
I'm dumb guys...

Don't feel bad. I needed quite a bit of help getting firedaemon set up the first time. Now it seems quite natural.

[dnar]

I played around with the Tuxtime program today. While poking around the site, I noticed something odd here: http://www.tuxtime.dk/index.php?page=top10

How do you guess "dfx" aceived 429 days up when he is running kernel 2.2.20 (a recent release). Either his data entry is screwed, his system is falsely reporting his kernel ID or.... :confused:

[Cherubim]

Originally posted by dnar
How do you guess "dfx" aceived 429 days up when he is running kernel 2.2.20 (a recent release)

His current uptime, running Kernel 2.2.20, is 134 days.
btw: the latest Linux-kernel 2.2.x is 2.2.21.

He may have achieved the 429 days uptime with a different, somewhat older kernel :D

Andy

[dnar]

Originally posted by Cherubim


His current uptime, running Kernel 2.2.20, is 134 days.
btw: the latest Linux-kernel 2.2.x is 2.2.21.

He may have achieved the 429 days uptime with a different, somewhat older kernel :D

Andy
Good point, thats his "best" uptime. I am aware 2.2.21 is the current kernel, but for me, the changes are pointless.