From nobody  Thu Jun  4 10:18:42 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA17894;
          Thu, 4 Jun 1998 10:18:42 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199806041718.KAA17894@hub.freebsd.org>
Date: Thu, 4 Jun 1998 10:18:42 -0700 (PDT)
From: jher@io.com
To: freebsd-gnats-submit@freebsd.org
Subject: inetd in realloc(): warning: junk pointer, too low to make sense.
X-Send-Pr-Version: www-1.0

>Number:         6858
>Category:       kern
>Synopsis:       inetd in realloc(): warning: junk pointer, too low to make sense.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jun  4 10:20:01 PDT 1998
>Closed-Date:    Tue Dec 28 00:47:57 PST 1999
>Last-Modified:  Tue Dec 28 00:49:02 PST 1999
>Originator:     jher
>Release:        3.0-980518-SNAP
>Organization:
Illuminati Online
>Environment:
FreeBSD solomon.io.com 3.0-980518-SNAP FreeBSD 3.0-980518-SNAP #0: Tue Jun  2 19:22:49 CDT 1998     jher@solomon.io.com:/usr/src/sys/compile/SOLOMON  i386

>Description:
I boot the machine, run my innd server o it and after its 12am expire
run, the machine starts screwing up.  The expire run is very memory
intensive and usually eats about 200megs of ram.  As soon as it starts,
sshd can no longer malloc correctly and tries to malloc 1+gig of memory
whenever I ssh into the machine.  I therefore resort to telnetting in and
get the message:
inetd in realloc(): warning: junk pointer, too low to make sense.
but it lets me login.  From that point forward, the cronjobs cease to
run correctly.  Basically they startup and exit immediately.  If I send
a HUP to sshd's pid, it returns to normal and I can ssh in.  Of course,
since cron no longer functions correctly, news is failing to get expired
etc.  If I reboot, it usually corrects the problem until the cronjob
for news runs at midnight.
I'm on a P-II 266Mhz, with 256M SDram, 2940UW scsi (2 controllers), SMC
10/100 Etherpower, and an LX-6 Motherboard.

I'm running an SMP version of the same release on a Dual PPro 200Mhz
machine with DPT and 2904UW, and SMC 10/100 without having the same
problem.  The kernel has esentially the same compile options.  This
machine is also running innd and its nightly news.daily (expire) run
has a larger amount of data to work with and so far its been flawless.
Oh and the Mainboard is an ASUS board.
>How-To-Repeat:
wait for the news.daily run to happen from the 12am crontab
>Fix:
reboot
>Release-Note:
>Audit-Trail:

From: jher <jher@io.com>
To: FreeBSD-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org
Cc:  Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Thu, 4 Jun 1998 16:00:14 -0500

 Updates: 
 	I upgraded to 3.0-980523-SNAP. No change.  
 	Dowgraded to 3.0-980504-SNAP.  No change.
 	Recompiled the kernel with "NMBCLUSTERS=4096" as per
 	http://x7.dejanews.com/getdoc.xp?AN=349752605&CONTEXT=896993782.176226375&hitnum=24
 	No effect.
 	What I have found out is this.  When expire runs it grows to around 
 230M in size.  Testing with ssh and telnet, both begin to fail when 62M of
 Swap is allocated in top.  ssh reports the following debug message:
 
 Jun  4 15:58:54 solomon sshd[166]: debug: Forked child 1004.
 Jun  4 15:58:54 solomon sshd[1004]: log: Connection from 199.170.88.23 port 797
 Jun  4 15:58:55 solomon sshd[1004]: debug: Client protocol version 1.5; client software version 1.2.22
 Jun  4 15:58:55 solomon sshd[1004]: fatal: xmalloc: out of memory (allocating 1073690875 bytes)
 Jun  4 15:58:55 solomon sshd[1004]: debug: Calling cleanup 0xf8dc(0x0)
 
 and of course fails to let me login.  Currently I have an associate recompiling
 inetd with debug so we can track it also.   I'll followup with the results 
 after we get more data.
 
 -- 
 jher@io.com	Senior Systems Engineer 	jher@fnord.org	Pope
                          http://www.fnord.org
 
 Today is Setting Orange, day 9 in the season of Confusion, 3164.

