[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Jan 30 17:00:05 2000 
Subject:Re: pglink crash/core dump of Redhat Linux 6.1? Help! 
From:Aaron Sloman See text for reply address 
Volume-ID:1000130.01 

[To reply replace "Aaron.Sloman.XX" with "A.Sloman"]

Apologies for delay. I was hoping to check this out sooner, but have
been very busy.

Rod Chapman Praxis Critical Systems <rod@praxis-cs.co.uk> writes:

> Date: Wed, 19 Jan 2000 09:53:21 +0000
>
> Can anyone help me out with this problem...
>
> I need to re-build PopLog (v15.53) on my Linux
> system (RedHat 6.1, 128 Meg RAM, 256 Meg swap)

I previously had no problems running pglink with the same version of
poplog on a redhat 6.0 sysytem.

It produces a newpop11 almost immediately on a fairly new PC 600mhz.

But like you I find it doesn't work on 6.1. I checked this out using
V15.53 on a Dell laptop running redhat 6.1. Apart from pglink all
of poplog seems to work fine.

> The first time I ran "pglink" nothing happened - I realised
> this was due to an rlimit

I tried pglink without recompiling anything first and it produced
only a core file.

> ..- I did an "unlimit all" and
> tried again.
> It now runs, but the "poplink" process
> grows to 1.3Gig and then dumps a 1.3Gig core file.

I tried unlimit all and pglink, but after it had run for a while without
stopping I killed the process, and found a 275Mbyte core file.

> What's up?  Do I need more RAM and/or swap?
>   Cheers,

More likely something has changed in redhat 6.1 which requires some
change in the pglink process.

Perhaps something needs to be recompiled first.

Does anyone with more knowledge of linux, and what might have changed
between redhat 6.0 and redhat 6.1 have any suggestions?

Aaron
===
-- 
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
School of Computer Science, The University of Birmingham, B15 2TT, UK
EMAIL A.Sloman AT cs.bham.ac.uk   (NB: Anti Spam address)
TOOLS: http://www.cs.bham.ac.uk/research/poplog/freepoplog.html