RE: Clutz-Proof Logging

----- Original Message ----
From: Bill Moran <wmoran@xxxxxxxxxxxxxxxxxxxxxxx>

Many shells keep a history as a matter of normal operation. You might
find that enough for you. Personally, I use bash, and the command
"history" brings the last 100 commands or so.

No, this isn't sufficient. The problems are:
1) occasionally the sysadmin people at the server farm do stuff
2) sometimes I edit files, and of course the shell doesn't record how
3) the shell history seems erratic! It remembers the session clearly, but if I reboot, for example, and look at the history, it's not what I would
expect it to be.

TIA,
Stan
I am not certain if you are using X or console.

On X windows you can set the size of the history to your liking - I usually set to unlimited. Then, as frequently as one wishes, save the session to a log file. I have not found any problem with history not being the "history".

As far as file editing is concerned if the file is important to you then you might want to try saving a snapshot when you open the file and use a small script to both save the snapshot and do a diff report that stores the differences between the file when you opened it and when you saved it. opened. That way you always have as permanent a record as you wish to keep.

My 2 cents

David

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Newbie: save an interpretation session
    ... editing/interpretation session for next Forth interpreter startup. ... In iForth, every line of input is appended to a history file and all lines ... it on the command line. ...
    (comp.lang.forth)
  • Re: Need ideas: automating history dump
    ... > shell's history once a day, or whenever the shell exits normally ... zsh sessions will all have their history lists added to the ... history file, in the order they are killed. ... command line, setting this option will cause the oldest history ...
    (comp.unix.shell)
  • [TOOL] ComLog.pl, a WIN32 Command Prompt Logger
    ... administrator to keep a history of commands typed in the DOS command ... prompt and the associated output, for example on an IIS server. ... # This program captures the input/output of the Windows NT Command Promt ... sub getcurrentdrive ...
    (Securiteam)
  • Release : ComLog 1.0, a WIN32 command prompt logger
    ... a WIN32 command prompt logger ... DOS sessions on Windows NT/2K (should also work on XP, ... This tool can be used by administrator to keep a history of commands ... typed in the DOS command prompt and the associated output, ...
    (Focus-IDS)
  • [Full-Disclosure] Release : ComLog 1.0, a WIN32 command prompt logger
    ... a WIN32 command prompt logger ... DOS sessions on Windows NT/2K (should also work on XP, ... This tool can be used by administrator to keep a history of commands ... typed in the DOS command prompt and the associated output, ...
    (Full-Disclosure)