From: Greg Lehey <grog@lemis.com>
To: jher@io.com, freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Fri, 5 Jun 1998 09:46:57 +0930

 This symptom seems much more common than this message would suggest.
 I've seen it in cases where the system has run out of swap, but that
 doesn't seem to be a requirement.  The "fix" is rather heavy-handed.
 I've always been able to restart inetd and keep it quiet for some
 time.
 
 Greg
 
 On Thu,  4 June 1998 at 10:18:42 -0700, jher@io.com wrote:
 >
 >> Number:         6858
 >> Category:       kern
 >> Synopsis:       inetd in realloc(): warning: junk pointer, too low to make sense.
 >> Confidential:   no
 >> Severity:       serious
 >> Priority:       high
 >> Responsible:    freebsd-bugs
 >> State:          open
 >> Quarter:
 >> Keywords:
 >> Date-Required:
 >> Class:          sw-bug
 >> Submitter-Id:   current-users
 >> Arrival-Date:   Thu Jun  4 10:20:01 PDT 1998
 >> Last-Modified:
 >> Originator:     jher
 >> Organization:
 > Illuminati Online
 >> Release:        3.0-980518-SNAP
 >> Environment:
 > FreeBSD solomon.io.com 3.0-980518-SNAP FreeBSD 3.0-980518-SNAP #0: Tue Jun  2 19:22:49 CDT 1998     jher@solomon.io.com:/usr/src/sys/compile/SOLOMON  i386
 >
 >> Description:
 > I boot the machine, run my innd server o it and after its 12am expire
 > run, the machine starts screwing up.  The expire run is very memory
 > intensive and usually eats about 200megs of ram.  As soon as it starts,
 > sshd can no longer malloc correctly and tries to malloc 1+gig of memory
 > whenever I ssh into the machine.  I therefore resort to telnetting in and
 > get the message:
 > inetd in realloc(): warning: junk pointer, too low to make sense.
 > but it lets me login.  From that point forward, the cronjobs cease to
 > run correctly.  Basically they startup and exit immediately.  If I send
 > a HUP to sshd's pid, it returns to normal and I can ssh in.  Of course,
 > since cron no longer functions correctly, news is failing to get expired
 > etc.  If I reboot, it usually corrects the problem until the cronjob
 > for news runs at midnight.
 > I'm on a P-II 266Mhz, with 256M SDram, 2940UW scsi (2 controllers), SMC
 > 10/100 Etherpower, and an LX-6 Motherboard.
 >
 > I'm running an SMP version of the same release on a Dual PPro 200Mhz
 > machine with DPT and 2904UW, and SMC 10/100 without having the same
 > problem.  The kernel has esentially the same compile options.  This
 > machine is also running innd and its nightly news.daily (expire) run
 > has a larger amount of data to work with and so far its been flawless.
 > Oh and the Mainboard is an ASUS board.
 >> How-To-Repeat:
 > wait for the news.daily run to happen from the 12am crontab
 >> Fix:
 > reboot
 >> Audit-Trail:
 >> Unformatted:
 
 --
 See complete headers for address and phone numbers
 finger grog@lemis.com for PGP public key

