Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Logging all console activity to a file - how? Post 302121238 by patwa on Tuesday 12th of June 2007 02:22:26 PM
Old 06-12-2007
Logging all console activity to a file - how?

Hi all,

Well I've had a bit more experience with Unix-like environments since my last post, now that I have started working on my website in earnest and am doing much of the file manipulation via the command line through SSH.

The thing is, I want to be able to log all console activity, basically everything that appears in the window, both my input and the returned output from the system.

How do I do this on a cygwin port? I couldn't find any commands to do it through Google, or maybe I'm not using the right terminology.

Thanks.

H.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

file activity (open/closed) file descriptor info using KORN shell scripting

I am trying to find a way to check the current status of a file. Such as some cron job processes are dependent on the completion of others. if a file is currently being accessed / modified or simply open state I will wait until it is done being processed before attempting the next process on that... (3 Replies)
Discussion started by: Gary Dunn
3 Replies

2. UNIX for Dummies Questions & Answers

logging users activity

Hello All! Does anyone know of a nice way to log commands in solaris 8. What I need is a program or script that saves any command that a user does in solaris command prompt. So when Steven logs in on a system, it should record everything he does, from an ls to exit with timestamps. I've been... (6 Replies)
Discussion started by: dozy
6 Replies

3. Linux

Recording X or VNC Activity to a Video File?

I have the need to record some step by step instructions to help with instruction in using Fedora Core 3. I was wondering if there are any ways to capture X or VNC activity to a video file. It can be any of the most common formats (MPEG, DiVX/ViDX, Ogg Theora, etc...) Does anyone know of any apps... (3 Replies)
Discussion started by: deckard
3 Replies

4. Shell Programming and Scripting

activity on a file

is there anyway to tell when an activity is happening on a file. i'm talking about something deeper than what ls -l can give. when i say activity, i want to know exactly when any commands was run on a specific file. i.e, did anyone run the mail command on this file. did anyone cat this... (2 Replies)
Discussion started by: Terrible
2 Replies

5. BSD

Logging to /dev/console

Hi, The output of the cat ttys on a free BSD m/c console none unknown off secure # # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyd0 "/usr/libexec/getty std.9600" unknown on secure ttyd1 "/usr/libexec/getty std.9600" dialup off ttyd2... (0 Replies)
Discussion started by: mlalitha
0 Replies

6. UNIX for Dummies Questions & Answers

Windows to Linux remote console using VNC brings up blank console screen with only mouse pointer

:confused:Hi This was installed on the Linux box a few weeks back by a guy that no longer works for us. All worked fine until last week. Now when we connect its just a blank screen with no icons. I get a whole bunch of errors when starting the service too: Tue Feb 23 14:29:45 2010 ... (1 Reply)
Discussion started by: wbdevilliers
1 Replies

7. Shell Programming and Scripting

logging to file

I am trying to figure a way to have a log file and still keep the output in the terminal in a script. The example below logs to a file nicely but i still want the output in the terminal as well #!/bin/bash #Create a log exec >> /path/to/my/logfile echo "hello world" Any help would be... (3 Replies)
Discussion started by: dave100
3 Replies

8. Shell Programming and Scripting

Event logging to file and display to console | tee command is not able to log all info.

My intention is to log the output to a file as well as it should be displayed on the console > I have used tee ( tee -a ${filename} ) command for this purpose. This is working as expected for first few outputs, after some event loggin nothing is gettting logged in to the file but It is displaying... (3 Replies)
Discussion started by: sanoop
3 Replies

9. Solaris

How can i prevent logging user1 from console?

Dear all, i have two users user1 and user2 i want force user1 to login first by user2 and then su - user1 i want to prevent logging user1 from console directly (5 Replies)
Discussion started by: maxim42
5 Replies

10. 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
console(n)						       Tk Built-In Commands							console(n)

__________________________________________________________________________________________________________________________________________________

