Hi,
How do i know if the files are transferred succesfully when i use SCP to transfer files between 2 servers.
One more is i am trying to send all the files in a single shot by using * to save the connection time. So can i know when the scp breakes in the middle
scp $sourcepath/*... (9 Replies)
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)
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)
FILE_LIST="{a.txt,b.txt,cal*}"
scp -r $..$REMOTE_PATH$FILE_LIST $LOCAL_PATH
This script passes only when all the three files are transfere, wat if only two file are transfered, but still I was to make the return code as pass.
is it possible. (2 Replies)
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)
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)
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)
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)
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
LEARN ABOUT SUSE
net::server::proto::ssl
Net::Server::Proto::SSL(3) User Contributed Perl Documentation Net::Server::Proto::SSL(3)NAME
Net::Server::Proto::SSL - Net::Server SSL protocol.
SYNOPSIS
See Net::Server::Proto.
DESCRIPTION
Experimental. If anybody has any successes or ideas for improvment under SSL, please email <paul@seamons.com>.
Protocol module for Net::Server. This module implements a secure socket layer over tcp (also known as SSL). See Net::Server::Proto.
There is a limit inherent from using IO::Socket::SSL, namely that only one SSL connection can be maintained by Net::Server. However,
Net::Server should also be able to maintain any number of TCP, UDP, or UNIX connections in addition to the one SSL connection.
Additionally, getline support is very limited and writing directly to STDOUT will not work. This is entirely dependent upon the
implementation of IO::Socket::SSL. getline may work but the client is not copied to STDOUT under SSL. It is suggested that clients
sysread and syswrite to the client handle (located in $self->{server}->{client} or passed to the process_request subroutine as the first
argument).
PARAMETERS
In addition to the normal Net::Server parameters, any of the SSL parameters from IO::Socket::SSL may also be specified. See
IO::Socket::SSL for information on setting this up.
BUGS
Christopher A Bongaarts pointed out that if the SSL negotiation is slow then the server won't be accepting for that period of time (because
the locking of accept is around both the socket accept and the SSL negotiation). This means that as it stands now the SSL implementation
is susceptible to DOS attacks. To fix this will require deviding up the accept call a little bit more finely which may not yet be possible
with IO::Socket::SSL. Any ideas or patches on this bug are welcome.
LICENCE
Distributed under the same terms as Net::Server
THANKS
Thanks to Vadim for pointing out the IO::Socket::SSL accept was returning objects blessed into the wrong class.
perl v5.12.1 2007-02-03 Net::Server::Proto::SSL(3)