Command Logging


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Command Logging
# 1  
Old 01-12-2012
Command Logging

I searched the forums for command logging and the user "Driver" seemed to provide a script for logging shell commands with related info like date and time. The subject was "logging command invocations -cmdlog" . I would be interested in this script.

Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Linux

Syslog not logging successful logging while unlocking server's console

When unlocking a Linux server's console there's no event indicating successful logging Is there a way I can fix this ? I have the following in my rsyslog.conf auth.info /var/log/secure authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies

2. Shell Programming and Scripting

Logging in and running an update file from command

I am trying to upgrade many installations of a gallery script called coppermine through the commandline. I've copied the latest files of the script to each account. Then, I need to run a file gallery/update.php which requires I log in I can create an admin user for myself for each... (2 Replies)
Discussion started by: vanessafan99
2 Replies

3. Shell Programming and Scripting

bash logging al $() command lines

I have been doing a lot more bash on LINUX RedHat and Ubuntu lately, and one thing keeps cropping up intermittently. If I do a $( some-commands ) Command Substitution, the some-commands are logged onto my screen each time they are evaluated. Did I turn on some odd option? It seems to happen just... (13 Replies)
Discussion started by: DGPickett
13 Replies

4. Shell Programming and Scripting

awk command-logging

hi folks, In the following code, logfile remains empty. log_file="/u/Sc/prav.log.$mon$day" ps -ef | grep "myprocess"| awk -v logfile=$log_file '{ system("date >> logfile") }' can u please help as how to log the date to that logfile. thanks in advance! (3 Replies)
Discussion started by: pravfraz
3 Replies

5. Cybersecurity

Full Command Logging?

I am looking for a really good command logging tool to improve the auditing of my servers. I have previously used snoopy but this is currently a bit flaky and causing serious problems for me, it doesn't look like it's been maintained since 2004, it didn't even want to compile until I added -fPIC... (1 Reply)
Discussion started by: humbletech99
1 Replies

6. Solaris

shell command logging

Does anyone have a simple method of logging all shell commands typed by a user (csh in our case)? - I could enable auditing, but this would be overkill - I could enable process accounting, but AFAIK, this does not log arguments Thanks all. (2 Replies)
Discussion started by: minkie
2 Replies

7. UNIX for Dummies Questions & Answers

Command Logging in SCO

Hello, new user here. I am the "administrator" for a few SCO Unix servers here, but do not have much Unix administration experience other than some basic stuff (don't ask). Anyway, I have been charged with finding a way to log all users commands for auditing purposes. This includes root. The log... (2 Replies)
Discussion started by: brian_g
2 Replies

8. UNIX for Dummies Questions & Answers

Logging command invocations - cmdlog

. (1 Reply)
Discussion started by: Driver
1 Replies

9. UNIX for Dummies Questions & Answers

What is command for logging?

Hi, I am trying to recollect the command used to log a file. We use this command just before starting, say, installation. At the end you get a file capturing the series of commands you used during the course of time and sytems response. Could anybody please help. Thanks, Dasa (3 Replies)
Discussion started by: dtamminx
3 Replies

10. UNIX for Advanced & Expert Users

SSH and command logging

Hi all... I've completed the task of deploying SSH over my 400 servers. I don't know if i'm right or wrong, but ssh doesn't do any command-logging, does it? Is there a app i can use to log all commands passed ( besides the usual .sh_history), whith no modification possible by the user, and how... (2 Replies)
Discussion started by: penguin-friend
2 Replies
Login or Register to Ask a Question
Net::DRI::Logging(3pm)					User Contributed Perl Documentation				    Net::DRI::Logging(3pm)

NAME
Net::DRI::Logging - Logging Operations for Net::DRI VERSION
This documentation refers to Net::DRI::Logging version 1.02 SYNOPSIS
This module is never used directly, only its subclasses are used. See the subclasses documentation: Net::DRI::Logging::Files, Net::DRI::Logging::Null and Net::DRI::Logging::Stderr. See also Net::DRI documentation and its "logging()" method. DESCRIPTION
This is the superclass of all logging modules (under the Net::DRI::Logging::* namespace). EXAMPLES
See Net::DRI documentation. SUBROUTINES
/METHODS This is mostly a pure virtual superclass. All subclasses should have the following methods: new() a ref hash is passed with some keys ; besides keys specifically related to the logging class used, some keys are (or should be) understood by all clases. They are: level current level of logging (no messages below this level would be dumped), between: debug info notice warning error critical alert emergency ; default: warning It can be changed anytime later by using the level() method xml_indent 0 or 1 depending if you want your XML strings to be dumped as a long line(0) or indented for humans(1) ; default: 0 encoding if needed, name of encoding to use to convert data stream ; default: UTF-8 name() returns the name as string of the logging modules setup_channel(SOURCE,TYPE,DATA) prepare for a new channel of data comming from SOURCE (package name), of TYPE ; DATA is a ref hash of additional parameter, such as filenames, etc. output(LEVEL,TYPE,DATA1,DATA2,...) add data to channel type TYPE at level LEVEL ('debug', 'info', 'notice', etc.) ; DATA is a ref hash with all data to log or a simple string (the message) ; the logging module should know what to do with it and how to format it (which may depend on the TYPE attribute, which itself is tied to the SOURCE attribute of "setup_channel()"). DIAGNOSTICS
None. CONFIGURATION AND ENVIRONMENT
See the "new()" method. DEPENDENCIES
This module has to be used inside the Net::DRI framework and needs the following components: Net::DRI::BaseClass Net::DRI::Util Net::DRI::Exception INCOMPATIBILITIES
None. BUGS AND LIMITATIONS
No known bugs. Please report problems to author (see below) or use CPAN RT system. Patches are welcome. The interface could be later changed to suit Log::Log4Perl or other Perl standard logging modules, if needed. Other subclasses should be created to cater for other logging destinations (such as a RDBMS). Net::DRI expects these logging modules to be non-blocking and returning immediately. This logging framework is currently only used by Net::DRI::Transport::Socket, it should get applied to other transports and other internal parts of Net::DRI. When LocalStorage do appear inside Net::DRI, logging should probably use it (TODO). SUPPORT
For now, support questions should be sent to: <netdri@dotandco.com> Please also see the SUPPORT file in the distribution. SEE ALSO
<http://www.dotandco.com/services/software/Net-DRI/> AUTHOR
Patrick Mevzek, <netdri@dotandco.com> LICENSE AND COPYRIGHT
Copyright (c) 2009,2010 Patrick Mevzek <netdri@dotandco.com>. All rights reserved. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. See the LICENSE file that comes with this distribution for more details. perl v5.10.1 2010-03-25 Net::DRI::Logging(3pm)