Originally posted by Perderabo I need to do a lot of automated ftp jobs myself. I have tried several versions of this and have finally settled on a style of script that I like. I found that using a .netrc file to automate the logging-in process kept painting me into a corner because different scripts needed to sign in as different users. So I avoid .netrc and force the script to sign in. I don't like to allocate pty's unless I really am forced into it, so I also avoid pty based tools like expect. I really like ksh so that was my tool of choice. And I like the co-process concept because it makes feeding commands into the ftp process so easy with "print -p". The only problem is that the co-process manipulates standard-out so as to make it available to "read -p". And it's too hard to know how many "read -p" I will need. So I send the output to a different file descriptor. Putting it all together:
That script will tranfer the file and the output of the script will be the output from the ftp job itself. Put the script into cron and save the output so you can look at it the next morning.
Hi:
I tried your script .. somehow it doesnt work with SFTP it still asks for password......
#!/usr/bin/ksh
exec 4>&1
sftp user@host >&4 2>&4 |&
print -p cd outgoing
print -p put test1
wait
exit 0
~
If I wanted a machine to put a specific file onto another OS far across the internet via FTP - and I wanted to do it automatically not user intervented, how would I do that?
Use the PUT command?
The file name and position never changes, it gets overwritten and the system on the other end... (6 Replies)
How can an automated script be setup to run at a later time in the day. cron runs recurring tasks. I am interested in a one time process.
I want to back up a number of files whenever I make changes to an application and ftp for backup purposes. The script to automate the zipping of files has... (1 Reply)
I have seen the script posted yesterday for automated ftp
Can we do some thing like ftp ing multiple files in one script
Example input.txt has all files names to be ftped
input.txt ------
a.tar
b.ccp
c.perl
i need to ftp all the files present in input.txt
i tried something like... (0 Replies)
Hi
I am trying to delete some specific files ( files other than created today) from the server on a cron basis. I wrote a small script, but I am stuck up in how to delete only specific files.
#!/usr/bin/expect -f
set IP
set timeout -1
spawn ftp $IP
expect ):
send "username\n"... (10 Replies)
Automated FTP.
hint : use 'atd' to schedule to run a specific script.
An Env Variable should be created,say CONF_DIR which points to some dir.
@ some time, create a TAR file of this and FTP it to some server. (3 Replies)
I want to do Automated FTP from linux client to LINUX server using a shell script after every one hour. And copies last most updated file from Linux server.
OR
You can say that whenever files get modified on LINUX server so it also copies on my LINUX client.
Linux SERVER path=... (4 Replies)
Hi all,
I'm using the following script to automated ftp files to 1 ftp servers
host=192.168.0.1
/usr/bin/ftp -vi >> $bkplog 2>&1 <<ftp
open $host
bin
cd ${directory}
put $files
quit
ftp
and the .netrc file contain
machine 192.168.0.1
login abc... (4 Replies)
Hello,I just know the basics of scripting & I need a script to automate ftp since I use it quite often.
I use ftp to transfer different kind of files and everytime the source & the destination directories are different for transferring files, so can anyone help me out on this urgently.. (2 Replies)
Discussion started by: mohit_02mar
2 Replies
LEARN ABOUT X11R4
wait
wait(1) User Commands wait(1)NAME
wait - await process completion
SYNOPSIS
/bin/sh
wait [pid...]
/bin/jsh /bin/ksh /usr/xpg4/bin/sh
wait [pid...]
wait [ % jobid...]
/bin/csh
wait
DESCRIPTION
The shell itself executes wait, without creating a new process. If you get the error message cannot fork,too many processes, try using the
wait command to clean up your background processes. If this doesn't help, the system process table is probably full or you have too many
active foreground processes. There is a limit to the number of process IDs associated with your login, and to the number the system can
keep track of.
Not all the processes of a pipeline with three or more stages are children of the shell, and thus cannot be waited for.
/bin/sh, /bin/jsh
Wait for your background process whose process ID is pid and report its termination status. If pid is omitted, all your shell's currently
active background processes are waited for and the return code will be 0. The wait utility accepts a job identifier, when Job Control is
enabled (jsh), and the argument, jobid, is preceded by a percent sign (%).
If pid is not an active process ID, the wait utility will return immediately and the return code will be 0.
csh
Wait for your background processes.
ksh
When an asynchronous list is started by the shell, the process ID of the last command in each element of the asynchronous list becomes
known in the current shell execution environment.
If the wait utility is invoked with no operands, it will wait until all process IDs known to the invoking shell have terminated and exit
with an exit status of 0.
If one or more pid or jobid operands are specified that represent known process IDs (or jobids), the wait utility will wait until all of
them have terminated. If one or more pid or jobid operands are specified that represent unknown process IDs (or jobids), wait will treat
them as if they were known process IDs (or jobids) that exited with exit status 127. The exit status returned by the wait utility will be
the exit status of the process requested by the last pid or jobid operand.
The known process IDs are applicable only for invocations of wait in the current shell execution environment.
OPERANDS
The following operands are supported:
One of the following:
pid The unsigned decimal integer process ID of a command, for which the utility is to wait for the termination.
jobid A job control job ID that identifies a background process group to be waited for. The job control job ID notation is applicable
only for invocations of wait in the current shell execution environment, and only on systems supporting the job control option.
USAGE
On most implementations, wait is a shell built-in. If it is called in a subshell or separate utility execution environment, such as one of
the following,
(wait)
nohup wait ...
find . -exec wait ... ;
it will return immediately because there will be no known process IDs to wait for in those environments.
EXAMPLES
Example 1: Using A Script To Identify The Termination Signal
Although the exact value used when a process is terminated by a signal is unspecified, if it is known that a signal terminated a process, a
script can still reliably figure out which signal is using kill, as shown by the following (/bin/ksh and /usr/xpg4/bin/sh):
sleep 1000&
pid=$!
kill -kill $pid
wait $pid
echo $pid was terminated by a SIG$(kill -l $(($?-128))) signal.
Example 2: Returning The Exit Status Of A Process
If the following sequence of commands is run in less than 31 seconds (/bin/ksh and /usr/xpg4/bin/sh):
sleep 257 | sleep 31 &
jobs -l %%
then either of the following commands will return the exit status of the second sleep in the pipeline:
wait <pid of sleep 31>
wait %%
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of wait: LANG, LC_ALL, LC_CTYPE, LC_MES-
SAGES, and NLSPATH.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), jobs(1), ksh(1), sh(1), attributes(5), environ(5), standards(5)SunOS 5.10 12 Dec 1997 wait(1)