From owner-freebsd-newbies Wed Nov 3 10: 6:57 1999 Delivered-To: freebsd-newbies@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 407E514D86 for ; Wed, 3 Nov 1999 10:06:52 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11j4nl-0009lj-00 for freebsd-newbies@freebsd.org; Wed, 3 Nov 1999 18:06:29 +0000 Date: Wed, 3 Nov 1999 19:05:50 +0100 (CET) From: Marc Schneiders To: freebsd-newbies@freebsd.org Subject: rpc.rstatd :-) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Recently I discovered 'rup', which shows me the uptime and load of all machines on my little lan, after I made sure rpc.statd was running (through inetd) on all of them. Quite nice. I played around a little with a small script to use 'rup' to display the uptime in my sig-file (see below). Unlike uptime it leaves out the number of users in its output, which I like. Anyway, this script worked, so I put it into /etc/crontab and went to bed. This morning I had very many messages in my mailbox from cron, saying rup timed out... I don't know exactly what happened, but I suppose I started rpc.statd manually in addition to it being run by inetd. The size of it as reported by top was 257MB this morning... (I have 256MB RAM). It was indeed not working. When I killed it, it worked again. I suppose the inclusion of rpc.statd in a cronjob combined with running it on its own made it grow and grow and grow. Never do this, unless you like a lot of mail in the morning :-) Marc Schneiders marc@venster.nl marc@oldserver.demon.nl propro 1:20pm up 7 days, 7:02, load average: 2.00 2.00 2.00 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message