On Sun, Aug 11, 2019 at 08:52:59PM -0400, Fred Smith
(fre...@fcshome.stoneham.ma.us) wrote:
> On Mon, Aug 12, 2019 at 10:16:35AM +1000, Jobst Schmalenbach wrote:
> > On Mon, Aug 05, 2019 at 08:57:45PM -0400, Fred Smith
> > (fre...@fcshome.stoneham.ma.us) wrote:
> > > Hi all!
> >
> > Late to the
On Mon, Aug 12, 2019 at 10:16:35AM +1000, Jobst Schmalenbach wrote:
> On Mon, Aug 05, 2019 at 08:57:45PM -0400, Fred Smith
> (fre...@fcshome.stoneham.ma.us) wrote:
> > Hi all!
> >
> > I'm stuck on something really bizarre that is happening to a product
> > I "own" at work. It's a C program,
On Mon, Aug 05, 2019 at 08:57:45PM -0400, Fred Smith
(fre...@fcshome.stoneham.ma.us) wrote:
> Hi all!
>
> I'm stuck on something really bizarre that is happening to a product
> I "own" at work. It's a C program, built on CentOS, runs on CentOs or
> RHEL, has been in circulation since the early
Smith
Sent: August 8, 2019 7:48 PM
To: centos@centos.org
Subject: Re: [CentOS] another bizarre thing...
On Thu, Aug 08, 2019 at 05:06:06PM +, Young, Gregory wrote:
> Is this on both EL6 and EL7? If only EL7, it could be control groups causing
> the issue. The idea of cgroups is t
it thinks the program
is killing itself, but as the guy who wrote it, I don't think so.
the script can be seen below in earlier mail.
As for if it also fails on C6, I don't know. I've asked our support
team to see if they have a C6/EL6 customer who will let them install
the latest version for 6 and
own.
Gregory Young
-Original Message-
From: CentOS On Behalf Of Fred Smith
Sent: August 7, 2019 1:39 PM
To: centos@centos.org
Subject: Re: [CentOS] another bizarre thing...
On Mon, Aug 05, 2019 at 08:57:45PM -0400, Fred Smith wrote:
> Hi all!
>
> I'm stuck on something rea
On Wed, 7 Aug 2019 13:38:54 -0400
Fred Smith wrote:
> So,... now I'm wondering how one figures that out.
Since it's your program you have the source code.
printf is your friend.
Start adding printf statements (to console and/or to a file at your option)
with status reports ("widget counting
On Mon, Aug 05, 2019 at 08:57:45PM -0400, Fred Smith wrote:
> Hi all!
>
> I'm stuck on something really bizarre that is happening to a product
> I "own" at work. It's a C program, built on CentOS, runs on CentOs or
> RHEL, has been in circulation since the early 00's, is in use at
> hundreds of
On Tue, Aug 06, 2019 at 09:02:37PM -0600, Warren Young wrote:
> On Aug 6, 2019, at 8:48 PM, Fred Smith wrote:
> >
> > Setting up as you described earlier, is there a way to allow only
> > a single program to drop core?
>
> Of course.
>
> The * in the limits.d file is a “domain” value you can
On Aug 6, 2019, at 8:48 PM, Fred Smith wrote:
>
> Setting up as you described earlier, is there a way to allow only
> a single program to drop core?
Of course.
The * in the limits.d file is a “domain” value you can adjust to suit:
On Tue, Aug 06, 2019 at 03:18:06PM -0600, Warren Young wrote:
> On Aug 6, 2019, at 7:59 AM, Fred Smith wrote:
> >
> > On Tue, Aug 06, 2019 at 05:27:54AM -0600, Warren Young wrote:
> >> On Aug 5, 2019, at 6:57 PM, Fred Smith
> >> wrote:
> >>>
> >>> no core file (yes, ulimit is configured)
> >
On Aug 6, 2019, at 7:59 AM, Fred Smith wrote:
>
> On Tue, Aug 06, 2019 at 05:27:54AM -0600, Warren Young wrote:
>> On Aug 5, 2019, at 6:57 PM, Fred Smith wrote:
>>>
>>> no core file (yes, ulimit is configured)
>
> yeah, I meant "ulimit -c unlimited" is in effect.
That only affects the shell
On Tue, Aug 06, 2019 at 03:49:29PM +, James Pearson wrote:
> Fred Smith wrote:
> >
> > Hi all!
> >
> > I'm stuck on something really bizarre that is happening to a product
> > I "own" at work. It's a C program, built on CentOS, runs on CentOs or
> > RHEL, has been in circulation since the
Fred Smith wrote:
>
> Hi all!
>
> I'm stuck on something really bizarre that is happening to a product
> I "own" at work. It's a C program, built on CentOS, runs on CentOs or
> RHEL, has been in circulation since the early 00's, is in use at
> hundreds of sites.
>
> recently, at multiple
On Tue, Aug 06, 2019 at 05:27:54AM -0600, Warren Young wrote:
> On Aug 5, 2019, at 6:57 PM, Fred Smith wrote:
> >
> > no core file (yes, ulimit is configured)
yeah, I meant "ulimit -c unlimited" is in effect.
I had no idea systemd had made such a drastic change. or is it that
someone at RH
Wow, thanks for the detailed recipe!
How did we deserve this when it was so easy in the past :-)
> On Aug 5, 2019, at 6:57 PM, Fred Smith
> wrote:
>>
>> no core file (yes, ulimit is configured)
>
> That’s nowhere near sufficient. To restore classic core file dumps on
> CentOS 7, you must:
>
>
On Aug 6, 2019, at 5:35 AM, Pete Biggs wrote:
>
> On Tue, 2019-08-06 at 05:27 -0600, Warren Young wrote:
>> On Aug 5, 2019, at 6:57 PM, Fred Smith wrote:
>>> no core file (yes, ulimit is configured)
>>
>> That’s nowhere near sufficient. To restore classic core file dumps
>> on CentOS 7, you
On Tue, 2019-08-06 at 05:27 -0600, Warren Young wrote:
> On Aug 5, 2019, at 6:57 PM, Fred Smith wrote:
> > no core file (yes, ulimit is configured)
>
> That’s nowhere near sufficient. To restore classic core file dumps
> on CentOS 7, you must:
>
I was under the impression that a SIGKILL
On Aug 5, 2019, at 6:57 PM, Fred Smith wrote:
>
> no core file (yes, ulimit is configured)
That’s nowhere near sufficient. To restore classic core file dumps on CentOS
7, you must:
1. Remove Red Hat’s ABRT system, which wants to catch all of this and handle it
directly. Say something like
of a memory
shortage.
From: CentOS on behalf of Fred Smith
Sent: Tuesday, 6 August 2019 10:57 AM
To: centos@centos.org
Subject: [CentOS] another bizarre thing...
Hi all!
I'm stuck on something really bizarre that is happening to a product
I "own&q
uns and there's no evidence of a memory
shortage.
>
> From: CentOS on behalf of Fred Smith
>
> Sent: Tuesday, 6 August 2019 10:57 AM
> To: centos@centos.org
> Subject: [CentOS] another bizarre thing...
>
> Hi all!
>
> I'm stuck
To: centos@centos.org
Subject: [CentOS] another bizarre thing...
Hi all!
I'm stuck on something really bizarre that is happening to a product
I "own" at work. It's a C program, built on CentOS, runs on CentOs or
RHEL, has been in circulation since the early 00's, is in use at
hundred
Hi all!
I'm stuck on something really bizarre that is happening to a product
I "own" at work. It's a C program, built on CentOS, runs on CentOs or
RHEL, has been in circulation since the early 00's, is in use at
hundreds of sites.
recently, at multiple customer sites it has started just going
23 matches
Mail list logo
