Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.albasani.net!news.stack.nl!newsfeed.xs4all.nl!newsfeed4a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.052 X-Spam-Evidence: '*H*': 0.90; '*S*': 0.00; 'blue': 0.09; 'counting': 0.09; 'cc:addr:python-list': 0.11; '>down': 0.16; '>on': 0.16; 'buggy': 0.16; 'hardware.': 0.16; 'included,': 0.16; 'simpson': 0.16; 'subject:Thread': 0.16; 'wrote:': 0.18; 'year,': 0.18; 'bit': 0.19; '>>>': 0.22; 'email addr:gmail.com>': 0.22; 'cc:addr:python.org': 0.22; 'header:User-Agent:1': 0.23; 'cc:2**0': 0.24; 'cc:no real name:2**0': 0.24; 'equivalent': 0.26; 'nearly': 0.26; 'asking': 0.27; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; 'quickly': 0.29; 'unix': 0.29; "doesn't": 0.30; 'url:mailman': 0.30; 'that.': 0.31; "d'aprano": 0.31; 'long.': 0.31; 'sep': 0.31; 'steven': 0.31; 'probably': 0.32; 'linux': 0.33; 'url:python': 0.33; 'fri,': 0.33; 'not.': 0.33; 'but': 0.35; 'received:google.com': 0.35; 'much.': 0.36; 'url:listinfo': 0.36; 'subject:?': 0.36; 'url:org': 0.36; 'two': 0.37; 'pm,': 0.38; 'anything': 0.39; 'does': 0.39; '12,': 0.39; 'url:mail': 0.40; 'how': 0.40; 'even': 0.60; 'skip:u 10': 0.60; 'most': 0.60; 'hardware': 0.61; 'matter': 0.61; 'different': 0.65; 'to:addr:gmail.com': 0.65; 'incoming': 0.72; 'power': 0.76; '2014,': 0.84; 'gone.': 0.84; 'uptime': 0.84; 'subject:much': 0.91 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=in-reply-to:references:user-agent:mime-version:content-type :content-transfer-encoding:subject:from:date:to:cc:message-id; bh=BOkQPFE/IeByn6/J7gs9jfxjlw5BCu+cRYeoFJCPs2I=; b=HbdqRUXA8iBYwudtO6nI5G7umixgarjVXxxI194T0SLXvl24pdVVUcqdbtiMGd8XHp zZM8W9ODS4C28mMdW2vEUSgul0atJJPqtVscDaMfL8sso8J8hijYNfyzpkyY/JeqkuN1 H7QF256bjX4+pmkeHldn6T3z9nLOK6C1bjSwSfWytHQNwaoyKGIv7IXti/k4sTogjhgw 6/0SypsMtLG/tE/RNk5m4wxexIrLO8MxNM9WDD6aLOiHydwhl3CznOnRKzBtJZxf+NrF Fdj0nioO3aAQkJkGCNXVQy8t4hoX5WCQUNz7yAqJCSXG0SFC1ohCKIc3PU534smJOAk/ RoFg== X-Received: by 10.152.87.146 with SMTP id ay18mr134141lab.92.1410602974945; Sat, 13 Sep 2014 03:09:34 -0700 (PDT) In-Reply-To: References: <54124c95$0$29991$c3e8da3$5496439d@news.astraweb.com> <20140912034100.GA14188@cskk.homeip.net> User-Agent: Blue for Android MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----3YYFXS4Q9P4RY08HYWET1DU7Q64I7O" Content-Transfer-Encoding: 8bit Subject: Re: Thread-ID - how much could be? From: =?ISO-8859-1?Q?Martin_Skj=F6ldebrand?= Date: Sat, 13 Sep 2014 12:09:28 +0200 To: Chris Angelico Cc: python-list@python.org X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 62 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1410602977 news.xs4all.nl 2848 [2001:888:2000:d::a6]:44410 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:77843 ------3YYFXS4Q9P4RY08HYWET1DU7Q64I7O Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Unfortunately we will never know 😢 Sent from Blue Mail On 12 Sep 2014 07:43, at 07:43, Chris Angelico wrote: >On Fri, Sep 12, 2014 at 1:41 PM, Cameron Simpson wrote: >> On 12Sep2014 11:29, Steven D'Aprano > >> wrote: >>> >>> [...]maxint. I know that some Linux >>> systems can have an uptime over a year, perhaps even two years, but >I >>> think >>> that nearly 300 years is asking a bit much. >> >> >> 2 years is nothing. Unless they have a particularly buggy kernel, >most UNIX >> systems, Linux included, will stay up almost indefinitely. We've >definitely >> had systems up for well over 2 years. >> >>> Your hardware probably won't >>> keep working that long. >> >> >> 300 years? Probably not. Regrettably. > >Once you get into the counting of years (rather than days), it's all >down to hardware. How long before that hardware needs an upgrade? Does >your incoming power have fail-overs? I don't currently have any >servers with multiple power supplies, so if anything like that goes >bung, my server's down. Doesn't matter how quickly I can bring up an >equivalent on a different hunk of hardware, the uptime's gone. > >But yeah. 300 years? Good luck. I don't think anyone's ever going to >hit that. > >ChrisA >-- >https://mail.python.org/mailman/listinfo/python-list ------3YYFXS4Q9P4RY08HYWET1DU7Q64I7O Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Unfortunately we will never know 😢

Sent from Blue Mail

On 12 Sep 2014, at 07:43, Chris Angelico <rosuav@gmail.com> wrote:
On Fri, Sep 12, 2014 at 1:41 PM, Cameron Simpson 
 On 12Sep2014 11:29, Steven D'Aprano  wrote:

 [...]maxint. I know that some Linux
 systems can have an uptime over a year, perhaps even two years, but I
 think
 that nearly 300 years is asking a bit much.


 2 years is nothing. Unless they have a particularly buggy kernel, most UNIX
 systems, Linux included, will stay up almost indefinitely. We've definitely
 had systems up for well over 2 years.

 Your hardware probably won't
 keep working
that long.


 300 years? Probably not. Regrettably.

Once you get into the counting of years (rather than days), it's all
down to hardware. How long before that hardware needs an upgrade? Does
your incoming power have fail-overs? I don't currently have any
servers with multiple power supplies, so if anything like that goes
bung, my server's down. Doesn't matter how quickly I can bring up an
equivalent on a different hunk of hardware, the uptime's gone.

But yeah. 300 years? Good luck. I don't think anyone's ever going to hit that.

ChrisA
------3YYFXS4Q9P4RY08HYWET1DU7Q64I7O--