Re: [leafnode-list] Cannot allocate memory?

[Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

jom1@xxxxxxxxxx writes:

> I agree, but in this case texpire will stop with the message:
> "lockfile /var/lock/news/fetchnews.lck exists, abort ..."
> .. and also fetchnews (in this case) is *not* affected.

I don't understand the last line of this paragraph. texpire is currently
terminating right away if fetchnews is still active. I'm not sure why it
does that, it's code that predates my involvement with leafnode.

Some programs wait until the lock file becomes available, others don't
and abort right away. That is inconsistent, and that may change, but
there is more important work to do.

> The low water mark is for me useless... :-)
> (texpire should correct that anyway if you need the exact low water
> mark).

Well, the low water mark may influence how much memory your newsreader
reserves when "entering" a group, and you don't necessarily run texpire
straight after applyfilter.

While some inefficiency conditions may (and probably will) still lurk in
the code, robustness is more important to me at the moment.

-- 
Matthias Andree

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."         Benjamin Franklin

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list