On 2 Feb 2017, at 8:05pm, Stephen Chrzanowski wrote:
> There's a little bit more involved than just consolidating the files into
> one that I need. Specifically, since the command line on all customer
> linux machines are formatted a certain way, I can easily identify what
> machine I'm specifi
Definitely radical and possible, but something I don't think I'd like to
take on, simply because I'm a Delphi dev'r, not C/C++, although, I did do
10 other peoples final C++ projects back in my college days, but that was
two decades ago. (I don't mind saying that, but man do I hate realizing
that t
There's a little bit more involved than just consolidating the files into
one that I need. Specifically, since the command line on all customer
linux machines are formatted a certain way, I can easily identify what
machine I'm specifically looking at, and filter results based on that.
Because I'm
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
times
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 t
On 2 Feb 2017, at 4:48pm, Stephen Chrzanowski wrote:
> Unfortunately no, there is no time stamp at the command lines, and I can't
> add that ability (Maybe if I setup my own new account on our jump-point
> server, but then I've got another kettle to deal with). The only reference
> to a time i
Unfortunately no, there is no time stamp at the command lines, and I can't
add that ability (Maybe if I setup my own new account on our jump-point
server, but then I've got another kettle to deal with). The only reference
to a time is based on the filename that Putty creates the file, and the
las
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 the
On 2 Feb 2017, at 4:22pm, Stephen Chrzanowski wrote:
> But, in my preplanning, scenario development and brain storming, the above
> paragraph is going to destroy my machine doing a [ select * from CmdLine
> where upper(CmdEntered) =upper('SomeText') ] every time I read a new line
> from a new lo
Interesting idea. Does LastInsertID return the row that was a dupe? I
suppose I can test that..
On Thu, Feb 2, 2017 at 11:34 AM, Paul Sanderson <
sandersonforens...@gmail.com> wrote:
> You could make the CmdEntered field unique, or create a hash on the
> uppercase content of the command and
You could make the CmdEntered field unique, or create a hash on the
uppercase content of the command and make that a unique key.
Then use INSERT OR IGNORE...
Paul
www.sandersonforensics.com
skype: r3scue193
twitter: @sandersonforens
Tel +44 (0)1326 572786
http://sandersonforensics.com/forum/conten
By a new requirement of my manager, we're asked to log all our SSH sessions
to our customer machines. The current Windows search is a PITA, grepping
for text is burdensome considering the number of sessions I open per day,
and being a pack rat, I love reading about stuff I did years ago. :] (Not
12 matches
Mail list logo
