From owner-freebsd-questions Fri Dec 31 11:41:13 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id D739A14E66 for ; Fri, 31 Dec 1999 11:41:09 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id UAA14162 for freebsd-questions@FreeBSD.ORG; Fri, 31 Dec 1999 20:41:07 +0100 (CET) (envelope-from olli) Date: Fri, 31 Dec 1999 20:41:07 +0100 (CET) From: Oliver Fromme Message-Id: <199912311941.UAA14162@dorifer.heim3.tu-clausthal.de> To: freebsd-questions@FreeBSD.ORG Subject: Re: shell history files Organization: Administration TU Clausthal Reply-To: freebsd-questions@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ben Smithurst wrote in list.freebsd-questions: > aunty wrote: > > Is there some way to stop users from deleting their .bash_history files? > > Try "chflags sunlnk" on them, it might work. That won't prevent from ``cp /dev/null .bash_history'' to effectively delete the history. Sue, why do you want to have the users' history files preserved anyway? If this is for user monitoring, then it is a bad way. It is unreliable and can easily be faked and forged. Better use process accounting for this (see ``man lastcomm'' and ``man 8 sa''). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message