10-31-2008
from wikipedia "On POSIX-compliant platforms, SIGTTOU is the signal thrown by computer programs that attempt to write to the tty while in the background"
which suggests that your client is asking for information, or is trying to give you information. Are there any silent mode switches to make it not try and print to the screen, or have you tried redirecting stdin and stderr?
and does it work without trouble when run in the foreground (and without writing to stdin or stderr)
10 More Discussions You Might Find Interesting
1. Programming
consider the given prg.
main() {
.....
function1(); /* to write into a file or log */
printf(" ");
.....
}
when the control reaches function1(), it should get executed in the
background.At the same time main's printf(" ") statement should also get executed.i.e... (5 Replies)
Discussion started by: bankpro
5 Replies
2. Shell Programming and Scripting
How can I run a shell in the background?
cat test.sh
#!/bin/sh
sleep 600
Thank u very much indeed! (2 Replies)
Discussion started by: GCTEII
2 Replies
3. Shell Programming and Scripting
Hi all,
I have a script like:
echo Please input list file name:
read listn
for file in `cat $listn.txt`
do
send_file $file
done
normally, I will run the script like:
:. resendfile
Please input list filename:
list1
#Then, the script will resend all file from the list1. However,... (4 Replies)
Discussion started by: happyv
4 Replies
4. Programming
Hi,
in my program i need to run an external program in background.I am aware that there are at least 2 alternatives for this:
1)fork+exec
2)system("program &");
I have read several posts about this,and they all tend to suggest to use fork+exec (and that's what i am doing now).
I have some... (2 Replies)
Discussion started by: Zipi
2 Replies
5. Shell Programming and Scripting
Looking for a logic where say i have a script called parent_script which is used to call other 4 to 5 child scripts in background as..
cat parent_script # containing 65 lines
1
2
..
35 while read child_script
36 do
37 ./child_script_name&
38 done< ${SCRIPT_LISTS}
39
40 # Need to have... (2 Replies)
Discussion started by: michaelrozar17
2 Replies
6. Shell Programming and Scripting
I am trying to create a service to always run and monitor a script that has a tendency to hang, we could not find what is causing it to hang so are in the process of completely reprogramming just about everything, however, that will take upto 6 months.
So I need to create this to monitor the... (5 Replies)
Discussion started by: ukndoit
5 Replies
7. Shell Programming and Scripting
Hello everybody,
I'm making a script for running a .bat process on wineconsole, but I want that wineconsole doesn't show up when I call it from the script.
The script is named "reset" and it looks like this:
When I execute it, it will show up the wineconsole window on top, and that is... (3 Replies)
Discussion started by: taurokpo
3 Replies
8. Shell Programming and Scripting
Hi All,
i'm a newbie here, i'm just wondering in how do i run my script in background then echo it if it's done.
Please advise,
Thanks,
-nik (1 Reply)
Discussion started by: nikki1200
1 Replies
9. Shell Programming and Scripting
Hii Friends,
I am using Perl CGI. I am running A SCP Command via Perl CGI in Background. Like
system("scp -r machinename:/PathOfFile/ /Path/WhereToCopyIt/ &)
This Copy Process takes some times lets say 15 min.
Now I want When This copy process gets complete then send me... (5 Replies)
Discussion started by: Navrattan Bansa
5 Replies
10. Shell Programming and Scripting
Hello all,
Can someone help with one script?
I have as example 3 scripts
1.sh
sleep 60 &
sleep 60 &
sleep 10 &
sleep 80 &
sleep 60 &
2.sh
sleep 40 &
sleep 5 &
sleep 10 &
sleep 70 &
sleep 60 &
3.sh (2 Replies)
Discussion started by: vikus
2 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