I've been following this thread with interest. I have used Putty for
years as its the de-facto standard for decent ssh terminals on Windows
boxes.
A slightly more radical suggestion for the log files. Since Putty is
open source, have a look at the code and see if you can easily add in a
timestamp per line for the log file section.
That gives you two features:
1. You now have a verifiable traceable source as you have downloaded and
compiled it. I have worked in environments where we need to trace every
bit of code that comes into the data centre. We need to know where we
downloaded it from, what the license was, authority from legal to use
etc etc. Your situation might not warrant it :)
2. You now have unique lines with a timestamp, a hostname and a TTY
session (I assume). I think that guarantees uniqueness.
I have no idea if Putty can be modified in this way, but it wouldn't
hurt to have a look, see if the change is easy, do the change and then
send some diffs back to the Putty team. If they accept the changes
you're sorted. If they don't well, Putty doesn't change that much over
time so you could probably use your version for years to come.
Rob
On 2 Feb 2017, at 19:53, Stephen Chrzanowski wrote:
I can only get to our customer machines by jumping into a server that
has
access to both sides of the network. Our side, and the customer side.
I
can't get to a customers machine directly. The &H is out, but I'm
already
doing the rest.
The image in my head of what my program is going to do is that I feed
it a
date range, a server I'm interested in, and optionally provide text
that
further filters the information I'm looking for. Once I have the
filtered
data, I'd have a list of days that I'd been on that exact server,
and/or
entries that mention my subject server, and I can see the text only
pertaining to that machine and date range. I'd be able to read the
full
set of activities on that machine for that day, and not have to hop
around
to multiple log files.. This would get rid of the concept of many log
files as well, since all files are now one. Kind of Borg-ish?
On Thu, Feb 2, 2017 at 11:54 AM, Donald Griggs <dfgri...@gmail.com>
wrote:
Maybe another method to consider:
This guy shows that Putty appears to support creating separate log
files
for each session including a timestamp in the file name.
https://www.viktorious.nl/2013/01/14/putty-log-all-session-output/
Could your script import any new log files it sees, then move them to
an
archive?
That way, you'd never have to read through a huge log file to find
what
should be imported.
==========================From the page linked above:
I am using some putty parameters which will make every session
unique, in
this case “&H-&Y&M&D-&T.log”, which means:
- &H = hostname for the session
- &Y = year
- &M = month
- &D = day
- &T = time
==========================================
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
