Topher wrote:
Nicholas Blatter wrote:
Why am I not surprised that Reiser killed your system? ;)
I think that's the funniest thing I've seen on this list in a very
long time. Thanks for the laugh.
I hope he's acquitted in this case.
--Dave
BYU Unix Users Group
On Thursday 24 January 2008 09:08:33 am Dave Smith wrote:
I hope he's acquitted in this case.
He may. There is no body to point to murder. However, I read several
articles about the case and he seems to be kind of an odd fellow. I
guess genius has its price.
--
Alberto Treviño
[EMAIL
On Jan 24, 2008 9:56 AM, Alberto Treviño [EMAIL PROTECTED] wrote:
On Thursday 24 January 2008 09:08:33 am Dave Smith wrote:
I hope he's acquitted in this case.
He may. There is no body to point to murder. However, I read several
articles about the case and he seems to be kind of an odd
Alberto Treviño wrote:
On Thursday 24 January 2008 09:08:33 am Dave Smith wrote:
I hope he's acquitted in this case.
He may. There is no body to point to murder. However, I read several
articles about the case and he seems to be kind of an odd fellow. I
guess genius has its
On Thursday 24 January 2008 10:18:35 am Dave Smith wrote:
I was talking about the file system issue that killed the OP's
uptime. ;)
Well, the system is in a RAID 1 configuration. The screen was scrolling
error messages, all starting with reiserfs: . . . The ones I could
read stated
Who knows. Maybe the Uptime Gods have a sense of humor and they cause
mischief on systems so that they never reach 1,000 days of uptime. No
matter what the problem was, my 1,000 days of uptime were never
achieved, 993 was close enough, and that's by far the longest uptime I
have ever
Jan L. Peterson wrote:
Who knows. Maybe the Uptime Gods have a sense of humor and they cause
mischief on systems so that they never reach 1,000 days of uptime. No
matter what the problem was, my 1,000 days of uptime were never
achieved, 993 was close enough, and that's by far the longest
On Thursday 24 January 2008 02:00:47 pm Jan L. Peterson wrote:
There used to be a thing called the uptime project
(http://en.wikipedia.org/wiki/Uptime) that relied on people running
uptime reporting clients on their systems.
Well, the only problem with running tests of this kind is that they
Alberto Treviño wrote:
On Thursday 24 January 2008 02:00:47 pm Jan L. Peterson wrote:
There used to be a thing called the uptime project
(http://en.wikipedia.org/wiki/Uptime) that relied on people running
uptime reporting clients on their systems.
Well, the only problem with
Nicholas Blatter wrote:
Why am I not surprised that Reiser killed your system? ;)
I think that's the funniest thing I've seen on this list in a very long
time. Thanks for the laugh.
--
Topher Fischer
GnuPG Fingerprint: 3597 1B8D C7A5 C5AF 2E19 EFF5 2FC3 BE99 D123 6674
[EMAIL PROTECTED]
My Linux box that had been up for a long time had to be reset. The
machine was started on May 3, 2005 at 8:58am and stayed up until today,
January 22 right at the stroke of midnight. That puts the uptime to
993 days, 15 hours, or 2 years, 8 months, 18 days, and 15 hours.
So what killed it?
On Tue, 2008-01-22 at 10:34 -0700, Alberto Treviño wrote:
So what killed it? A cron job started at midnight that triggered a
bug in ReiserFS, stopping all operations to the filesystem.
Tell us more about the time-bomb nature of this bug.
Gabe
BYU Unix Users Group
On Tuesday 22 January 2008 11:20:45 am Gabriel Gunderson wrote:
On Tue, 2008-01-22 at 10:34 -0700, Alberto Treviño wrote:
So what killed it? A cron job started at midnight that triggered a
bug in ReiserFS, stopping all operations to the filesystem.
Tell us more about the time-bomb nature
I don't know exactly which bug hit me. The kernel that is running on
that machine is 2.6.11, obviously very old. I know that up to version
Is there problems in running an kernel that is that out of date?
Security concerns?
--
~ Mark
Gardner ~
***
LEADERSHIP is a flavor of evil.
On Tue, 2008-01-22 at 16:23 -0600, Mark Gardner wrote:
Is there problems in running an kernel that is that out of date?
Security concerns?
Definitely. Just because Linux can run that long doesn't mean it should
run that long. If you plan on staying up for months at a time, you
should isolate
Why am I not surprised that Reiser killed your system? ;)
On 1/22/08, Alberto Treviño [EMAIL PROTECTED] wrote:
So what killed it? A cron job started at midnight that triggered a bug
in ReiserFS, stopping all operations to the filesystem.
BYU Unix Users Group
On Tuesday 22 January 2008 03:39:57 pm Stuart Jansen wrote:
Definitely. Just because Linux can run that long doesn't mean it
should run that long. If you plan on staying up for months at a time,
you should isolate the system and/or pay careful attention to
security announcements. Thankfully,
17 matches
Mail list logo
