![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Darren New
Subject: Re: Is this the end of the world as we know it?
Date: 26 Oct 2011 16:43:49
Message: <4ea87105@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 10/25/2011 9:23, Jim Henderson wrote:
> It's been my experience that in far more cases with Windows admins than
> with those of other systems, "reboot the system" becomes the "fix" rather
> than trying to troubleshoot it.
Well, yes. I'll grant you that.
> Once upon a time, I worked for a Fortune 50 company with several thousand
> Windows servers. Informix was running on them, and there was a memory
> leak. "Reboot the system" was the "fix", to the extent that the reboot
> was scripted and scheduled to run nightly.
Same with Linux set-top boxes I was working on. Because we didn't have the
source to the code that was leaking the memory.
And indeed, I was working on one Linux server system where they were
catching sigsegv's and outputting "caught a signal!" to stdout, but then not
actually recovering. So I had to pipe the output into a second process *I*
wrote that would grep for that string and send a kill -9 and restart it when
it got stuck.
It's not Windows per se, but proprietary software that you can't fix.
> Now, part of the reason for that was that Informix was taking their time
> fixing the problem
There ya go. :-)
--
Darren New, San Diego CA, USA (PST)
People tell me I am the counter-example.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Jim Henderson
Subject: Re: Is this the end of the world as we know it?
Date: 26 Oct 2011 19:16:28
Message: <4ea894cc@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Wed, 26 Oct 2011 13:43:47 -0700, Darren New wrote:
>> Once upon a time, I worked for a Fortune 50 company with several
>> thousand Windows servers. Informix was running on them, and there was
>> a memory leak. "Reboot the system" was the "fix", to the extent that
>> the reboot was scripted and scheduled to run nightly.
>
> Same with Linux set-top boxes I was working on. Because we didn't have
> the source to the code that was leaking the memory.
>
> And indeed, I was working on one Linux server system where they were
> catching sigsegv's and outputting "caught a signal!" to stdout, but then
> not actually recovering. So I had to pipe the output into a second
> process *I* wrote that would grep for that string and send a kill -9 and
> restart it when it got stuck.
>
> It's not Windows per se, but proprietary software that you can't fix.
Exactly. :)
>> Now, part of the reason for that was that Informix was taking their
>> time fixing the problem
>
> There ya go. :-)
Yep.
Jim
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 26/10/2011 09:43 PM, Darren New wrote:
> On 10/25/2011 9:23, Jim Henderson wrote:
>> It's been my experience that in far more cases with Windows admins than
>> with those of other systems, "reboot the system" becomes the "fix" rather
>> than trying to troubleshoot it.
>
> Well, yes. I'll grant you that.
>
>> Once upon a time, I worked for a Fortune 50 company with several thousand
>> Windows servers. Informix was running on them, and there was a memory
>> leak. "Reboot the system" was the "fix", to the extent that the reboot
>> was scripted and scheduled to run nightly.
>
> Same with Linux set-top boxes I was working on. Because we didn't have
> the source to the code that was leaking the memory.
> It's not Windows per se, but proprietary software that you can't fix.
One of our production systems is a crappy little thing written in VB.
Roughly once a week somebody over in the USA files a helpdesk ticket
saying "please reboot it". Apparently it leaks memory until it stops
working. Reboot the server and it works again.
(What I can't figure out is why just restarting the program itself
wouldn't fix that...)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 10/27/2011 1:13, Invisible wrote:
> (What I can't figure out is why just restarting the program itself wouldn't
> fix that...)
It probably would, unless it's a service that's leaking memory, in which
case restarting the service *should* work.
--
Darren New, San Diego CA, USA (PST)
People tell me I am the counter-example.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Orchid XP v8
Subject: Re: Is this the end of the world as we know it?
Date: 27 Oct 2011 16:20:18
Message: <4ea9bd02$1@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 27/10/2011 05:15 PM, Darren New wrote:
> On 10/27/2011 1:13, Invisible wrote:
>> (What I can't figure out is why just restarting the program itself
>> wouldn't
>> fix that...)
>
> It probably would, unless it's a service that's leaking memory, in which
> case restarting the service *should* work.
As best as I know, it's a user GUI application. I'm not sure why the
hell just logging out and logging back in again doesn't fix it, but
anyway...
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |