11-17-2014
prints "couldn't connect" into file descriptor two, i.e. standard error, the traditional place for human readable error messages.
When you run something in a terminal it traditionally gets two independent connections to the terminal, stdout and stderr. stdout is meant for data, so that if you do command | anothercommand | etc they won't be piping their own error messages into each other, but dumping them direct to the screen for you to read.
This User Gave Thanks to Corona688 For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am trying to ftp some files from a certain directory, but i got an invalid command. does anybody know why i got this error?
ftp -v -i -n <<SCRIPT
open servername
user
username password
cd /server/logs
for file in MCWAS*
do
put ${file} /home/test/${file}
done
bye
SCRIPT (2 Replies)
Discussion started by: caesarkim
2 Replies
2. Shell Programming and Scripting
Hi,
I have to ftp to a remote machine.
i have got the Ip, username and password and the file path..
I need to get the file name with out user intervention in my script..
is there any way to do this..
please help
esham (2 Replies)
Discussion started by: esham
2 Replies
3. UNIX for Dummies Questions & Answers
Hi ,,
I am wrting a shell script to ftp a file from remote server but its giving some problem to me.can you help me in debugging this.
#!/usr/bin/ksh
HOST="some ip"
user="user_name"
passwd="password"
ftp -n $HOST >>END_SCRIPT
USER $user
$passwd
binary
prompt
get... (3 Replies)
Discussion started by: namishtiwari
3 Replies
4. Shell Programming and Scripting
Hi,
I need to upload a file via ftp. I have given :
ftp -n $HOST <<END
quote user $USER
quote pass $PASSWD
prompt off
put bus.txt
quit
END
Its throwing a syntax error at "<<" symbol. What should be done for this ?? (2 Replies)
Discussion started by: risshanth
2 Replies
5. Shell Programming and Scripting
Can I ftp to put file with shell script(as bath file) ?
Plz give the simple code to do that.
My script look like that
#!/bin/sh
echo "Start ftp"
ftp temphost <<EOF
put file
quit
EOF
# end
This code ignore username & password but I need to input.
How to input username &... (8 Replies)
Discussion started by: aungomarin
8 Replies
6. UNIX for Advanced & Expert Users
HI ALL
i am writing a shell script in which i have to use FTP command like.
FTP <ip address>
cd xyz
mget*
bye
but i am not able to perform any command from shell script.
once the control goes to FTP, i again have to type all the things.
i just want my shell script to take care of the... (8 Replies)
Discussion started by: infyanurag
8 Replies
7. Shell Programming and Scripting
#!/usr/bin/ksh
export filename=/grid/PowerCenter/inbound/AT/filelist.txt
export SOURCE_DIR=/grid/PowerCenter/inbound/AT
export ICOMS_FTP_TGT_DIR1=/dw/input/ATU/ICOM_SERV1
export ICOMS_FTP_TGT_DIR2=/dw/input/AT/ICOM_SERV2
export FILE_MASK="ATRPU_RP_ATU"
echo "start"
ftp_data_file()
{
... (15 Replies)
Discussion started by: vsmeruga
15 Replies
8. Shell Programming and Scripting
I am running the following on linux (on a mac):
filename="/Users/thisfilename.txt"
hostname="ftp.mysite.com"
username="myusername"
password="mypassword"
echo '=======FTP========'
ftp -un $hostname <<EOF
quote USER $username
quote PASS $password
binary
put $filename
quit
EOF
I... (4 Replies)
Discussion started by: globalnerds
4 Replies
9. Shell Programming and Scripting
So i Administer multiple ftp servers that run on dynamic IP's as well as user and password settings are changed by other people constantly. What i need to do is ensure that an FTP is server is up on the IP i check. As well as the login credentials work.
Here is a simple script i wrote. However... (2 Replies)
Discussion started by: Noledge
2 Replies
10. UNIX for Dummies Questions & Answers
Dear All,
I am using FTP in a script. But when i exit from the FTP session, the commands written after EOF don't get executed.
i.e.
ftp <<EOF
quote $login
quote $password
cd /tmp
mget *somefile*
bye
EOF
echo $some_variable
#This last echo command or whatever piece of commands i... (10 Replies)
Discussion started by: Salman786
10 Replies
STDIN(3) Linux Programmer's 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).
On program startup, 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>. (Applying freopen(3) to
one of these streams can change the file descriptor number associated with the stream.)
Note that mixing use of FILEs and raw file descriptors can produce unexpected results and should generally be avoided. (For the masochis-
tic among you: POSIX.1, section 8.2.3, describes in detail how this interaction is supposed to work.) A general rule is that file descrip-
tors are handled in the kernel, while stdio is just a library. This means for example, that after an exec(3), 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 nonportable. 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, std-
out, and stderr. The standard streams are closed by a call to exit(3) and by normal program termination.
CONFORMING TO
The stdin, stdout, and stderr macros conform to C89 and this standard also stipulates that these three streams shall be open at program
startup.
NOTES
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
buffering 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, normally terminal input is line buffered in the kernel.) This kernel input handling can be modified using calls like tcse-
tattr(3); see also stty(1), and termios(3).
SEE ALSO
csh(1), sh(1), open(2), fopen(3), stdio(3)
COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2008-07-14 STDIN(3)