03-31-2007
It didn't work because you didn't copy it correctly.
Look at where I have spaces in my post and what you have.
exec 4>&1 5>&2
duplicates the output streams 4 and 5 to stdout and stderr.
10 More Discussions You Might Find Interesting
1. OS X (Apple)
Hey guys, does anyone know how I edit, configure the server settings using the terminal? MySQL and PHP was once working.
But after frying the Xserve G5 i'm in the middle of rebuilding everything, I believe i need to re-configure the root document directory...
but have forgotten how to edit... (1 Reply)
Discussion started by: hype.it
1 Replies
2. SuSE
Hello All,
I need some help as to how to debug the problem I am having with my webserver. I am using Suse 9.2 pro as my server. I have setup my firewall and router to forward http 80 request to my linux server.
I tried pinging my server from work - it worked.
I tried running localhost... (5 Replies)
Discussion started by: negixx
5 Replies
3. UNIX for Advanced & Expert Users
Can I set up an apache webserver on Mandriva? Looking for the easiest webserver program to install basic webserver just for home use. Any ideas/suggestions much appreciated..... (2 Replies)
Discussion started by: jo calamine
2 Replies
4. Solaris
how can I get statistics and web analysis for solaris 10 webserver access? what is the file? and what is the tools to analyze it?
thanx (2 Replies)
Discussion started by: fsmadi
2 Replies
5. Shell Programming and Scripting
Somewhat long story:
I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage.
This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
Discussion started by: jondo
1 Replies
6. UNIX for Advanced & Expert Users
Hi all,
This is my server configuration.
Hard Disk - 500 GB
RAM - 3GB
Processor - intel core 2 quad ( 4 numbers). each one of four cores.
We have an application hosted thorough tomcat and accessed via apache through mod_jk connector.
There would be around 200 clients... (1 Reply)
Discussion started by: anishkumarv
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I was writing one script which includes to switch to the another telnet automatically from the present telnet server. I was using rlogin but firstly it takes the same user name of the present telnet and secondly it is prompting for the password.
But i want to switch to the another telnet... (2 Replies)
Discussion started by: Prateek
2 Replies
8. Shell Programming and Scripting
Hello All
I want to develop a news ticker using a PHP webserver instead of polling the RSS feed using AJAX.
Let me know if you guys have any idea about this. (0 Replies)
Discussion started by: suvendu4urs
0 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I want to know the difference between these two services. Both are under xinetd. Both are used for enabling and disabling Telnet service. So, can somebody please explain me the difference between the two ?
Thanks in advance :) (0 Replies)
Discussion started by: kashifsd17
0 Replies
10. Emergency UNIX and Linux Support
Dear Linux guru's
I am trying to create a webserver using nc (netcat only) on RHEL 7.2 running on bash shell.
now the easy thing is to get nc listing to a port and respond back
$ while true; do { echo -e 'HTTP/1.0 200 OK\r\n'; set; } | nc -l 7877; done
This when called from a... (3 Replies)
Discussion started by: chakrapani
3 Replies
LEARN ABOUT REDHAT
stderr
STDIN(3) BSD Library Functions Manual STDIN(3)
NAME
stdin, stdout, stderr -- standard I/O streams
SYNOPSIS
#include <stdio.h>
extern FILE *stdin;
extern FILE *stdout;
extern FILE *stderr;
DESCRIPTION
Under normal circumstances every Unix program has three streams opened for it when it starts up, one for input, one for output, and one for
printing diagnostic or error messages. These are typically attached to the user's terminal (see tty(4)) but might instead refer to files or
other devices, depending on what the parent process chose to set up. (See also the ``Redirection'' section of sh(1) .)
The input stream is referred to as ``standard input''; the output stream is referred to as ``standard output''; and the error stream is
referred to as ``standard error''. These terms are abbreviated to form the symbols used to refer to these files, namely stdin, stdout, and
stderr.
Each of these symbols is a stdio(3) macro of type pointer to FILE, and can be used with functions like fprintf(3) or fread(3).
Since FILEs are a buffering wrapper around Unix file descriptors, the same underlying files may also be accessed using the raw Unix file
interface, that is, the functions like read(2) and lseek(2). The integer file descriptors associated with the streams stdin, stdout, and
stderr are 0, 1, and 2, respectively. The preprocessor symbols STDIN_FILENO, STDOUT_FILENO, and STDERR_FILENO are defined with these values
in <unistd.h>.
Note that mixing use of FILEs and raw file descriptors can produce unexpected results and should generally be avoided. (For the masochistic
among you: POSIX.1, section 8.2.3, describes in detail how this interaction is supposed to work.) A general rule is that file descriptors
are handled in the kernel, while stdio is just a library. This means for example, that after an exec, the child inherits all open file
descriptors, but all old streams have become inaccessible.
Since the symbols stdin, stdout, and stderr are specified to be macros, assigning to them is non-portable. The standard streams can be made
to refer to different files with help of the library function freopen(3), specially introduced to make it possible to reassign stdin, stdout,
and stderr. The standard streams are closed by a call to exit(3) and by normal program termination.
SEE ALSO
sh(1), csh(1), open(2), fopen(3), stdio(3)
CONSIDERATIONS
The stream stderr is unbuffered. The stream stdout is line-buffered when it points to a terminal. Partial lines will not appear until
fflush(3) or exit(3) is called, or a newline is printed. This can produce unexpected results, especially with debugging output. The buffer-
ing mode of the standard streams (or any other stream) can be changed using the setbuf(3) or setvbuf(3) call. Note that in case stdin is
associated with a terminal, there may also be input buffering in the terminal driver, entirely unrelated to stdio buffering. (Indeed, nor-
mally terminal input is line buffered in the kernel.) This kernel input handling can be modified using calls like tcsetattr(3); see also
stty(1), and termios(3).
CONFORMING TO
The stdin, stdout, and stderr macros conform to ANSI X3.159-1989 (``ANSI C89''), and this standard also stipulates that these three streams
shall be open at program startup.
Linux 2.0 March 24, 1998 Linux 2.0