Data transfer in Linux

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Data transfer in Linux
Prev   Next
# 8  
Old 07-01-2015
can you please suggest for both?
 
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Red Hat

Data transfer Time calculation

1 TB of data needs to read through 4 I/O channesl, each channels supports - 100 MB/s, What is average time taken to read the data ? Please give the formula for my understanding (2 Replies)
Discussion started by: Srini.rk1983
2 Replies

2. Windows & DOS: Issues & Discussions

DEC 2000 Data Transfer to PC

Hello - My first post here. I did some looking around; wasn't sure where to jump in or if something like this has been covered. I have a DEC 2000 Alpha that was turned off probably 6 years ago once I had made the transition of programs and most files to the desktop PC. I have the idea... (4 Replies)
Discussion started by: KSchrader
4 Replies

3. UNIX for Dummies Questions & Answers

Data transfer to excel

i have two excel sheets with cpu uasge and memory usage in the follwing format: sheet 1: 22,33 sheet 2: 55,66 i need to display in the below format: servername cpu mem ser1 22 33 ser2 55 66 am using UNIX os. can anyone help me... (2 Replies)
Discussion started by: arunmanas
2 Replies

4. Solaris

Data Transfer

We have a data on the disk that was copied from HP N4000 running HPUX 11.11 and it was created with vxfs version 4. We need to transfer this data to Sun server, how might this be done? (2 Replies)
Discussion started by: Kjons76
2 Replies

5. UNIX for Dummies Questions & Answers

Transfer data from one file to another

Hi, I'm relatively new to shell scripting, Ive worked on a few basic scripts and used most of the unix commands in the simplest of situations. But I am now faced with a task that's seems to be beyond me. I have a file with some data in the form of rows and columns : 123 4536 abcd4 677 bbb... (1 Reply)
Discussion started by: inquisitive101
1 Replies

6. SCO

data transfer from serial port

dear sir, pls. can you help me ? , my os is unix sco 5.0.4 and ,server dat derive (1,4gb) not working, now i want to transfer my server data in other machine (unix/other possible) by serial port/other port comminication. thanks pankaj raval (2 Replies)
Discussion started by: pankajbraval
2 Replies

7. AIX

FTP - Data Transfer Limitations.

Hi, I have to transfer data from our production site to DR site(another city). I am using FTP for transfering data. But I am unable to get the same data transfer rate on AIX machines, one I am geting on windows machines. I want to know, is there any constraint on data transfer using FTP on AIX... (2 Replies)
Discussion started by: system-admin
2 Replies

8. UNIX for Advanced & Expert Users

data corruption with ftp transfer

Hi again, first of all thanks for you help on my last problem, the problem is solved now. But I have many problem :) This time, I transfered a big file, ~3,5 GByte, with ftp from a Sun machine to a linux box, RedHat 7.3. But the file recieved on the Linux Box is corrupt, with smaller files... (12 Replies)
Discussion started by: malcom
12 Replies

9. UNIX for Dummies Questions & Answers

How much data will transfer at 100 full

I am trying to determing how long it will take to transfer 384 Gb of data across a 100 Mb full ethernet. If I am correct, I come up with 36 Gb per hour. Surely that is not correct. I assumed 100 megabit per second is 10 megabyte per second, which is 600 megabytes per minute and 36 GB per hour.... (3 Replies)
Discussion started by: 98_1LE
3 Replies
Login or Register to Ask a Question
transfer::copy(n)					     Data transfer facilities						 transfer::copy(n)

__________________________________________________________________________________________________________________________________________________

NAME
transfer::copy - Data transfer foundation SYNOPSIS
package require Tcl 8.4 package require transfer::copy ?0.2? transfer::copy::do chan|string data outchannel ?options...? transfer::copy::chan channel outchannel ?options...? transfer::copy::string string outchannel ?options...? transfer::copy::doChan channel outchannel optvar transfer::copy::doString string outchannel optvar transfer::copy::options outchannel optionlist optvar _________________________________________________________________ DESCRIPTION
This package provides a number of commands for the asynchronous of information contained in either a string or channel. The main point of this package is that the commands here provide a nicer callback API than the builtin command fcopy, making the use of these facilities sim- pler than the builtin. API
transfer::copy::do chan|string data outchannel ?options...? This command transfers the information in data to the outchannel, according to the options. The type of the information in data is determined by the first argument. The options available to this command are the same as are available to the command transfer::copy::options, and explained there. chan The argument data contains the handle of a channel and the actual infomration to transfer is read from that channel. string The argument data contains a string and this is the information to be transfered. transfer::copy::chan channel outchannel ?options...? This command is a shorter and more direct form for the command transfer::copy::do chan. transfer::copy::string string outchannel ?options...? This command is a shorter and more direct form for the command transfer::copy::do string. transfer::copy::doChan channel outchannel optvar This command is an alternate form of transfer::copy::chan which reads its options out of the array variable named by optvar instead of from a variable length argument list. transfer::copy::doString string outchannel optvar This command is an alternate form of transfer::copy::string which reads its options out of the array variable named by optvar instead of from a variable length argument list. transfer::copy::options outchannel optionlist optvar This command is the option processor used by all the commands above which read their options from a variable length argument list. It first reads default settings from the channel handle outchannel, then processes the list of options in optionlist, at last stores the results in the array variable named by optvar. The contents of that variable are in a format which is directly understood by all the commands above which read their options out of an array variable. The recognized options are: -blocksize int This option specifies the size of the chunks to transfer in one operation. It is optional and defaults to the value of -buffersize as configured for the output channel. If specified its value has to be an integer number greater than zero. -command commandprefix This option specifies the completion callback of the operation. This option has to be specified. An error will be thrown if it is not, or if the empty list was specified as argument to it. Its value has to be a command prefix, i.e. a list whose first word is the command to execute, followed by words containing fixed arguments. When the callback is invoked one or two additional arguments are appended to the prefix. The first argument is the number of bytes which were transfered. The optional second argument is an error message and added if and only if an error occured during the the transfer. -progress commandprefix This option specifies the progress callback of the operation. It is optional and defaults to the empty list. This last possi- bility signals that no feedback was asked for and disabled it. Its value has to be a command prefix, see above, -command for a more detailed explanation. When the callback is invoked a single additional arguments is appended to the prefix. This argument is the number of bytes which were transfered so far. -size int This option specifies the number of bytes to read from the input data and transfer. It is optional and defaults to "Transfer everything". Its value has to be an integer number and any value less than zero has the same meaning, i.e. to transfer all available data. Any other value is the amount of bytes to transfer. All transfer commands will throw error an when their user tries to transfer more data than is available in the input. This happens immediately, before the transfer is actually started, should the input be a string. Otherwise the, i.e. for a channel as input, the error is thrown the moment the underflow condition is actually detected. -encoding encodingname -eofchar eofspec -translation transspec These options are the same as are recognized by the builtin command fconfigure and provide the settings for the output chan- nel which are to be active during the transfer, and only then. I.e. the settings of the output channel before the transfer are saved, and restored at the end of a transfer, regardless of its success or failure. None of these options are required, and they default to the settings of the output channel if not specified. BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category transfer of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. KEYWORDS
channel, copy, transfer COPYRIGHT
Copyright (c) 2006 Andreas Kupries <andreas_kupries@users.sourceforge.net> transfer 0.2 transfer::copy(n)