Hello
I run a program that creates number of processes.
Is there a way of viewing their standard output on terminal and logging it to a log file simultaneously? (3 Replies)
Hi all,
I have a c++ program which is running fine but has some printfs which its spews on to the screen, which I need for debugging.
But, I execute this program through a java, i.e I run a java program which actually launches my c++ executable and when it does this, I see none of my printfs... (1 Reply)
Hiya all,
Simple question - yet no simple answer im afraid !
Is there a way to execute a shell script (child) which returns one line and get the current (parent) shell to execute the stdout from the child ???
example
child.sh
#!/bin/sh
echo "setenv DISPLAY xxx:03"
parent_prompt>... (5 Replies)
I am using a third party API to get some real time feed. When I run the command it shows the results properly:
etd@mhs-apps5009 $ mamalistenc -m lbm -tport mamaqa -S MLALERTS -s KANA wFinancialStatus
Type CTRL-C to exit.
(null).MLALERTS.KANA Type: INITIAL Status OK
wFinancialStatus |... (5 Replies)
Does anyone know how I can use gzip to zip a large log file on the fly.
My simulation is currently logging a large file that I need for analysis at a later point. However the files are so huge that I may even run out of disk space. The content is mainly text so when compressed the files are... (2 Replies)
I want to split big files based on a pattern to stdout.
Although csplit works well for me splitting the output into separate files (e.g. xx00, xx01, xx02, ...), the following is not working as expected:
<code>
# assuming pattern occurs less than 100 times
csplit bigfile '%pattern%'... (2 Replies)
Can somebody explain to me why the diff output is not going to stderr?
Yet when I issue a diff from the command line the return code is -ne 1.
I am guessing diff always writes to stdout???
Is there away I can force the difff to write to stderr USING THE CURRENT
template. If possible, I... (5 Replies)
Today I used Terminal (invoked from Mac OS X 10.4.11) to view some data that is secured by a password.
After exiting Terminal, it occurred to me that a vestige of the data displayed on my screen might reside in memory or in disk file ... the actual file used for stdout, for example.
Do I need... (1 Reply)
Discussion started by: dcollins
1 Replies
LEARN ABOUT MOJAVE
vga_flip
vga_flip(3) Svgalib User Manual vga_flip(3)NAME
vga_flip - toggle between text and graphics mode
SYNOPSIS
#include <vga.h>
int vga_flip(void);
DESCRIPTION
switches between graphics and text mode without destroying the screen contents. This makes it possible for your application to use both
text and graphics output.
However, This is an old vgalib function. You should really only use it for debugging as it runs extremely unstable because svgalib now does
its own virtual console management. If you want to perform a similar action, save the current screen contents with ordinary memory copy
operation to the frame buffer or gl_getbox(3), set vga_setmode(TEXT), then call vga_setmode(3) to return to graphics operation and restore
the screen contents with memory or gl_putbox(3).
One could also use vga_drawscansegment(3) and vga_getscansegment(3) calls.
However, avoid any calls to vga_flip() in your applications.
The function always returns 0, a fact on which you shouldn't rely.
It might be useful if you are debugging one of your svgalib applications though. If your program reaches a breakpoint while in graphics
mode, you can switch to text mode with the gdb command
print vga_flip()
and later restore the graphics screen contents with the same command. It is useful to define the following alias in gdb:
define flip <Return> print vga_flip() <Return> end <Return>
SEE ALSO svgalib(7), vgagl(7), libvga.config(5), vga_init(3), vga_setflipchar(3), vga_drawscanline(3), vga_drawscansegment(3), vga_getscanseg-
ment(3), gl_getbox(3), gl_putbox(3)AUTHOR
This manual page was edited by Michael Weller <eowmob@exp-math.uni-essen.de>. The exact source of the referenced function as well as of the
original documentation is unknown.
It is very likely that both are at least to some extent are due to Harm Hanemaayer <H.Hanemaayer@inter.nl.net>.
Occasionally this might be wrong. I hereby asked to be excused by the original author and will happily accept any additions or corrections
to this first version of the svgalib manual.
Svgalib (>= 1.2.11) 27 July 1997 vga_flip(3)