2009/5/27 Glen Barber glen.j.bar...@gmail.com:
On Tue, May 26, 2009 at 11:23 PM, Polytropon free...@edvax.de wrote:
Maybe there's a way of patching the uptime utility that it adds
the previous uptime of the system (since last shutdown) to the
actual uptime. I know this denies everything uptime
Chris Rees wrote:
2009/5/27 Glen Barber glen.j.bar...@gmail.com:
On Tue, May 26, 2009 at 11:23 PM, Polytropon free...@edvax.de wrote:
Maybe there's a way of patching the uptime utility that it adds
the previous uptime of the system (since last shutdown) to the
actual uptime. I know this
Hi, Chris
On Wed, May 27, 2009 at 9:45 AM, Chris Rees utis...@googlemail.com wrote:
I like that idea, actually.. Not for faking cumulative uptime. It'd
be kinda nice knowing how long a particular machine has been 'alive'
without looking through service tag records.
How about:
On Wed, May 27, 2009 at 9:56 AM, Steve Bertrand st...@ibctech.ca wrote:
Not really a biggie, I've got another test box right behind it ;)
ww9# uptime
9:09AM up 501 days, 22:20, 1 user, load averages: 0.00, 0.00, 0.00
Due to network restructuring, the test hardware will be coming out...
On Wed, May 27, 2009 at 8:45 AM, Chris Rees utis...@googlemail.com wrote:
2009/5/27 Glen Barber glen.j.bar...@gmail.com:
On Tue, May 26, 2009 at 11:23 PM, Polytropon free...@edvax.de wrote:
Maybe there's a way of patching the uptime utility that it adds
the previous uptime of the system
Glen Barber wrote:
On Wed, May 27, 2009 at 9:56 AM, Steve Bertrand st...@ibctech.ca wrote:
Not really a biggie, I've got another test box right behind it ;)
ww9# uptime
9:09AM up 501 days, 22:20, 1 user, load averages: 0.00, 0.00, 0.00
Due to network restructuring, the test hardware will
2009/5/27 Andrew Gould andrewlylego...@gmail.com:
On Wed, May 27, 2009 at 8:45 AM, Chris Rees utis...@googlemail.com wrote:
2009/5/27 Glen Barber glen.j.bar...@gmail.com:
On Tue, May 26, 2009 at 11:23 PM, Polytropon free...@edvax.de wrote:
Maybe there's a way of patching the uptime utility
radius# uptime
11:01PM up 553 days, 13:38, 1 user, load averages: 0.00, 0.00, 0.00
very good result, but thinking that way is quite a nonsense. you have to
shut down, then just shut down!
if you want to talk about how well your server works, how stable it is and
how good admin are you,
Maybe there's a way of patching the uptime utility that it adds
the previous uptime of the system (since last shutdown) to the
actual uptime. I know this denies everything uptime stands for,
let's call it accumulated uptime. :-)
if it will add only in case of clean shutdown - it would be good.
On Wed, May 27, 2009 at 10:06 AM, Steve Bertrand st...@ibctech.ca wrote:
Glen Barber wrote:
Steve,
Just out of curiosity, what function did 'radius' serve?
RADIUS ;)
I didn't think it could be that easy. :)
--
Glen Barber
___
On Wed, 27 May 2009 09:02:08 -0500, Andrew Gould andrewlylego...@gmail.com
wrote:
You could write a script that sends uptime output and a start/stop flag to a
database when the system starts and stops. This wouldn't account for
improper shutdowns, although you could tell when a stop date/time
On Tue, 26 May 2009 23:14:10 -0400,
Steve Bertrand st...@ibctech.ca said:
S Just a little bit of sadness of having to 'down' it, given this uptime in
S my relatively hostile environment. *sigh*
I'll match your sigh and add some curse-words. One of our fileservers:
date: Mon May 18
On Wed, 27 May 2009 09:02:08 -0500,
Andrew Gould andrewlylego...@gmail.com said:
A You could write a script that sends uptime output and a start/stop
A flag to a database when the system starts and stops. This wouldn't
A account for improper shutdowns, although you could tell when a stop
A
date: Mon May 18 09:03:09 EDT 2009
uname: FreeBSD 4.9-RELEASE #0
uptime: 9:03AM up 732 days, 11:36, 0 users
Hardly possible in Poland. i can't imagine 2 years without power failures
:)
___
freebsd-questions@freebsd.org mailing list
On Wed, May 27, 2009 at 5:00 PM, Karl Vogel vogelke+u...@pobox.com wrote:
On Wed, 27 May 2009 09:02:08 -0500,
Andrew Gould andrewlylego...@gmail.com said:
A You could write a script that sends uptime output and a start/stop
A flag to a database when the system starts and stops. This wouldn't
I have a script which runs fping on a bunch of servers and writes
a timestamp for any host that answers. It's run every minute from
cron on our loghost. Another script watches the results and sends
me an IM if any of my boxes fails to respond for 3 minutes.
I can put up a
...unfortunately, due to re-racking and upgrade requirements, I have to
pull the plug. There is nothing hidden or obfuscated in my output, and I
am not ashamed of that.
Just a little bit of sadness of having to 'down' it, given this uptime
in my relatively hostile environment. *sigh*
I know this
On Tue, 26 May 2009 23:14:10 -0400, Steve Bertrand st...@ibctech.ca wrote:
...unfortunately, due to re-racking and upgrade requirements, I have to
pull the plug. There is nothing hidden or obfuscated in my output, and I
am not ashamed of that.
Maybe there's a way of patching the uptime utility
Polytropon wrote:
On Tue, 26 May 2009 23:14:10 -0400, Steve Bertrand st...@ibctech.ca wrote:
...unfortunately, due to re-racking and upgrade requirements, I have to
pull the plug. There is nothing hidden or obfuscated in my output, and I
am not ashamed of that.
Maybe there's a way of
Steve Bertrand wrote:
[..snip..]
Just a little bit of sadness of having to 'down' it,
[..snip..]
radius# uptime
1:19AM up 553 days, 15:56, 1 user, load averages: 0.00, 0.00, 0.00
:(
radius# halt
smime.p7s
Description: S/MIME Cryptographic Signature
Steve,
On Wed, May 27, 2009 at 1:22 AM, Steve Bertrand st...@ibctech.ca wrote:
Steve Bertrand wrote:
[..snip..]
Just a little bit of sadness of having to 'down' it,
[..snip..]
radius# uptime
1:19AM up 553 days, 15:56, 1 user, load averages: 0.00, 0.00, 0.00
:(
radius# halt
That
On Tue, May 26, 2009 at 11:23 PM, Polytropon free...@edvax.de wrote:
Maybe there's a way of patching the uptime utility that it adds
the previous uptime of the system (since last shutdown) to the
actual uptime. I know this denies everything uptime stands for,
let's call it accumulated uptime.
22 matches
Mail list logo