From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
To: jher <jher@io.com>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Thu, 4 Jun 1998 23:41:35 -0400 (EDT)

 <<On Thu, 4 Jun 1998 16:00:14 -0500, jher <jher@io.com> said:
 
 > 	What I have found out is this.  When expire runs it grows to around 
 > 230M in size.  Testing with ssh and telnet, both begin to fail when 62M of
 > Swap is allocated in top.  ssh reports the following debug message:
 
 You're probably suffering from the same cause as the ``daemons dying''
 bug which causes cron on my news server to wet itself after a
 particularly heavy news burst has caused the machine to run out of
 memory.  This bug was definitely present as early as April 1st and as
 late as June 1st (the last two dates I've tried to run).
 
 -GAWollman
 
 --
 Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
 wollman@lcs.mit.edu  | O Siem / The fires of freedom 
 Opinions not those of| Dance in the burning flame
 MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick

From: Poul-Henning Kamp <phk@critter.freebsd.dk>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: jher <jher@io.com>, FreeBSD-gnats-submit@FreeBSD.ORG,
        freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense. 
Date: Fri, 05 Jun 1998 09:42:17 +0200

 In message <199806050341.XAA06128@khavrinen.lcs.mit.edu>, Garrett Wollman writes:
 ><<On Thu, 4 Jun 1998 16:00:14 -0500, jher <jher@io.com> said:
 >
 >> 	What I have found out is this.  When expire runs it grows to around 
 >> 230M in size.  Testing with ssh and telnet, both begin to fail when 62M of
 >> Swap is allocated in top.  ssh reports the following debug message:
 >
 >You're probably suffering from the same cause as the ``daemons dying''
 >bug which causes cron on my news server to wet itself after a
 >particularly heavy news burst has caused the machine to run out of
 >memory.  This bug was definitely present as early as April 1st and as
 >late as June 1st (the last two dates I've tried to run).
 
 Have you guys tried:
 
 	ln -s h /etc/malloc.conf 
 
 --
 Poul-Henning Kamp             FreeBSD coreteam member
 phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
 "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal

From: jher <jher@io.com>
To: Greg Lehey <grog@lemis.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Mon, 8 Jun 1998 10:31:44 -0500

 Sure, that fixes inetd, but that doesn't make my cronjobs work.  Thats the
 main problem.
 
 On Fri, Jun 05, 1998 at 09:46:57AM +0930, Greg Lehey wrote:
 > This symptom seems much more common than this message would suggest.
 > I've seen it in cases where the system has run out of swap, but that
 > doesn't seem to be a requirement.  The "fix" is rather heavy-handed.
 > I've always been able to restart inetd and keep it quiet for some
 > time.
 > 
 > Greg
 > 
 > On Thu,  4 June 1998 at 10:18:42 -0700, jher@io.com wrote:
 > >
 > >> Number:         6858
 > >> Category:       kern
 > >> Synopsis:       inetd in realloc(): warning: junk pointer, too low to make sense.
 > >> Confidential:   no
 > >> Severity:       serious
 > >> Priority:       high
 > >> Responsible:    freebsd-bugs
 > >> State:          open
 > >> Quarter:
 > >> Keywords:
 > >> Date-Required:
 > >> Class:          sw-bug
 > >> Submitter-Id:   current-users
 > >> Arrival-Date:   Thu Jun  4 10:20:01 PDT 1998
 > >> Last-Modified:
 > >> Originator:     jher
 > >> Organization:
 > > Illuminati Online
 > >> Release:        3.0-980518-SNAP
 > >> Environment:
 > > FreeBSD solomon.io.com 3.0-980518-SNAP FreeBSD 3.0-980518-SNAP #0: Tue Jun  2 19:22:49 CDT 1998     jher@solomon.io.com:/usr/src/sys/compile/SOLOMON  i386
 > >
 > >> Description:
 > > I boot the machine, run my innd server o it and after its 12am expire
 > > run, the machine starts screwing up.  The expire run is very memory
 > > intensive and usually eats about 200megs of ram.  As soon as it starts,
 > > sshd can no longer malloc correctly and tries to malloc 1+gig of memory
 > > whenever I ssh into the machine.  I therefore resort to telnetting in and
 > > get the message:
 > > inetd in realloc(): warning: junk pointer, too low to make sense.
 > > but it lets me login.  From that point forward, the cronjobs cease to
 > > run correctly.  Basically they startup and exit immediately.  If I send
 > > a HUP to sshd's pid, it returns to normal and I can ssh in.  Of course,
 > > since cron no longer functions correctly, news is failing to get expired
 > > etc.  If I reboot, it usually corrects the problem until the cronjob
 > > for news runs at midnight.
 > > I'm on a P-II 266Mhz, with 256M SDram, 2940UW scsi (2 controllers), SMC
 > > 10/100 Etherpower, and an LX-6 Motherboard.
 > >
 > > I'm running an SMP version of the same release on a Dual PPro 200Mhz
 > > machine with DPT and 2904UW, and SMC 10/100 without having the same
 > > problem.  The kernel has esentially the same compile options.  This
 > > machine is also running innd and its nightly news.daily (expire) run
 > > has a larger amount of data to work with and so far its been flawless.
 > > Oh and the Mainboard is an ASUS board.
 > >> How-To-Repeat:
 > > wait for the news.daily run to happen from the 12am crontab
 > >> Fix:
 > > reboot
 > >> Audit-Trail:
 > >> Unformatted:
 > 
 > --
 > See complete headers for address and phone numbers
 > finger grog@lemis.com for PGP public key
 > 
 
 -- 
 jher@io.com	Senior Systems Engineer 	jher@fnord.org	Pope
                          http://www.fnord.org
 
 Today is Prickle-Prickle, day 13 in the season of Confusion, 3164.

From: jher <jher@io.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Mon, 8 Jun 1998 10:29:37 -0500

 On Fri, Jun 05, 1998 at 09:42:17AM +0200, Poul-Henning Kamp wrote:
 > In message <199806050341.XAA06128@khavrinen.lcs.mit.edu>, Garrett Wollman writes:
 > ><<On Thu, 4 Jun 1998 16:00:14 -0500, jher <jher@io.com> said:
 > >> 	What I have found out is this.  When expire runs it grows to around 
 > >> 230M in size.  Testing with ssh and telnet, both begin to fail when 62M of
 > >> Swap is allocated in top.  ssh reports the following debug message:
 > >You're probably suffering from the same cause as the ``daemons dying''
 > >bug which causes cron on my news server to wet itself after a
 > >particularly heavy news burst has caused the machine to run out of
 > >memory.  This bug was definitely present as early as April 1st and as
 > >late as June 1st (the last two dates I've tried to run).
 > Have you guys tried:
 > 	ln -s h /etc/malloc.conf 
 This doesn't seem like a complete command here.. what is "h" supposed to be?
 A random file?  No, I don't have a malloc.conf file either way.
 
 -- 
 jher@io.com	Senior Systems Engineer 	jher@fnord.org	Pope
                          http://www.fnord.org
 
 Today is Prickle-Prickle, day 13 in the season of Confusion, 3164.

From: Poul-Henning Kamp <phk@critter.freebsd.dk>
To: jher <jher@io.com>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense. 
Date: Mon, 08 Jun 1998 18:21:49 +0200

 In message <19980608102937.49046@io.com>, jher writes:
 >On Fri, Jun 05, 1998 at 09:42:17AM +0200, Poul-Henning Kamp wrote:
 >> In message <199806050341.XAA06128@khavrinen.lcs.mit.edu>, Garrett Wollman writes:
 >> ><<On Thu, 4 Jun 1998 16:00:14 -0500, jher <jher@io.com> said:
 >> >> 	What I have found out is this.  When expire runs it grows to around 
 >> >> 230M in size.  Testing with ssh and telnet, both begin to fail when 62M of
 >> >> Swap is allocated in top.  ssh reports the following debug message:
 >> >You're probably suffering from the same cause as the ``daemons dying''
 >> >bug which causes cron on my news server to wet itself after a
 >> >particularly heavy news burst has caused the machine to run out of
 >> >memory.  This bug was definitely present as early as April 1st and as
 >> >late as June 1st (the last two dates I've tried to run).
 >> Have you guys tried:
 >> 	ln -s h /etc/malloc.conf 
 
 >This doesn't seem like a complete command here.. what is "h" supposed to be?
 >A random file?  No, I don't have a malloc.conf file either way.
 
 man malloc
 
 --
 Poul-Henning Kamp             FreeBSD coreteam member
 phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
 "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal

From: jher <jher@io.com>
To: freebsd-gnats-submit@freebsd.org, jher@io.com
Cc:  Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Mon, 29 Jun 1998 11:32:22 -0500

 I've done the ln -s h /etc/malloc.conf and i'm still seeing
 
 inetd in realloc(): warning: junk pointer, too low to make sense.
 
 sshd also still has malloc problem and cron ceases to run.  In addition,
 i've upped the
 physical ram to 512M which at least allows "expire" to run in 15 minutes
 instead of 6 hours.
 
 --
 Today is Setting Orange, day 34 in the season of Confusion, 3164.
 
 
 

From: jher <jher@io.com>
To: freebsd-gnats-submit@freebsd.org, jher@io.com
Cc:  Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Thu, 09 Jul 1998 10:27:18 -0500

 Well the last idea suggested to me was replacing the ram.  That did
 
 the trick. Granted it was 512M of ram and I replaced the first two
 
 sticks but now its not failing on the overnight cronjobs.  Consider
 
 this case closed.
 
 --
 Today is Setting Orange, day 44 in the season of Confusion, 3164.
 
 
 
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Thu Jul 9 09:29:16 PDT 1998 
State-Changed-Why:  
originator says hw bug 
State-Changed-From-To: closed->suspended 
State-Changed-By: wollman 
State-Changed-When: Sat Jul 11 11:45:43 PDT 1998 
State-Changed-Why:  
Originator replaced 256M of memory with 512M of memory, thus eliminating 
the low-memory condition which causes the bug.  The bug itself is 
still not fixed, but nobody appears to be working on it, either. 

From: jher <jher@io.com>
To: freebsd-gnats-submit@freebsd.org, jher@io.com, engineering@lists.io.com
Cc:  Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to 
 make sense.
Date: Tue, 18 Aug 1998 14:33:51 -0500

     Since my previous update on this bug, it has taken on a new form.
 I now have the
 machine DIE every 12 hours and sit at the debug prompt as follows.
 
 Fatal trap 12: page fault while in kernel mode
 fault virtual addr = 0x1f80000
 fault code = supervisor read, page not present
 instruction pointer = 0x8: 0xf019048f
 stack pointer = 0x10: 0xf01eef54
 frame pointer = 0x10:0xf01eef88
 code segment = base 0x0, limit 0xfffff, type 0x1b
                             = DPL 0, pres 1, def 321, gran 1
 processor eflags = interrupt enabled, resume, IOPL = 0
 current process = Idle
 interrupt mask = net
 kernel: type 12 trap, code 0
 stopped at _tulip_rx_intrt 0x41f: mov | 0(%eax),%eax
 
 there might be a typo in there as I had to transcribe the db output from
 the screen to
 paper and back to email.  It would be nice if there were some way to
 dump the debug
 output to floppy or swap and read it during reboot or something like
 that.  Also, I
 downgraded the box from 3.0-19980817-SNAP to 2.2.7-current and this bug
 crashed the box within 15 minutes.
 
 --
 Today is Setting Orange, day 11 in the season of Bureaucracy, 3164.
 
 
 

From: John Fieber <jfieber@indiana.edu>
To: freebsd-gnats-submit@freebsd.org
Cc: jher@io.com
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low
 to make sense.
Date: Thu, 5 Nov 1998 17:07:54 -0500 (EST)

 At least some dimension of this PR seems to be the same problem
 as bin/8183 (http://www.freebsd.org/cgi/query-pr.cgi?pr=8183)
 
 I doubt it is hardware related because my inetd started dying
 regularly as a consequence of upgrading from 2.2.7 to 3.0, with
 no hardware change at all.  I've just applied the last patch in
 the bin/8183 and I'll see how it goes.
 
 -john
 

From: Steve Qualls <steve@wnol.net>
To: freebsd-gnats-submit@freebsd.org, jher@io.com
Cc:  Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Wed, 02 Dec 1998 21:26:18 -0500

 Is anyone ever going to post a fix for this It seems like its been
 happening for months now with out a fix. It causes outlook to stop
 POPing the mail.
 

From: Lew Payne <lewiz@netcom.com>
To: freebsd-gnats-submit@freebsd.org, jher@io.com
Cc:  
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to 
 make sense.
Date: Tue, 26 Jan 1999 18:02:44 -0800

 Is someone going to fix this??  It is happening to me,
 using FreeBSD 2.2.8-RELEASE from the CD-ROM.
 
 inetd in realloc(): warning: junk pointer, too low to make sense.
 
 Pentium II/300MHZ, 512MB RAM.  Both machines.
 
 

From: Cy Schubert - BCSC Open Systems Group <cys@wlc.com>
To: freebsd-gnats-submit@freebsd.org, jher@io.com,
	cschuber@uumail.gov.bc.ca, cy@uumail.gov.bc.ca
Cc:  
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Wed, 17 Mar 1999 08:59:04 -0800

 I see this on 3.1R after tripwire runs, which uses 25MB VM on a machine
 with 32MB installed (high scan rate and paging rate of 5-8 pages/second
 while tripwire is running).  Under 2.2.8R i had no problems, however I
 do notice that processes do take more VM under 3.1R, e.g. exmh2 takes
 40MB of VM under 3.1R using an ELF version of wish8.0 while it took 9MB
 under 2.2.8R and under 3.1R using an a.out version of wish8.0.
 
 I also noticed that while tripwire runs under 2.2.8R, the scan rate
 averaged at ~ 700 pages/sec., while under 3.1R the paging rate is
 2000-3000 pages/sec.
 
 The problem is probably in VM somewhere.
 
 -- 
 Regards,                       Phone:  (250)387-8437
 Cy Schubert                      Fax:  (250)387-5766
 Open Systems Group          Internet:  cschuber@uumail.gov.bc.ca
 ITSD                                   Cy.Schubert@gems8.gov.bc.ca
 Government of BC
 

From: Cy Schubert - BCSC Open Systems Group <cys@wlc.com>
To: freebsd-gnats-submit@freebsd.org, jher@io.com,
	cschuber@uumail.gov.bc.ca, cy@uumail.gov.bc.ca
Cc:  
Subject: Re: kern/6858: inetd in realloc(): warning: junk pointer, too low to make sense.
Date: Wed, 17 Mar 1999 12:30:17 -0800

 That should be scan rate at 2000-3000 pages/sec.
 
 
 -- 
 Regards,                       Phone:  (250)387-8437
 Cy Schubert                      Fax:  (250)387-5766
 Open Systems Group          Internet:  cschuber@uumail.gov.bc.ca
 ITSD                                   Cy.Schubert@gems8.gov.bc.ca
 Government of BC
 
State-Changed-From-To: suspended->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Tue Dec 21 08:04:00 PST 1999 
State-Changed-Why:  
Fixes which went into CURRENT for the inetd problem have been merged 
into 3.3-STABLE and have made it into 3.4-RELEASE.  Could you try 
with the newer sources and let me know?  I'd like to try to keep 
one problem per PR, so if we can confirm that the junk pointer 
bug in inetd is really fixed (and I believe it is), I'll want 
to close this PR. 
State-Changed-From-To: feedback->closed 
State-Changed-By: sheldonh 
State-Changed-When: Tue Dec 28 00:47:57 PST 1999 
State-Changed-Why:  
Believed to be fixed in both 3.4-RELEASE and CURRENT.  Regrettably, 
the originator is not in a position to verify. :-( 
>Unformatted:
