Mag Gam on 15 Sep 2007 14:24:42 -0000


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Bash History question

  • From: "Mag Gam" <magawake@gmail.com>
  • To: "Philadelphia Linux User's Group Discussion List" <plug@lists.phillylinux.org>
  • Subject: Re: [PLUG] Bash History question
  • Date: Sat, 15 Sep 2007 10:24:35 -0400
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=qKoA0uvPJQWpG9Y62PsaLSvaoLxsOuVSxff6aq06Zb0=; b=R1vADCQJJBg4O4eauGhrsKxGdJbcDKTXdHeEgkaD2qJCJ6OqoHwK5bhR4ARGgVqlGkkDYSMioqw04CeqPPmZxvAkE+IrpYmvQZG941NwDA7d3+luLjo1f4TYkqDXYnwLEUfCpn8PiP9HSf1c66gzwghed9jjjG3nOeAnUVyjuGw=
  • Reply-to: Philadelphia Linux User's Group Discussion List <plug@lists.phillylinux.org>
  • Sender: plug-bounces@lists.phillylinux.org
Nice trick.

Will try that


On 9/14/07, Dan Widyono <dan@widyono.net> wrote:
I suppose if you're changing PROMPT_COMMAND anyway, you could wrap your
history -a command with your own home-grown locking using e.g. "ln -s $$
$HOME/.bash_history.lck 2>/dev/null && history -a && rm -f
$HOME/.bash_history.lck 2>/dev/null; history -n".

?

Dan W.

On Fri, Sep 14, 2007 at 04:38:02PM -0400, JP Vossen wrote:
> Chet says, "There's no file locking.  The burden is on the user to
> synchronize."
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug

___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug