From owner-freebsd-chat Mon May 10 6: 3:45 1999 Delivered-To: freebsd-chat@freebsd.org Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (Postfix) with ESMTP id EABF014BD0 for ; Mon, 10 May 1999 06:03:39 -0700 (PDT) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.3/8.9.2) id IAA13212 for chat@freebsd.org; Mon, 10 May 1999 08:01:42 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 10 May 1999 08:01:42 -0500 (CDT) Reply-To: conrads@neosoft.com From: Conrad Sabatier To: chat@freebsd.org Subject: Stupidity subjects box to *severe* stress test -- FreeBSD passes with flying colors Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ The following was mailed to a friend of mine whose -STABLE box I've been maintaining. Even under the conditions described below, I was still able to rlogin and bring the machine back to a useable state, a real credit to FreeBSD's performance and reliablity. ] -----FW: Stupid, stupid, stupid! ----- Date: Mon, 10 May 1999 07:03:04 -0500 (CDT) From: Conrad Sabatier To: "Wayne F. Cox" Subject: Stupid, stupid, stupid! Got your mail this morning (it's a miracle you were able to send it; must have been a real exercise in frustration, I'm sure). I'm terribly, terribly sorry. It was such a stupid, idiotic mistake. In your root crontab, I had scheduled a job to update your ports collection at 3:00 am (I thought) [ Note: this included a "make -k readmes index" after the actual update ]. What I actually had done, though, was schedule the job to run *every* *friggin'* *minute* starting at 3:00 am. So you had literally *hundreds* of these things going. The scheduling info should have read: 0 3 * * * Whereas, instead, it actually read: * 3 * * * You can see, I'm sure, that the first asterisk was the culprit. It's a real credit to the stability and solidity of FreeBSD that all these processes running simultaneously [in only 64 MB/128 MB swap!] didn't just crash the system altogether. A lesser operating system surely would have choked to death in no time. Talk about a stress test! :-) I've gone in and fixed my error, and killed all the errant processes. Tonight at 3:00 am you should notice a marked difference, I guarantee. Again, I am truly sorry. But even the best of us UNIX Guru types are entitled to an occasional stupid fuck-up. :-) Take care, Conrad -- Conrad Sabatier Acid absorbs 47 times it's weight in excess Reality. --------------End of forwarded message------------------------- -- Conrad Sabatier "I'd love to go out with you, but I've been scheduled for a karma transplant." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message