04-14-2008
Quote:
Originally Posted by
vijaykrc
Thank you for the help...
I may be moving around 5000 files and i cannot tar them... i need to send individually...
I am benefiting around 3 hrs if i send then at a time using the * and if i send then individually its taking that 3-4 hrs more for the 5000 files.
The way I would approach this if the contents of the source directory were likely to change while the copy process is running is to create a shell function to copy one individual file and then to delete it if the copy was successful. I would then start the process by creating a list of all the current files, passing them one by one to the function. This will ensure that only files that were copied correctly get deleted. I know that this will take extra time and resources as each individual file will require a new connection to be set up, but it is, in my opinion the safest way. Of course you will need to set up key authorisation rather than password auth as that would be tedious in the extreme for 5000 files.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I need to transfer multiple files using SCP between two solaris machines. Can somebody explain how to achieve that ? (3 Replies)
Discussion started by: parthum
3 Replies
2. Shell Programming and Scripting
Hi Frdz
I have a problem like.
I need to transfer a file from source to destination (different systems with different IPs) using "scp" command and before transfer the file i have to check the file is available in destination or not, if it is there no need to transfer, otherwise we have to... (5 Replies)
Discussion started by: KiranKumarKarre
5 Replies
3. UNIX for Dummies Questions & Answers
I have a shell script which uses SCP command to transfer the files from one server to another server. The files are getting transferred successfully, but the problem is the files transferred to the destination server didnot have the permissions as that of the files on the source server.
Command... (5 Replies)
Discussion started by: kumarm
5 Replies
4. UNIX for Advanced & Expert Users
I am not able to throw a file from server173 to server067
i.e.
wlsuser@server173> scp /tmp/harsha.txt wlsuser@server067:/tmp
fails
However, I am able to pull a file from server173 onto server067's /tmp dir
wlsuser@server067> scp wlsuser@server173:/tmp/harsha.txt /tmp... (2 Replies)
Discussion started by: shifahim
2 Replies
5. UNIX for Advanced & Expert Users
Whenever I transfer file through SCP between two server it gives below given message.....Is there a way to avoid it....
Target server : newyork
$ scp ABC27801.iue newyork:./iABC/x0017801.iue
Message
=====
This system is for the use of authorized users only. Individuals using this... (1 Reply)
Discussion started by: Pash
1 Replies
6. UNIX for Advanced & Expert Users
I have 3 AIX server namely - Server 1 , Server 2 and Server 3.
And have done SCP setup between Server 1 and Server 2 so that i dont have to give password when i transfer file from Server 1 to Server 2 by setting public key between the server.
Q1. If the unix password of the target server... (3 Replies)
Discussion started by: Pash
3 Replies
7. UNIX for Advanced & Expert Users
On unix AIX server, when I am trying to transfer file from one directory to another directory on the same server through a program(where i call the script) it gives error "Lost Connection". (5 Replies)
Discussion started by: Pash
5 Replies
8. AIX
I am testing the following command to transfer a file from my server (AIX 5.2) to another server. I was able to generate the keys and sent them the public key.
scp -v -P 4030 /home/lawson/.ssh/jimtest.txt someuser@some.ftpsite.net:/Inbound/jimtest.txt > jimtest_out.txt 2>&1
Based on... (3 Replies)
Discussion started by: jyoung
3 Replies
9. Shell Programming and Scripting
I am trying to transfer a zip file of around 30 MB in my automation script using scp from system A to B.
When I manually do scp, file is complete transferred but when automation shell script runs it, zip file is not completely transferred.
Stack Trace while doing manual :
Executing:... (1 Reply)
Discussion started by: Shaishav Shah
1 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
Need some help regarding file transfer between server.
Suppose we have system-A and system-B. To transfer file from system-A to system-B we usually share the
public keys of system-A to system-B and do scp/sftp to transfer a file.
Is it possible that public key of system-B can be... (3 Replies)
Discussion started by: abhi_123
3 Replies
LEARN ABOUT DEBIAN
clientupdate
CLIENTUPDATE(1) General Commands Manual CLIENTUPDATE(1)
NAME
clientupdate - Xymon client update utility
SYNOPSIS
clientupdate [options]
DESCRIPTION
clientupdate is part of the Xymon client. It is responsible for updating an existing client installation from a central repository of
client packages stored on the Xymon server.
When the Xymon client sends a normal client report to the Xymon server, the server responds with the section of the client-local.cfg(5)
file that is relevant to this client. Included in this may be a "clientversion" value. The clientversion received from the server is com-
pared against the current clientversion installed on the client, as determined by the contents of the $BBHOME/etc/clientversion.cfg file.
If the two versions are not identical, clientupdate is launched to update the client installation.
OPTIONS
--level
Report the current clientversion.
--update=NEWVERSION
Attempt to update the client to NEWVERSION by fetching this version of the client software from the Xymon server.
--reexec
Used internally during the update process, see OPERATION below.
--remove-self
Used internally during the update process. This option causes the running clientupdate utility to delete itself - it is used during
the update to purge a temporary copy of the clientupdate utility that is installed in $BBTMP.
USING CLIENTUPDATE IN HOBBIT
To manage updating clients without having to logon to each server, you can use the clientupdate utility. This is how you setup the release
of a new client version.
Create the new client
Setup the new client $BBHOME directory, e.g. by copying an existing client installation to an empty directory and modifying it for
your needs. It is a good idea to delete all files in the tmp/ and logs/ directories, since there is no need to copy these over to
all of the clients. Pay attention to the etc/ files, and make sure that they are suitable for the systems where you want to deploy
this new client. You can add files - e.g. extension scripts in the ext/ directory - but the clientupdate utility cannot delete or
rename files.
Package the client
When your new client software is ready, create a tar-file of the new client. All files in the tar archive must have filenames rela-
tive to the clients' $BBHOME (usually, ~xymon/client/). Save the tarfile on the Xymon server in ~xymon/server/download/some-
file.tar. Dont compress it. It is recommended that you use some sort of operating-system and version-numbering scheme for the
filename, but you can choose whatever filename suits you - the only requirement is that it must end with ".tar". The part of the
filename preceding ".tar" is what Xymon will use as the "clientversion" ID.
Configure which hosts receive the new client
In the client-local.cfg(5) file, you must now setup a clientversion:ID line where the ID matches the filename you used for the tar-
file. So if you have packaged the new client into the file linux.v2.tar, then the corresponding entry in client-local.cfg would be
clientversion:linux.v2.
Wait for hobbitd to reload client-local.cfg
hobbitd will automatically reload the client-local.cfg file after at most 10 minutes. If you want to force an immediate reload, send
a SIGHUP signal to the hobbitd process.
Wait for the client to update
The next time the client contacts the Xymon server to send the client data, it will notice the new clientversion setting in client-
local.cfg, and will run clientupdate to install the new client software. So when the client runs the next time, it will use the new
client software.
OPERATION
clientupdate runs in two steps:
Re-exec step
The first step is when clientupdate is first invoked from the hobbitclient.sh script with the "--re-exec" option. This step copies
the clientupdate program from $BBHOME/bin/ to a temporary file in the $BBTMP directory. This is to avoid conflicts when the update
procedure installs a new version of the clientupdate utility itself. Upon completion of this step, the clientupdate utility automat-
ically launches the next step by running the program from the file in $BBTMP.
Update step
The second step downloads the new client software from the Xymon server. The new software must be packed into a tar file, which
clientupdate then unpacks into the $BBHOME directory.
ENVIRONMENT VARIABLES
clientupdate uses several of the standard Xymon environment variables, including BBHOME and BBTMP.
SEE ALSO
xymon(7), bb(1), client-local.cfg(5)
Xymon Version 4.2.3: 4 Feb 2009 CLIENTUPDATE(1)