On Fri, 15 Jun 2012 19:00:57 -0500, David Brodbeck g...@gull.us wrote:
Hard to get unless you have several kilobucks to spend on an online
type UPS, though. I actually had one I got surplus, several years
back, but the constant inverter buzz got old fast in a home
environment.
Refurbups.com
From owner-freebsd-questi...@freebsd.org Thu Jun 14 22:56:16 2012
To: freebsd-questions@freebsd.org
Date: Thu, 14 Jun 2012 22:51:45 -0500
From: Mark Felder f...@feld.me
Cc: Steve Bertrand steve.bertr...@gmail.com
Subject: Re: Uptime [OT]
FreeBSD REDACTED 6.0-RELEASE FreeBSD 6.0-RELEASE #0
. Too bad it will be
moved to another physical location in a week or two.
$ uptime
2:38PM up 2266 days, 20:43, 1 user, load averages: 0.00, 0.00, 0.00
Disclaimer: http://www.ose.nl/email
___
freebsd-questions@freebsd.org mailing list
http
On Thu, Jun 14, 2012 at 09:20:19PM -0600, Steve Bertrand wrote:
I still have non-root access to a box from my old job... it is
non-available and doing nothing, so updates are irrelevant:
%uptime
9:01PM up 1142 days, 5:29, 1 user, load averages: 0.00, 0.00, 0.00
Hmm. My longest uptime
, the hardware it's running on is old enough to
vote. wry grin
It's publicly accessible on the Internet,
It's not quite as ridiculous as it looks, the (limited) apps running on it
_are_ up-to-date.
Uptime is nothing to brag about -- no UPS, combined with 'unreliable' public
utility
On 06/15/2012 08:30, Bernt Hansson wrote:
Aha.A pissing contest and it's fridaycount me in...
FreeBSD fqdn 4.11-RELEASE-p20 FreeBSD 4.11-RELEASE-p20 #0: Mon Aug 28
07:21:42 CEST 2006 user@fqdn:/usr/obj/usr/src/sys/HPNETSERVERFW i386
On Friday 15 June 2012 09:49:49 Robert Bonomi wrote:
From owner-freebsd-questi...@freebsd.org Thu Jun 14 22:56:16 2012
To: freebsd-questions@freebsd.org
Date: Thu, 14 Jun 2012 22:51:45 -0500
From: Mark Felder f...@feld.me
Cc: Steve Bertrand steve.bertr...@gmail.com
Subject: Re: Uptime
On Fri, Jun 15, 2012 at 4:00 PM, Chad Perrin per...@apotheon.com wrote:
No power conditioning (implied by no UPS) is nothing to brag about.
If your utility power is very -- common now in places with buried
utilities -- a UPS of the non-enterprise variety can actually make
reliability *worse*.
On Fri, Jun 15, 2012 at 11:47 PM, David Brodbeck g...@gull.us wrote:
On Fri, Jun 15, 2012 at 4:00 PM, Chad Perrin per...@apotheon.com wrote:
No power conditioning (implied by no UPS) is nothing to brag about.
If your utility power is very -- common now in places with buried
utilities -- a UPS
On Fri, Jun 15, 2012 at 11:47:55PM +, David Brodbeck wrote:
On Fri, Jun 15, 2012 at 4:00 PM, Chad Perrin per...@apotheon.com wrote:
No power conditioning (implied by no UPS) is nothing to brag about.
If your utility power is very -- common now in places with buried
utilities -- a UPS of
On Fri, Jun 15, 2012 at 11:54 PM, Chad Perrin per...@apotheon.com wrote:
I don't consider the ability to stay up for a few minutes when there's a
brief blackout to be the most important function of a good UPS, even
though that's kinda the reason the things were invented in the first
place.
I still have non-root access to a box from my old job... it is
non-available and doing nothing, so updates are irrelevant:
%uptime
9:01PM up 1142 days, 5:29, 1 user, load averages: 0.00, 0.00, 0.00
Steve
___
freebsd-questions@freebsd.org mailing
In production and survived many area-wide power outages:
% uptime
10:34PM up 2021 days, 18:02, 1 user, load averages: 0.00, 0.00, 0.00
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
On 14/06/2012 9:20 PM, Steve Bertrand wrote:
I still have non-root access to a box from my old job... it is
non-available and doing nothing, so updates are irrelevant:
%uptime
9:01PM up 1142 days, 5:29, 1 user, load averages: 0.00, 0.00, 0.00
fwiw:
%uname -a
FreeBSD ..xxx 7.2
On 14/06/2012 9:35 PM, Mark Felder wrote:
In production and survived many area-wide power outages:
% uptime
10:34PM up 2021 days, 18:02, 1 user, load averages: 0.00, 0.00, 0.00
That's hardcore homie... wow!
What does this box survive to do?
Steve
is
quickly aging. The dual power supply has saved it a few times, too. I
think there's another server which I believe is close to 2600 days uptime
but I'll have to brainstorm and see if I can remember which one it is.
___
freebsd-questions
FreeBSD REDACTED 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Wed Nov 15 16:29:10
CST 2006 root@REDACTED:/usr/src/sys/i386/compile/IPFW-POLING-ALTQ i386
Theres no way I'm giving out the organization name or hostname haha. We're
slowly moving customers away from this device, but not forcing anyone.
. There isn't much load at all, but the hardware
is quickly aging. The dual power supply has saved it a few times, too. I
think there's another server which I believe is close to 2600 days
uptime but I'll have to brainstorm and see if I can remember which one
it is.
lmao... you must be a sysadmin ;)
IPFW
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
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:
[ch
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
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
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
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
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. :-)
Nah, uptime is uptime. Uptime was never my intention, it just worked.
There have been times
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
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
On Monday 15 December 2008 15:09:31 Polytropon wrote:
Hi!
I'm going to setup a system with a dial-up modem for sporadic
Internet access; a provider that charges per second online time
is used. Is there a way ppp (which is used for dialing) can log
the online time (or at least the
Hi!
I'm going to setup a system with a dial-up modem for sporadic
Internet access; a provider that charges per second online time
is used. Is there a way ppp (which is used for dialing) can log
the online time (or at least the connection's start and stop time)
so the costs can be calculated?
I'm going to setup a system with a dial-up modem for sporadic
Internet access; a provider that charges per second online time
is used. Is there a way ppp (which is used for dialing) can log
the online time (or at least the connection's start and stop time)
so the costs can be calculated?
Many thanks for your ideas. I think I'll use #2 and have start
and stop time recorded in epoch format (because its easy to
get the substraction result instead of fiddling around with
date's ymdhms parameters).
This is because I'm not very familiar with ppp's logs, and
maybe they provide the
On Thu, 2008-10-09 at 10:52 -0400, Mikel King wrote:
On Oct 8, 2008, at 9:00 PM, Chad Marshall wrote:
No Problem, I figured that there are other systems out there
with a
longer uptime. I have this server as a
postfix/courier-imap
On Thu, 2008-10-09 at 10:03 -0500, Paul Schmehl wrote:
--On Thursday, October 09, 2008 09:34:02 -0500 Jerry
McAllister
[EMAIL PROTECTED] wrote:
On Thu, Oct 09, 2008 at 07:07:31AM -0700, Chad Marshall
wrote:
On Thu, 2008-10-09 at 07:50 -0700, Chad Marshall wrote:
Here's what I said to the last guy who says my skin is thin,
just
leave well enough alone and drop it please. Seems your skin is
thin as
well if you can't handle a little back talk :)
I love the direction this thread has taken. First, humorous,
then it
will turn into flames. I bet all my US$:-)
Unfortunately that doesn't really offer much value anymore with
the
recent market downturn- got anything else to
Zbigniew Szalbot:
2008/10/9 Jon Radel:
Dear Mr. Marshall:
I'm terribly sorry that our representatives in charge of answering emails
have been rude to you. I've just fired the lot of them, particularly as we
can't afford to keep then on anymore seeing as how your generous donations
are now in
was worth a read. It wasn't worth a response,
espically escalated to the rediculousness that some have
been. Did anyone bother to think that any admin with
2 years uptime on a system probably has some decent coin
into the environment (think, UPS power here) and more like
as not knows what
Sorry to bother you...You know, you could just leave well enough
alone if you don't care. There goes any future donations from me and
my organization as this is more than the first untactful email I
recieved from this, I'll donate and use other platforms. Please don't
send any other
On Behalf Of matt donovan
why is this news or even important? heck most servers
are up longer then this.
It's neither. But the discussion proved useful as it served to remind me
that there are security updates that need to be reviewed periodically,
even for machines that are not directly
On Thu, Oct 09, 2008 at 07:07:31AM -0700, Chad Marshall wrote:
Sorry to bother you...You know, you could just leave well enough
alone if you don't care. There goes any future donations from me and
my organization as this is more than the first untactful email I
recieved from this,
On Thu, Oct 09, 2008 at 07:07:31AM -0700, Chad Marshall wrote:
Sorry to bother you...You know, you could just leave well enough
alone if you don't care. There goes any future donations from me and
my organization as this is more than the first untactful email I
recieved from this,
Eitan Adler [EMAIL PROTECTED] writes:
andrew clarke wrote:
Is FreeBSD 7.1 2038-proof? ;-)
As far as I know the amd64 version is (anyone care to verify/correct?)
All 64-bit platforms have 64-bit time_t, so that covers most of the
possible problems. Even on 32-bit platforms, the major
Here's what I said to the last guy who says my skin is thin, just
leave well enough alone and drop it please. Seems your skin is thin as
well if you can't handle a little back talk :)
Well, I can always except critism. The problem is that I don't need
rude responses for something I thought
On Oct 8, 2008, at 9:00 PM, Chad Marshall wrote:
No Problem, I figured that there are other systems out there with a
longer uptime. I have this server as a postfix/courier-imap/
squirrelmail (60+ accounts and 30-40 forwards) mailserver with
apache/php/mysql. Also use it as a slave
--On Thursday, October 09, 2008 09:34:02 -0500 Jerry McAllister
[EMAIL PROTECTED] wrote:
On Thu, Oct 09, 2008 at 07:07:31AM -0700, Chad Marshall wrote:
Sorry to bother you...You know, you could just leave well enough
alone if you don't care. There goes any future donations from me and
my
when thanks to this list I have learnt something
useful or was given useful advice. And two years ago I knew nothing
about Unix or Linux. Thanks to this list I can manage FreeBSD (almost)
on my own. :)
But the discussion that followed made me realize that uptime is not
everything. I also love to see
--- On Thu, 10/9/08, Chad Marshall [EMAIL PROTECTED] wrote:
Maybe you should put someone in charge of answering emails
who aren't
cocky and smug
This is a public mailing list. No one is in charge of answering mails to it.
When sending to -questions, you are emailing the community of
Chad Marshall wrote:
Here's what I said to the last guy who says my skin is thin, just leave
well enough alone and drop it please. Seems your skin is thin as well if
you can't handle a little back talk :)
Well, I can always except critism. The problem is that I don't need rude
responses
2008/10/9 Jon Radel:
Dear Mr. Marshall:
I'm terribly sorry that our representatives in charge of answering emails
have been rude to you. I've just fired the lot of them, particularly as we
can't afford to keep then on anymore seeing as how your generous donations
are now in jeopardy.
How
On Thu, Oct 9, 2008 at 7:51 PM, Zbigniew Szalbot [EMAIL PROTECTED] wrote:
2008/10/9 Jon Radel:
Dear Mr. Marshall:
I'm terribly sorry that our representatives in charge of answering emails
have been rude to you. I've just fired the lot of them, particularly as we
can't afford to keep then
Hi,
2008/10/9 Odhiambo Washington [EMAIL PROTECTED]:
I love the direction this thread has taken. First, humorous, then it
will turn into flames. I bet all my US$:-)
Well, I do not have much to lose in terms of USD ;) but I cannot
really understand why some people are still sort of getting on
On Thu, Oct 9, 2008 at 1:03 PM, Zbigniew Szalbot [EMAIL PROTECTED] wrote:
Hi,
2008/10/9 Odhiambo Washington [EMAIL PROTECTED]:
I love the direction this thread has taken. First, humorous, then it
will turn into flames. I bet all my US$:-)
Well, I do not have much to lose in terms of USD
Chad Marshall wrote:
Here's what I said to the last guy who says my skin is thin, just
leave well enough alone and drop it please. Seems your skin is thin as
well if you can't handle a little back talk :)
Well, I can always except critism. The problem is that I don't need
rude responses for
On Thu, Oct 09, 2008 at 05:11:13PM +0200, Zbigniew Szalbot wrote:
But the discussion that followed made me realize that uptime is not
everything. I also love to see huge uptimes on my servers but if
anything this discussion brought it home to me that more than anything
I need to take care
Lowell Gilbert wrote:
[snip]
And in theory it should be possible to change time_t to unsigned, and
get another two-thirds of a century out of it...
However this would break binary compatibility with anything compiled
before the change.
--
GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6
and supportive and found some value in my story.
Best Regards,
Modulok wrote:
uptime 2 years!
Congratulations. Long uptimes should be shared, so as to encourage people to
consider FreeBSD for long-term stability. Thank you for posting.
Through this discussion the lazy administrator topic
uptime 2 years!
Congratulations. Long uptimes should be shared, so as to encourage people to
consider FreeBSD for long-term stability. Thank you for posting.
Through this discussion the lazy administrator topic came up... In
regards to that, we
must keep in mind, 'stability,' pertains not only
--- On Thu, 10/9/08, Eitan Adler [EMAIL PROTECTED] wrote:
From: Eitan Adler [EMAIL PROTECTED]
Subject: Re: uptime 2 years!
To: freebsd-questions@FreeBSD.org
Date: Thursday, October 9, 2008, 8:41 PM
Lowell Gilbert wrote:
[snip]
And in theory it should be possible to change time_t
--- On Thu, 10/9/08, Eitan Adler [EMAIL PROTECTED] wrote:
From: Eitan Adler [EMAIL PROTECTED]
Subject: Re: uptime 2 years!
To: freebsd-questions@FreeBSD.org
Date: Thursday, October 9, 2008, 8:41 PM
Lowell Gilbert wrote:
[snip]
And in theory it should be possible to change time_t
On Wed, Oct 08, 2008 at 06:00:38PM -0700, Chad Marshall wrote:
No Problem, I figured that there are other systems out there with a
longer uptime. I have this server as a postfix/courier-imap/
squirrelmail (60+ accounts and 30-40 forwards) mailserver with apache/
php/mysql. Also use
Hello,
Would like to share a success story which I'm sure you've had in the
past but one of my servers running FreeBSD will have an uptime of 2
years tomorrow. I plan on putting on my blog but as it doesn't have
much reach but wanted to share with you since your community has made
On Wed, Oct 08, 2008 at 08:54:47AM -0700, Chad Marshall wrote:
Would like to share a success story which I'm sure you've had in the
past but one of my servers running FreeBSD will have an uptime of 2
years tomorrow. I plan on putting on my blog but as it doesn't have much
reach but wanted
On Wednesday 08 October 2008, Jeremy Chadwick wrote:
On Wed, Oct 08, 2008 at 08:54:47AM -0700, Chad Marshall wrote:
Would like to share a success story which I'm sure you've had in the
past but one of my servers running FreeBSD will have an uptime of 2
years tomorrow. I plan on putting
On Wed 2008-10-08 09:21:53 UTC-0700, Jeremy Chadwick ([EMAIL PROTECTED]) wrote:
I don't want to rain on your parade, but uptime ultimately means squat.
Agreed.
I can install FreeBSD on a box under my desk at home, on a UPS, and
leave it powered on for the next 30 years -- it tells people
--On Wednesday, October 08, 2008 10:54:47 -0500 Chad Marshall
[EMAIL PROTECTED] wrote:
Hello,
Would like to share a success story which I'm sure you've had in the
past but one of my servers running FreeBSD will have an uptime of 2
years tomorrow. I plan on putting on my blog
andrew clarke wrote:
Is FreeBSD 7.1 2038-proof? ;-)
As far as I know the amd64 version is (anyone care to verify/correct?)
--
GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1
___
freebsd-questions@freebsd.org mailing list
On Wed, Oct 08, 2008 at 08:54:47AM -0700, Chad Marshall wrote:
Hello,
Would like to share a success story which I'm sure you've had in the
past but one of my servers running FreeBSD will have an uptime of 2
years tomorrow. I plan on putting on my blog but as it doesn't have
much
On Wed, 8 Oct 2008, Frank Shute wrote:
On Wed, Oct 08, 2008 at 08:54:47AM -0700, Chad Marshall wrote:
Hello,
Would like to share a success story which I'm sure you've had in the
past but one of my servers running FreeBSD will have an uptime of 2
years tomorrow. I plan on putting on my blog
FreeBSD will have an uptime of 2
| years tomorrow. I plan on putting on my blog but as it doesn't have
| much reach but wanted to share with you since your community has made
| this possible. Please indicate where I could post this to have a bit
| more reach or if you'd like to put a link to my
will have an uptime of 2
years tomorrow. I plan on putting on my blog but as it doesn't have
much reach but wanted to share with you since your community has made
this possible. Please indicate where I could post this to have a bit
more reach or if you'd like to put a link to my blog, I'd be more
Nice, but what does port audit say?
On Wed, Oct 8, 2008 at 8:54 AM, Chad Marshall [EMAIL PROTECTED] wrote:
Hello,
Would like to share a success story which I'm sure you've had in the past
but one of my servers running FreeBSD will have an uptime of 2 years
tomorrow. I plan on putting on my
No Problem, I figured that there are other systems out there with a
longer uptime. I have this server as a postfix/courier-imap/
squirrelmail (60+ accounts and 30-40 forwards) mailserver with apache/
php/mysql. Also use it as a slave authoritative nameserver for over
100 zones (one zone
why is this news or even important? heck most servers are up longer then
this.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Well sometimes you don't need to upgrade and you aren't connected to the
internet directly.
elephant: {25} uptime
5:54PM up 1756 days, 7:07, 2 users, load averages: 1.04, 1.01, 1.00
elephant 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003
This machine is semi-retired now
Well sometimes you don't need to upgrade and you aren't connected to
the
internet directly.
elephant: {25} uptime
5:54PM up 1756 days, 7:07, 2 users, load averages: 1.04, 1.01, 1.00
elephant 4.9-RELEASE FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT
2003
an
email when
the server is down and when is up again. With this information you can
know
the uptime
of the web server.
I'd have to install Nagios on a different server then, right? I doubt
the actual server knows when its ISP's link drops (or just slows down)
due to an attack
?
You can install nagios and monitor the web server. It will send you an
email when
the server is down and when is up again. With this information you can
know
the uptime
of the web server.
I'd have to install Nagios on a different server then, right? I doubt
the actual server knows
of the world)?
Maybe make some sort of ping script from a remote server?
You can install nagios and monitor the web server. It will send you
an
email when
the server is down and when is up again. With this information you can
know
the uptime
of the web server.
I'd have to install
Redd Vinylene wrote:
Hello hello!
I got this dedicated server which is exposed to DDoS attacks quite
frequently. Say I need to host a website on it, is there any way of
telling how often it is actually online (to the rest of the world)?
Maybe make some sort of ping script from a remote server?
/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
Hello,
You can install nagios and monitor the web server. It will send you an
email when
the server is down and when is up again. With this information you can know
the uptime
of the web server.
I'd
. With this information you can know
the uptime
of the web server.
I'd have to install Nagios on a different server then, right? I doubt
the actual server knows when its ISP's link drops (or just slows down)
due to an attack.
You can easily get nagios to test the web server sitting on the same
machine
. With this information you can know
the uptime
of the web server.
I'd have to install Nagios on a different server then, right? I doubt
the actual server knows when its ISP's link drops (or just slows down)
due to an attack.
You can easily get nagios to test the web server sitting on the same
machine
know
the uptime
of the web server.
I'd have to install Nagios on a different server then, right? I doubt
the actual server knows when its ISP's link drops (or just slows down)
due to an attack.
Not necessarily. You can install nagios on your web server and use it
to monitor a server
Hello hello!
I got this dedicated server which is exposed to DDoS attacks quite
frequently. Say I need to host a website on it, is there any way of
telling how often it is actually online (to the rest of the world)?
Maybe make some sort of ping script from a remote server?
--
?
Thx
- --On Friday, September 21, 2007 12:36:24 -0400 Bill Moran
[EMAIL PROTECTED] wrote:
In response to Byung-Hee HWANG [EMAIL PROTECTED]:
Hi there,
My machine is FreeBSD 6.x currently. But Netcraft do not display of my
machine's uptime graph. When I used FreeBSD 4.x, actually I could see
On Fri, 05 Oct 2007 16:19:53 -0300
Marc G. Fournier [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That URL states that we 'default to 1000Hz' ... is it lowerable, and
what are the ramifications of doing so? My first thought is that
1000Hz is giving us higher
Hi there,
My machine is FreeBSD 6.x currently. But Netcraft do not display of my
machine's uptime graph. When I used FreeBSD 4.x, actually I could see
the uptime graph in Netcraft.
What happened?
And what can I do to solve the problem?
Here is my machine's uname:
[EMAIL PROTECTED]:~ uname -v
1 - 100 of 186 matches
Mail list logo
