Tyler MacDonald wrote:
> I moved the server because wedohosting.com's bandwidth fees were
> getting prohibitive (i'm with iweb.ca now).. otherwise I would have been
> happy to have it continue running for another few thousand days. :-)
I find that Tera-Byte.com in Edmonton has nice colo rate
On Thu, Jun 08, 2006 at 05:57:22PM -0700, Tyler MacDonald wrote:
> This is the most sensible answer I've heard about this (and I've
> bitched about the limitation a lot). Maybe it's time for me to delve into
> the kernel source for the first time in 10 years.
I gather this was "fixed" in Linux 2.5
Anthony Towns wrote:
> No it wouldn't; it'd just require you to have two extra ints, and something
> that
> ran every so often (and as part of any syscall that tells userspace the
> uptime),
> that does:
>
> static unsigned last_uptime = 0;
> static unsigned wraps = 0;
> if (u
On Thu, Jun 08, 2006 at 10:39:48PM +0300, Lars Wirzenius wrote:
> Fixing this would require having every increment of the jiffies counter
> to check for overflow, and using two counters. This is unnecessary
> overhead (a very small overhead, granted, but still), for a very small
> benefit.
No it w
Tyler MacDonald wrote:
> I moved the server because wedohosting.com's bandwidth fees were
> getting prohibitive (i'm with iweb.ca now).. otherwise I would have been
> happy to have it continue running for another few thousand days. :-)
>
I don't suppose you could have moved it while still r
Steinar H. Gunderson <[EMAIL PROTECTED]> wrote:
> > It was finally retired today, after 875 days of uptime, not because there
> > was a problem with it, just because there was a price problem with the
> > hosting provider it's colocated at. For an "unstable" distribution, it gave
> > me the most st
On Thu, Jun 08, 2006 at 11:29:21AM -0700, Tyler MacDonald wrote:
> It was finally retired today, after 875 days of uptime, not because there
> was a problem with it, just because there was a price problem with the
> hosting provider it's colocated at. For an "unstable" distribution, it gave
> me th
Ron Johnson <[EMAIL PROTECTED]> wrote:
> > That production server has been running debian/unstable since it's inception
> > in january of 2004, with dselect updates happening every couple of days. It
> > was running apache, postfix, mysql, mydns. Despite being "unstable", there
> > was never a prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tyler MacDonald wrote:
> http://www.crackerjack.net/adserton3.png
>
> That production server has been running debian/unstable since it's inception
> in january of 2004, with dselect updates happening every couple of days. It
> was running apache, post
Sebastian Harl, 2006-06-08 21:10:11 +0200 :
>> http://www.crackerjack.net/adserton3.png
>
> On that picture it says the box is up for 378 days. How does that go
> with 875 days idle time?
Old Linux kernels have their uptime roll over at about 497 days
(which is like 2^32 ticks of a hundredth of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Harl wrote:
>> http://www.crackerjack.net/adserton3.png
>
> On that picture it says the box is up for 378 days. How does that go with 875
> days idle time?
zoom in
- --
e-mail: Miguel Gea Milvaques <[EMAIL PROTECTED]>
Blog: http://www.
On Thu, Jun 08, 2006 at 12:20:03PM -0700, Tyler MacDonald wrote:
> Due to a bug with "w", or the kernel, or whatever, which nobody seems to
> want to fix, the system uptime wraps around to 0 days after 400-and-someodd
> days. That's why I circled the login/idle time on the screenshot. :-)
The jiff
to, 2006-06-08 kello 12:20 -0700, Tyler MacDonald kirjoitti:
> Sebastian Harl <[EMAIL PROTECTED]> wrote:
> > > http://www.crackerjack.net/adserton3.png
> >
> > On that picture it says the box is up for 378 days. How does that go with
> > 875 days idle time?
> >
>
> Due to a bug with "w", or the
Sebastian Harl <[EMAIL PROTECTED]> wrote:
> > http://www.crackerjack.net/adserton3.png
>
> On that picture it says the box is up for 378 days. How does that go with
> 875 days idle time?
>
Due to a bug with "w", or the kernel, or whatever, which nobody seems to
want to fix, the system uptime wra
> http://www.crackerjack.net/adserton3.png
On that picture it says the box is up for 378 days. How does that go with 875
days idle time?
Cheers,
Sebastian
--
Sebastian "tokkee" Harl
GnuPG-ID: 0x8501C7FC
http://tokkee.org/
signature.asc
Description: Digital signature
http://www.crackerjack.net/adserton3.png
That production server has been running debian/unstable since it's inception
in january of 2004, with dselect updates happening every couple of days. It
was running apache, postfix, mysql, mydns. Despite being "unstable", there
was never a problem that resu
16 matches
Mail list logo
