On 04/ 7/11 03:27 PM, Shawn Walker wrote:
On 04/ 7/11 03:11 PM, Danek Duvall wrote:
Shawn Walker wrote:
On 04/ 7/11 02:54 PM, Jon Aimone wrote:
<TRANSFER_MOD_E Apr 7 20:47:25> file protocol error: code: 37
<TRANSFER_MOD_E Apr 7 20:47:25> URL:
'file:///net/10.129.133.13/export/ds02/d534/workspace/ja123687/repo/Exalogic/stage1/solaris_repo/repo/publisher/solaris/pkg/library
0.000000libtool -0.000000libltdl/1.5.22
The OS' underlying errno is passed through for NFS repositories. In
this case, the error number is ECHRNG Channel number out of range,
which is a bit bizarre.
That suggests there was some sort of unexpected failure on the NFS
server side.
I think this is more likely the curl error:
/usr/include/curl/curl.h: CURLE_FILE_COULDNT_READ_FILE, /* 37 */
Doh, yes. We do pass through OS errno in other cases though. But I had
forgotten libcurl could bubble up vague messages like this.
Here's the libcurl man page for reference:
http://www.unix.com/man-page/All/3/libcurl-errors/
CURLE_FILE_COULDNT_READ_FILE (37)
A file given with FILE:// couldn't be opened. Most likely
because the file path doesn't identify an existing file. Did you
check file permissions?
-Shawn
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
