From owner-freebsd-current  Sun Jul 12 11:45:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA00773
          for freebsd-current-outgoing; Sun, 12 Jul 1998 11:45:33 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alushta.NL.net (alushta.NL.net [193.78.240.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00768
          for <current@freebsd.org>; Sun, 12 Jul 1998 11:45:30 -0700 (PDT)
          (envelope-from benst@terminus.stuyts.nl)
Received: from stuyts by alushta.NL.net with UUCP id <9016-17282>; Sun, 12 Jul 1998 20:45:22 +0200
Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7])
	by terminus.stuyts.nl (8.8.8/8.8.8) with ESMTP id TAA21623
	for <current@freebsd.org>; Sun, 12 Jul 1998 19:36:34 +0200 (MET DST)
	(envelope-from benst)
Received: (from benst@localhost)
	by daneel.stuyts.nl (8.8.5/8.8.5) id TAA06849
	for current@freebsd.org; Sun, 12 Jul 1998 19:36:30 +0200 (MET DST)
Message-Id: <199807121736.TAA06849@daneel.stuyts.nl>
Content-Type: text/plain
MIME-Version: 1.0 (NeXT Mail 3.3 v118.2)
X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2)
Received: by NeXT.Mailer (1.118.2)
From: Ben Stuyts <benst@terminus.stuyts.nl>
Date: Sun, 12 Jul 98 19:36:28 +0200
To: current@FreeBSD.ORG
Subject: Cputime limit exceeded
Reply-To: ben@stuyts.nl
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

I often get the Cputime limit exceeded errors from news-related programs. For  
example:

> Date: Sun, 12 Jul 1998 15:10:00 +0200 (MET DST)
> From: News Subsystem <news>
> To: newscrisis
> Subject: news (urgent): possible expire problems
>
> 66048 kept, 6032 expired
> 3141 residual lines
> 31 links archived, 6997 junked, 154 missing
> Cputime limit exceeded
> /usr/local/news/cnewsbin/nov/expov: expovguts failed in comp/sys/next/announce
> 	...using fallback code

This if from the password file:

news:*:8:8:news:0:0:News Subsystem:/:/nonexistent

And this from login.conf:

news:\
        :path=/usr/local/news/bin /bin /sbin /usr/bin /usr/sbin  
/usr/local/bin /usr/local/sbin:\
        :cputime=infinity:\
        :filesize=128M:\
        :datasize-cur=64M:\
        :stacksize-cur=32M:\
        :coredumpsize-cur=0:\
        :maxmemorysize-cur=128M:\
        :memorylocked=32M:\
        :maxproc=128:\
        :openfiles=256:\
        :tc=default:

I am running xntpd, but at those times there is no internet connection up. I  
thought setting cputime=infinity would solve the problem, but it didn't. I saw  
in the archives that more people had this kind of problem, but I couldn't  
find a solution to it.

The system is cvsupped and built last on June 12. It has otherwise been quite  
stable.

Thanks,
Ben

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message