Sponsored Content
Operating Systems Solaris Atached storage to v890 --- very slow Post 302293842 by bluetooth on Wednesday 4th of March 2009 01:56:09 AM
Old 03-04-2009
The hdd was perfectly right, again I transferred all data from spare pool hdd to its original hdd. But the transfer from internal V890's hdd to JBOD's hdd is taking 5.81 minute for 1 GB. I have tried to find the speed details on JBOD but I couldn't.
 

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

atached file mail

How atached file mail to user for exemplo file with gzip xxx.gz? ex: shell script: mailx -s "TEST SHELL" manoeldba@yahoo.com < $file <send content file> how send file xxx.gz to user? (2 Replies)
Discussion started by: manoelmarcos
2 Replies

2. Solaris

Disks atached to a Symbios 53C875, canīt see them.

Hi, I have SUN E450 box with Solaris 8 and a few internal disks, but i can only see the disks attached to one of the SCSI controlers. I think i canīt see the disks atached to two Symbios 53C875 SCSI controlers that apears in prtdiag output. Could be drivers? How can obtain those drivers to... (2 Replies)
Discussion started by: spacewalker
2 Replies
CURLOPT_PROGRESSFUNCTION(3)				     curl_easy_setopt options				       CURLOPT_PROGRESSFUNCTION(3)

NAME
CURLOPT_PROGRESSFUNCTION - callback to progress meter function SYNOPSIS
#include <curl/curl.h> int progress_callback(void *clientp, double dltotal, double dlnow, double ultotal, double ulnow); CURLcode curl_easy_setopt(CURL *handle, CURLOPT_PROGRESSFUNCTION, progress_callback); DESCRIPTION
Pass a pointer to your callback function, which should match the prototype shown above. We encourage users to use the newer CURLOPT_XFERINFOFUNCTION(3) instead, if you can. This function gets called by libcurl instead of its internal equivalent with a frequent interval. While data is being transferred it will be called very frequently, and during slow periods like when nothing is being transferred it can slow down to about one call per second. clientp is the pointer set with CURLOPT_PROGRESSDATA(3), it is not used by libcurl but is only passed along from the application to the callback. The callback gets told how much data libcurl will transfer and has transferred, in number of bytes. dltotal is the total number of bytes libcurl expects to download in this transfer. dlnow is the number of bytes downloaded so far. ultotal is the total number of bytes libcurl expects to upload in this transfer. ulnow is the number of bytes uploaded so far. Unknown/unused argument values passed to the callback will be set to zero (like if you only download data, the upload size will remain 0). Many times the callback will be called one or more times first, before it knows the data sizes so a program must be made to handle that. Returning a non-zero value from this callback will cause libcurl to abort the transfer and return CURLE_ABORTED_BY_CALLBACK. If you transfer data with the multi interface, this function will not be called during periods of idleness unless you call the appropriate libcurl function that performs transfers. CURLOPT_NOPROGRESS(3) must be set to 0 to make this function actually get called. DEFAULT
By default, libcurl has an internal progress meter. That's rarely wanted by users. PROTOCOLS
All EXAMPLE
https://curl.haxx.se/libcurl/c/progressfunc.html AVAILABILITY
Always RETURN VALUE
Returns CURLE_OK. SEE ALSO
CURLOPT_VERBOSE(3), CURLOPT_NOPROGRESS(3), libcurl 7.54.0 February 03, 2016 CURLOPT_PROGRESSFUNCTION(3)
All times are GMT -4. The time now is 11:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy