Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1.chuqui 4/7/84; site nsc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!harpo!decvax!ittvax!dcdwest!sdcsvax!bmcg!cepu!trwrba!trwrb!sdcrdcf!hplabs!nsc!chuqui
From: chuqui@nsc.UUCP
Newsgroups: net.news
Subject: Re: expire bug? HELP!
Message-ID: <942@nsc.UUCP>
Date: Mon, 14-May-84 10:21:56 EDT
Article-I.D.: nsc.942
Posted: Mon May 14 10:21:56 1984
Date-Received: Wed, 16-May-84 07:10:37 EDT
References: <121@green.UUCP>
Organization: National Semiconductor, Sunnyvale
Lines: 23

Bill:

That looping problem was found to have been caused because malloc() calls
were not checked for correct completion, and allocated space not correctly
returned. This only tends to show up on smaller machines. I have a version
of expire that has this fixed, and if you want it drop me a note by mail 
and I'll ship you a copy.

Note on the version of expire that I posted a while back:
    It seems that the reason the -r and -h routines in expire blow up
    on some systems is because they use the DBM routines regardless of
    whether or not the -DDBM flag is set during compilation. This is a 
    slip up and as soon as I get some time I will see about correcting 
    this. As far as I can tell, if your system supports dbm you should 
    be using it with news, and if you do the expire should work. 

chuq
-- 
>From the closet of anxieties of:			Chuq Von Rospach
{amd70,fortune,hplabs,ihnp4}!nsc!chuqui			(408) 733-2600 x242

Half asleep I hear a voice; is it only in my mind?
Or is it someone calling me, someone I failed and left behind?