Console redirect to xmanager in AIX ?

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to redirect the messages from the script to console in Linux?

msg.sh #!/bin/bash if then echo "starting service" else echo " service not started" echo " Please check the start.sh file or manuly start the service" fi if i login with root credentials @12.36.34.123 with passwd username:root passwd:abc once i login into linux pc...

2. Shell Programming and Scripting

Redirect an output from a script to a file and display it at a console simultaneously

Hi, I'd like to redirect the STDOUT output from my script to a file and simultaneously display it at a console. I've tried this command: myscript.sh | tail -f However, it doesn't end after the script finishes running I've also tried this: myscript.sh | tee ~/results.txt But it writes...

3. Shell Programming and Scripting

How to redirect the output of a cvs command to a file as well as the console.

Hi can anyone tell me how to redirect the ouput of a cvs command to a file as well as the console? i tried using cvs add <filename> | tee logFile cvs add <filename> 2>logFile 2>&1 All i could get is only on console or on file. Please help Thanks

4. Solaris

Command to redirect console to my tty?

Is there a utility built into Solaris that will allow me to see console messages from a tty? I've done a search and see that this is possible through software like ILOM, but I'm looking for a method to do this with built in utilities. For example, on AIX, I can use swcons `tty`

5. Shell Programming and Scripting

How to redirect the output to multiple files without putting on console

How to redirect the output to multiple files without putting on console I tried tee but it writes to STDOUT , which I do not want. Test.sh ------------------ #!/bin/ksh echo "Hello " tee -a file1 file2 ---------------------------- $>./Test.sh $> Expected output: -------------------...

6. AIX

177 port is up but xmanager is not working in AIX 6.1

Dear Friends, Recently we have to use AIX 6.1 IBM unix server . Here the 177 port is up and also inetd service is up . But we cannot access to the server using X-manager software . server's output : bash-3.00# netstat -nat | grep 177 udp4 0 0 *.177 *.* We have another server AIX-5.3 ....

7. Solaris

console redirect on dl365

anyone have any success with redirecting the console running sol10 x86 on a hp dl365?

8. Shell Programming and Scripting

console redirect of progress bar

I'm trying to write a python wrapper around wget to show the progress bar on a gui application. Wget gives you a progress bar on command line, but how would I pipe that to some "tty" that's really just a variable I read, or am I going about it all wrong? When I try to just redirect the output to a...

9. AIX

Unable to connect to AIX server through xmanager

Hi, I have xmanager installed on my windows PC. But I am not able to connect to AIX server. It's giving the error as follows: The X11 forwarding request was rejected. Graphics mode is not coming up in AIX server. Please help as I have to install oracle patchset urgently.

10. UNIX for Dummies Questions & Answers

AIX Console screens

How do you switch screens in AIX? I know you can use ALT-F1, ALT-F3, etc. in SCO Unix. Help!!!

LEARN ABOUT DEBIAN

tap::formatter::base

TAP::Formatter::Base(3pm)				User Contributed Perl Documentation				 TAP::Formatter::Base(3pm)

NAME

       TAP::Formatter::Base - Base class for harness output delegates

VERSION

       Version 3.25

DESCRIPTION

       This provides console orientated output formatting for TAP::Harness.

SYNOPSIS

	use TAP::Formatter::Console;
	my $harness = TAP::Formatter::Console->new( \%args );

METHODS

   Class Methods
       "new"

	my %args = (
	   verbose => 1,
	)
	my $harness = TAP::Formatter::Console->new( \%args );

       The constructor returns a new "TAP::Formatter::Console" object. If a TAP::Harness is created with no "formatter" a
       "TAP::Formatter::Console" is automatically created. If any of the following options were given to TAP::Harness->new they well be passed to
       this constructor which accepts an optional hashref whose allowed keys are:

       o   "verbosity"

	   Set the verbosity level.

       o   "verbose"

	   Printing individual test results to STDOUT.

       o   "timer"

	   Append run time for each test to output. Uses Time::HiRes if available.

       o   "failures"

	   Show test failures (this is a no-op if "verbose" is selected).

       o   "comments"

	   Show test comments (this is a no-op if "verbose" is selected).

       o   "quiet"

	   Suppressing some test output (mostly failures while tests are running).

       o   "really_quiet"

	   Suppressing everything but the tests summary.

       o   "silent"

	   Suppressing all output.

       o   "errors"

	   If parse errors are found in the TAP output, a note of this will be made in the summary report.  To see all of the parse errors, set
	   this argument to true:

	     errors => 1

       o   "directives"

	   If set to a true value, only test results with directives will be displayed.  This overrides other settings such as "verbose",
	   "failures", or "comments".

       o   "stdout"

	   A filehandle for catching standard output.

       o   "color"

	   If defined specifies whether color output is desired. If "color" is not defined it will default to color output if color support is
	   available on the current platform and output is not being redirected.

       o   "jobs"

	   The number of concurrent jobs this formatter will handle.

       o   "show_count"

	   Boolean value.  If false, disables the "X/Y" test count which shows up while tests are running.

       Any keys for which the value is "undef" will be ignored.

       "prepare"

       Called by Test::Harness before any test output is generated.

       This is an advisory and may not be called in the case where tests are being supplied to Test::Harness by an iterator.

       "open_test"

       Called to create a new test session. A test session looks like this:

	   my $session = $formatter->open_test( $test, $parser );
	   while ( defined( my $result = $parser->next ) ) {
	       $session->result($result);
	       exit 1 if $result->is_bailout;
	   }
	   $session->close_test;

       "summary"

	 $harness->summary( $aggregate );

       "summary" prints the summary report after all tests are run. The first argument is an aggregate to summarise. An optional second argument
       may be set to a true value to indicate that the summary is being output as a result of an interrupted test run.

perl v5.14.2							    2012-06-05						 TAP::Formatter::Base(3pm)

AIX