From owner-freebsd-questions@FreeBSD.ORG Tue Jan 8 23:38:53 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C2B54400 for ; Tue, 8 Jan 2013 23:38:53 +0000 (UTC) (envelope-from andre@drenet.info) Received: from mail-yh0-f51.google.com (mail-yh0-f51.google.com [209.85.213.51]) by mx1.freebsd.org (Postfix) with ESMTP id 711D9315 for ; Tue, 8 Jan 2013 23:38:53 +0000 (UTC) Received: by mail-yh0-f51.google.com with SMTP id f73so229050yha.38 for ; Tue, 08 Jan 2013 15:38:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drenet.info; s=google; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=kUUuQLb8xINPsygBAWa/nH0w+e92NtJSlScDOSHD450=; b=UdOoXAUIFy4AytDqf8w6GLbSwsYvmLcSZXomOTt0EK+UnZUBewGebGt/ocdc7blBHA kawlyTsA3YlNUNdT58lISTDF/ciGY/9RLxq4QNn49os9GDveHzCu/Iv5g1yzPyFuYIqt JH0a8gvQBvrJi4JsrjDCuzCRP3ZWtOyegoP4k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=kUUuQLb8xINPsygBAWa/nH0w+e92NtJSlScDOSHD450=; b=Wh1PyT500SnXUNNrYrNmSfUQjdluc8uO57+Z7YVBbqdYKhcIqkoyEZi6/A6G2IhLE0 PL0iehA86DQ3sToj7y9aXpeH3lvUPXEObXiuh3EfAFfaxGu0By7foU+V8BWr+gWm1x4a erzDx0XlU9KCl8Gc9PGOM5huzVrdMwE3fVrHg5IcT/cujL7DN/xmE+TFua2unTus/x04 n4PdgMZauaWnwKdOoJvuPgGc4ks4D1yIh2wMEWmI9J/xhEz4ssAnNQpAZqEL9GH/g5fA xFjyRabZBulI/KppjiE15wsPaM+xtnB7c2Ss3QLNlzzbHGAyc6IjG1zV41XdtoYjdQLe rOQQ== X-Received: by 10.236.84.197 with SMTP id s45mr75081526yhe.110.1357688326930; Tue, 08 Jan 2013 15:38:46 -0800 (PST) Received: from desktop.drenet.local ([184.90.29.173]) by mx.google.com with ESMTPS id i26sm72862298yhc.10.2013.01.08.15.38.46 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 15:38:46 -0800 (PST) Message-ID: <50ECADFF.6080003@drenet.info> Date: Tue, 08 Jan 2013 18:38:39 -0500 From: Andre Goree User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Subject: Re: Bash history empty on login References: <201301080759.52247.dyioulos@onpointfc.com> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Gm-Message-State: ALoCoQn9Hx+IYhvqyHk38jumA10BuyrWgH6TPITEPfPiPYtfEvAANTGr8gOwk7uQhpV3iwSk3rtJ Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2013 23:38:53 -0000 On 01/08/13 09:11, Trond Endrestøl wrote: > On Tue, 8 Jan 2013 09:05-0500, Andre Goree wrote: > >> On Tue, 08 Jan 2013 07:59:51 -0500, Dimitri Yioulos >> wrote: >> >>> >>> Hope I'm not offending you if the following are things >>> you've tried as a matter-of-course: >>> >>> After booting up, is history started, or do you have to do >>> that manually? Have you run "set -o" to see if history is >>> enabled? If it isn't, then "set -o history". Is a "clear" >>> command being issued from anywhere upon logout or reboot? >>> >>> Just some thoughts. >>> >> >> No offense at all, thanks for your suggestions! I'm currently at work so I'll >> test this when I get home (this is on a desktop running 8.3-stable). I've >> never had to do anything special when using bash on FreeBSD. I'll be sure to >> check th output of "set -o" and report back here. >> >> If there's an erroneous 'clear' command somewhere, it must be on logout since >> I can easily test this problem being that I use tmux. :) I also do not have >> a .bash_logout file, if that matters. >> >> Thanks for the suggestions, I'll let you know what turns up. > > What are the permissions of ~/.bash_history? > > Usually they are set to 0600 in octal due to security concerns and > rightfully so. Could they be (re)set to 0400 or even 0000? > I think I've found the culprit, however: [agoree@desktop ~]$ echo $HISTFILESIZE 1024000 [agoree@desktop ~]$ echo $HISTFILE /home/agoree/.bash_history [agoree@desktop ~]$ ll /home/agoree/.bash_history -rw------- 1 agoree agoree 12k Jan 5 14:09 /home/agoree/.bash_history [agoree@desktop ~]$ cat /home/agoree/.bash_history cat: /home/agoree/.bash_history: Input/output error [agoree@desktop ~]$ file /home/agoree/.bash_history /home/agoree/.bash_history: ERROR: cannot read `/home/agoree/.bash_history' (Input/output error) I suppose I'm in need of a scrub, eh? Or perhaps just a tweak to $HISTFILE until I have the time (or energy) to deal with the scrub -- probably not a good idea, but sense all my important data is kept on a NAS... :p -- Andre Goree andre@drenet.info