01-13-2010
Save the output of the script into a log file, and examine the log file afterwards.
ftp abc.com <<DO_FTP1 >abc.log
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi there,
I am in the process of writing a shell script to transfer files to a remote directory. Is there a method to determine the success or the failure of the ftp process.
Regards
Jim (4 Replies)
Discussion started by: JimJim
4 Replies
2. Shell Programming and Scripting
hi #!/bin/bash
SERVER=10.89.40.35
USER=xyz
PASSWD=xyz
ftp -in $SERVER<<EOF
user $USER $PASSWD
mkdir PPL
cd /path of remote dir
lcd /path of local dir
hash
bin
put <file name>
bye
<<EOF
The above ftp script i have to schedule in crontab at a particular instance of time run daily.... (2 Replies)
Discussion started by: rookie250
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I tried to do a ftp get process from linux server to a remote system.It was giving an error 'failure writing network systems'.I am trying to ftp two files,one among them is successful and this problem occurs only if i run the code through 'cron' ie,manual run ends successfully.
Would... (0 Replies)
Discussion started by: DILEEP410
0 Replies
4. IP Networking
Hi Guys,
i have this lil challenge;
i am to implement an automated script that searches/scans a directory for files then picks and sends this files to a very remote server via an ftp link.
the challenge here is that the ftp link fails due to netwrk issues maybe;
i therefore need to develop... (5 Replies)
Discussion started by: sdcoms
5 Replies
5. IP Networking
Hi,
I've been searching through out this forum to find the exact message when during the on-going FTP, suddenly the network went down but i cannot find some. Could anyone provide me the exact return codes when FTP failed during FTP or prior to FTP the network went down and you still proceeded to... (3 Replies)
Discussion started by: vibora
3 Replies
6. Shell Programming and Scripting
Hi Gurus
the below FTP code works fine, but the issue is from past 1 week couldn't able to send the files to external system.
#--------------------------------------------------------------------#
#Start the ftp session
#--------------------------------------------------------------------#... (3 Replies)
Discussion started by: SeenuGuddu
3 Replies
7. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
8. Shell Programming and Scripting
I need to read a file line by line, then depending on the contents of each line, type in a code that will get written to an array.
The problem I have is when I ask the user to confirm the input code, if it is wrong, how do i Return to ask again?
Any thing I try increments the file to the next... (6 Replies)
Discussion started by: kcpoole
6 Replies
9. Shell Programming and Scripting
I am using the below code to ftp file onto another server
FTP_LOG_FILE=${CURR_PRG_NAME}- ${FTP_FILE}-`date +%Y%m%d%H%M%S`.log
ftp -ivn ${FTP_HOST} ${FTP_PORT} << ENDFTP >> ${EDI_LOG_DIR}/${FTP_LOG_FILE} 2>&1
user ${FTP_USER} ${FTP_PSWD}
lcd... (2 Replies)
Discussion started by: akashdeepak
2 Replies
10. UNIX for Advanced & Expert Users
Hi,
We have a external vendor (outside firewall), who used to connect our ftp server till 2 days back. I am not able to figure out, what was changed. Now he is not able to login. When I login to ftp server (from inside firewall), I am able to connect with credentials. When that vendor login... (4 Replies)
Discussion started by: solaris_1977
4 Replies
log(8) System Manager's Manual log(8)
NAME
log - Records input and output from a program
SYNOPSIS
/usr/sbin/log <logfile> <command>
OPERANDS
The file in which to record the interaction being logged. The command to execute.
DESCRIPTION
The log program runs <command> and logs the input to and output from <command> to the <logfile> file. Input and output are logged until
<command> exits, the log program exits, and the exit status of <command> is returned.
The log program is used by the system installation procedure and the it(8) command to create the /var/adm/smlogs/install.log and
/var/adm/smlogs/it.log installation log files.
RESTRICTIONS
Because the log program is used in the installation standalone environment, program size was the greatest concern in its implementation.
The log program does not search for the PATH variable to locate <command> and error messages are terse.
The log program causes <command> to take standard input from and write standard output and standard error to UNIX pipes. Some commands
will not be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead. UNIX shells will
not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells). For example, log
foo.tmp /sbin/sh -i
In the previous example, foo.tmp is the name of <logfile>.
The log program intercepts end-of-file (usually Ctrl/d). Therefore programs which normally receive end-of-file as an exit command must
exit by some other means.
ERRORS
Log open error
Explanation:
The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly.
Exec Error
Explanation:
The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and that <command> is an exe-
cutable file.
Fork Error
Explanation:
The log program was unable to create one of the processes it requires to log data.
SEE ALSO
Commands: it(8), script(1)
log(8)