NAME
console - Control the console on systems without a real console SYNOPSIS
console subcommand ?arg ...? _________________________________________________________________ DESCRIPTION
The console window is a replacement for a real console to allow input and output on the standard I/O channels on platforms that do not have a real console. It is implemented as a separate interpreter with the Tk toolkit loaded, and control over this interpreter is given through the console command. The behaviour of the console window is defined mainly through the contents of the console.tcl file in the Tk library. Except for TkAqua, this command is not available when Tk is loaded into a tclsh interpreter with "package require Tk", as a conventional terminal is expected to be present in that case. In TkAqua, this command is ony available when stdin is /dev/null (as is the case e.g. when the application embedding Tk is started from the Mac OS X Finder). console eval script Evaluate the script argument as a Tcl script in the console interpreter. The normal interpreter is accessed through the consolein- terp command in the console interpreter. console hide Hide the console window from view. Precisely equivalent to withdrawing the . window in the console interpreter. console show Display the console window. Precisely equivalent to deiconifying the . window in the console interpreter. console title ?string? Query or modify the title of the console window. If string is not specified, queries the title of the console window, and sets the title of the console window to string otherwise. Precisely equivalent to using the wm title command in the console interpreter. ACCESS TO THE MAIN INTERPRETER
The consoleinterp command in the console interpreter allows scripts to be evaluated in the main interpreter. It supports two subcommands: eval and record. consoleinterp eval script Evaluates script as a Tcl script at the global level in the main interpreter. consoleinterp record script Records and evaluates script as a Tcl script at the global level in the main interpreter as if script had been typed in at the con- sole. ADDITIONAL TRAP CALLS
There are several additional commands in the console interpreter that are called in response to activity in the main interpreter. These are documented here for completeness only; they form part of the internal implementation of the console and are likely to change or be mod- ified without warning. Output to the console from the main interpreter via the stdout and stderr channels is handled by invoking the tk::ConsoleOutput command in the console interpreter with two arguments. The first argument is the name of the channel being written to, and the second argument is the string being written to the channel (after encoding and end-of-line translation processing has been performed.) When the . window of the main interpreter is destroyed, the tk::ConsoleExit command in the console interpreter is called (assuming the con- sole interpreter has not already been deleted itself, that is.) DEFAULT BINDINGS
The default script creates a console window (implemented using a text widget) that has the following behaviour: [1] Pressing the tab key inserts a TAB character (as defined by the Tcl escape.) [2] Pressing the return key causes the current line (if complete by the rules of info complete) to be passed to the main interpreter for evaluation. [3] Pressing the delete key deletes the selected text (if any text is selected) or the character to the right of the cursor (if not at the end of the line.) [4] Pressing the backspace key deletes the selected text (if any text is selected) or the character to the left of the cursor (of not at the start of the line.) [5] Pressing either Control+A or the home key causes the cursor to go to the start of the line (but after the prompt, if a prompt is present on the line.) [6] Pressing either Control+E or the end key causes the cursor to go to the end of the line. [7] Pressing either Control+P or the up key causes the previous entry in the command history to be selected. [8] Pressing either Control+N or the down key causes the next entry in the command history to be selected. [9] Pressing either Control+B or the left key causes the cursor to move one character backward as long as the cursor is not at the prompt. [10] Pressing either Control+F or the right key causes the cursor to move one character forward. [11] Pressing F9 rebuilds the console window by destroying all its children and reloading the Tcl script that defined the console's be- haviour. Most other behaviour is the same as a conventional text widget except for the way that the <<Cut>> event is handled identically to the <<Copy>> event. EXAMPLE
Not all platforms have the console command, so debugging code often has the following code fragment in it so output produced by puts can be seen while during development: catch {console show} SEE ALSO
destroy(n), fconfigure(n), history(n), interp(n), puts(n), text(n), wm(n) KEYWORDS
console, interpreter, window, interactive, output channels Tk 8.4 console(n)
All times are GMT -4. The time now is 03:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy