Tcl: Outputting Unix console without Buffering


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Tcl: Outputting Unix console without Buffering
# 1  
Old 06-02-2009
Tcl: Outputting Unix console without Buffering

Hi,

I'm have a tcl application using expect. The application is connecting to a unix box and is running a script. What i need my app to do is show the output of the console as the script runs in realtime. At the moment, it my app is waiting until the script finishes and then dumps what is buffered.
Can someone help me get it working in realtime.
Here is the code i have so far:

Code:
.msg.box delete 1.0 end
    .msg.box insert end "Please Wait...\n"
    spawn ssh -q user@server /home/user/Scripts/test/20R-Start
    expect eof { .msg.box insert end $expect_out(buffer) }

As you can see, it runs the script, uses expect to buffer then outputs when finished.
Is there a way to get it to output to .msg.box in realtime, maybe use stdout??

Thanks,
Phil.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

Help with AT&T UNIX SYSTEM V Version 4 Console Login

Hello I install AT&T UNIX System V Release 4 Version 2.1 (3.5) on Emulator Bochs 2.6.8 here I done with all Base .img file upload after uploading 10 the base img file System take restart and after that System ask for console Login. which is as root and password set by me. But it will NOT allow... (7 Replies)
Discussion started by: Akshay Nalange
7 Replies

2. Shell Programming and Scripting

Getting piped input from a program that's buffering it's stdout

The old buffering problem again, in a very specific case. On FreeBSD this time, but it's the generic line-buffered vs fully-buffered problem. I'm trying to pick an available bluetooth speaker (all named audio_N), by pinging all of them en mass and taking the first to respond. The... (10 Replies)
Discussion started by: Juha Nurmela
10 Replies

3. UNIX for Dummies Questions & Answers

Can we build a tool for Windows to retrieve data from UNIX servers (putty console)

Hi Friends, Is it possible to build a windows tool ( a java applet maybe? ) which can retrieve data and display after performing certain commands on unix servers ( simple grep / script output) after logging into putty console. I am on a company server so please bear that in mind. I might have... (23 Replies)
Discussion started by: srkmish
23 Replies

4. UNIX for Advanced & Expert Users

Discussion on buffering of standard I/O library

Hi, There are three type of buffering: Fully buffered,line buffered,and unbuffered. The goal of the buffering provided by the standard I/O library is to use the minimum number of read and write calls. I understand that decrease write() calls when use output function output data to a file ,... (4 Replies)
Discussion started by: Edward114
4 Replies

5. 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

6. UNIX for Dummies Questions & Answers

how can perform zip or unzip at unix console

how can perfrom zip or unzip for bulk of files at unix console can anybody tell that command (2 Replies)
Discussion started by: lmraochodisetti
2 Replies

7. Programming

Outputting a VMS quadword time in UNIX

I am writing a C program under UNIX which needs to write out a VMS quadword time for the current time (to a file) This quadword is the number of 100 nanoseconds since 1858. I know I can easily get the time in secs since 1970 in UNIX/C. The problem is how to multiply by a rather large number... (2 Replies)
Discussion started by: davebrown
2 Replies

8. UNIX for Advanced & Expert Users

problem with diff and tcl scripts freaking out unix

running solaris 2.5.1 on a sparc5, with less than 12 users runnign compilers, gui's, really not a heavy load on it however, sometimes, not always, when users run diff, or sdiff or a .tcl script, the computer locks up. One time right before everything froze, I noticed in top, that the sdiff process... (2 Replies)
Discussion started by: kymberm
2 Replies

9. Solaris

Question about pipes in solaris (and others) and buffering....

This is weird, so I'm hoping someone here knows solaris and how it handles pipes... OK... here goes... Theres this log file, right? I want to tail -f it, grep that, gzip that, then pipe that into more commands. Well thats easy, right? tail -f file | grep pattern | gzip | otherstuff... ... (1 Reply)
Discussion started by: sannik
1 Replies

10. Windows & DOS: Issues & Discussions

Windows Buffering during playing

Hello! Will someone out there pls help in clearifying what is really wrong with my system. I use window 98 as my operating system. I am connected to a proxy server for browsing the net. Whenever l am listening to music online l have the problem of intermitted break in which the playing will... (10 Replies)
Discussion started by: kayode
10 Replies
Login or Register to Ask a Question
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)