Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Oct 1997 13:42:39 +0000 (GMT)
From:      Aled Treharne <taff@blue.bad.bris.ac.uk>
To:        Doug White <dwhite@resnet.uoregon.edu>
Cc:        "Randy A. Katz" <randyk@ccsales.com>, questions@FreeBSD.ORG
Subject:   Re: HELP - Has anyone seen this?
Message-ID:  <Pine.BSF.3.96.971029133740.1568A-100000@blue.bad.bris.ac.uk>
In-Reply-To: <Pine.BSF.3.96.971028135923.15098C-100000@gdi.uoregon.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----

On Tue, 28 Oct 1997, Doug White wrote:
> On Tue, 28 Oct 1997, Aled Treharne wrote:
> > > > inetd in realloc(): warning: junk pointer, too low to make sense.
> > > > ftp>
> > > It's harmless.  If it bugs you, have inetd's log output placed in a
> > > different file.  See syslog.conf.
> > Hmmm. Harmless? One thing this does is to stop ftp logins and su's to
> > root. Having run 2.2.2 for several months I decided to change to 2.2.5
> > yesterday. I had the junk pointer error a few times in 2.2.2 but they
> > stopped. Now it's restarted again. Any idea what actually causes it and
> > is there an easy way or even a hard way of getting rid of it?

> It shouldn't stop su to root since it's long after inetd gets through.  It
> shouldn't do anything to ftp either, unless it never gets started.  What
> error messages are you seeing?

When I log in I get 
inetd in realloc(): warning: junk pointer, too low to make sense
and then the login carries on as normal. FTP logins get the same error
after logging in but the connection is immediately closed again. When I
tried to su I got something like
Cannot malloc()
or something like that - I'm not sure since I have no longer been able to
reproduce the error. In fact the whole problem seem to be very strange
since it comes and goes. We also had another problem today with the
server running out of swap space. Very strange since only 2 users were
logged in one was idle (only process was shell) and the other was using
pine. Pine decided to hog all the memory and the server went ape.

I'm totally at a loss as to what could possibly cause this. Is this a
problem with 2.2.5?

- -Taff.


	  	   Aled Treharne		felix@royal.net
"Big Bird meets Salvador Dali has been brought to you by the numbers L and
                            ), and by the letter 3."
         For PGP Public key finger taff@blue.bad.bris.ac.uk

#include(std.disclaim)


-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQCVAwUBNFc9VMaJukNO1flNAQHsswQAmXle4cz3kZlaxVgSlbYl9XiSa/2b24NT
hog2WScxnEsBSr42K3VbXEt9ObjmRDwZWV9mLMXDYqOl1nnTdACdu8m3gS1jSHBw
IZwyVMdHEfeA9vWIT902so5LtkqZHW6M1nuCqI8PNauAd6hIYsHV6cdsrIpf3V3k
Mmf/Curcn5g=
=GFh4
-----END PGP SIGNATURE-----




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971029133740.1568A-100000>