Date: Fri, 21 Nov 2003 18:25:52 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Richard Coleman <richardcoleman@mindspring.com> Cc: current@freebsd.org Subject: Re: Unfortunate dynamic linking for everything Message-ID: <20031121072552.GA71152@server.vk2pj.dyndns.org> In-Reply-To: <3FBD788A.4070809@mindspring.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031121072552.GA71152>