From owner-freebsd-isp Wed Jan 5 21:38:57 2000 Delivered-To: freebsd-isp@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id DA86A14DF8 for ; Wed, 5 Jan 2000 21:38:54 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id XAA12631; Wed, 5 Jan 2000 23:38:45 -0600 (CST) Date: Wed, 5 Jan 2000 23:38:45 -0600 From: Tim Tsai To: Tom Cc: up@3.am, FreeBSD ISP List Subject: Re: Why I have to reboot at times; was:RE: uptimes, Woo Hoo Message-ID: <20000105233845.B12339@futuresouth.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I thought this might be the case *except* I've had amanda complain that it > > is "unable to allocate memory", every couple of weeks or so, and a reboot > > is the only thing that fixes it. I have amanda as a "default" user in > > /etc/login.conf, which has no restrictions (users are a different class > > with lots of restrictions) Actually this is probably a different kind of memory issue. Amanda leaves a shared memory segment behind everytime there is an error. Eventually you run out of shared memory handles (the default is a very small number). Next time it happens run "ipcs" and then "ipcrm -m shm_id" and it should take care of your problem. It's a very common Amanda issue. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message