From: "Julian L. Ho" <jh6j+@andrew.cmu.edu>
To: rc@archone.tamu.edu
Subject: history on AFS
Date: Tue, 25 Feb 1992 02:36:21 -0600 [thread overview]
Message-ID: <699006981.4235.0@sucre.mdg.andrew.cmu.edu> (raw)
Sorry if this isn't the sort of thing you want in your mailbox. Here
is what I've been using to keep my history file updated in spite of
AFS...
-J
# AFS holds a complete history, always. This is atomic on a per machine,
# per login basis. Avoid logging out more than once, at the same time.
# history file for this shell and all its children
# put on the local hard drive (hopefully O_APPEND works there)
history = /tmp/. ^ $USER ^ _history_ ^ $pid
# build history file (or turn off all history processing)
if (cp $home/.history $history) {
oldhistsiz = `{ wc -l $history }
oldhistsiz = $oldhistsiz(1)
} else
history = ()
# clean up machine local history
# add to sigexit
fn history {
if (~ $history ())
return
if (~ $oldhistsiz ())
oldhistsiz = `{ wc -l $history }
L = `{ expr $oldhistsiz(1) + 1 } \
sed -n $L ^ ',$p' $history >>$home/.history &&
rm -f $history
}
reply other threads:[~1992-02-25 8:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=699006981.4235.0@sucre.mdg.andrew.cmu.edu \
--to=jh6j+@andrew.cmu.edu \
--cc=rc@archone.tamu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).