From owner-freebsd-current@FreeBSD.ORG Thu Nov 20 23:26:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6B1716A4CE for ; Thu, 20 Nov 2003 23:26:01 -0800 (PST) Received: from server.vk2pj.dyndns.org (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EEF543FB1 for ; Thu, 20 Nov 2003 23:26:00 -0800 (PST) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1])hAL7PwJD071221; Fri, 21 Nov 2003 18:25:58 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.12.9p1/8.12.9/Submit) id hAL7PqW2071220; Fri, 21 Nov 2003 18:25:52 +1100 (EST) (envelope-from peter) Date: Fri, 21 Nov 2003 18:25:52 +1100 From: Peter Jeremy To: Richard Coleman Message-ID: <20031121072552.GA71152@server.vk2pj.dyndns.org> References: <2147483647.1069240727@[192.168.42.6]> <20031120095214.GA68334@server.vk2pj.dyndns.org> <050d01c3afa8$1dfb97a0$b9844051@insultant.net> <156539179.20031121001033@andric.com> <061f01c3afbd$4692a040$b9844051@insultant.net> <3FBD788A.4070809@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FBD788A.4070809@mindspring.com> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: Unfortunate dynamic linking for everything X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2003 07:26:02 -0000 On Thu, Nov 20, 2003 at 09:29:30PM -0500, Richard Coleman wrote: >But I've often wondered how frequently a production system has such >problems. I've been a sysadmin for many years and can't remember this >ever happening. It's much more common to blow a hard drive, or have >flaky memory, etc. We've had a customer whose "system administrator" installed a root cronjob including "rm -r / somedirectory/tmp" (note the space) - on all four production machines as well as their model system. (The person in question is a classic example of "a little knowledge is a dangerous thing"). The console logs (which were on another unaffected system) made interesting reading - he had spent a significant amount of time attempting to reboot the systems before calling for help. Peter