from small one page howto to huge articles all in one place
 

search text in:





Poll
What does your sytem tell when running "ulimit -u"?








poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

187705

userrating:

average rating: 1.7 (102 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

250639

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

138300

userrating:

average rating: 1.4 (42 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





ARCHIVE_WRITE_DATA

Section: C Library Functions (3)
Index Return to Main Contents

BSD mandoc
 

NAME

archive_write_data archive_write_data_block - functions for creating archives  

LIBRARY

Streaming Archive Library (libarchive, -larchive)  

SYNOPSIS

In archive.h Ft la_ssize_t Fn archive_write_data struct archive * const void * size_t Ft la_ssize_t Fn archive_write_data_block struct archive * const void * size_t size int64_t offset  

DESCRIPTION

Fn archive_write_data
Write data corresponding to the header just written.
Fn archive_write_data_block
Write data corresponding to the header just written. This is like Fn archive_write_data except that it performs a seek on the file being written to the specified offset before writing the data. This is useful when restoring sparse files from archive formats that support sparse files. Returns number of bytes written or -1 on error. (Note: This is currently not supported for archive_write handles, only for archive_write_disk handles.

 

RETURN VALUES

This function returns the number of bytes actually written, or a negative error code on error.  

ERRORS

Detailed error codes and textual descriptions are available from the Fn archive_errno and Fn archive_error_string functions.  

BUGS

In libarchive 3.x, this function sometimes returns zero on success instead of returning the number of bytes written. Specifically, this occurs when writing to an Vt archive_write_disk handle. Clients should treat any value less than zero as an error and consider any non-negative value as success.  

SEE ALSO

tar(1), libarchive(3), archive_write_finish_entry3, archive_write_set_options3, cpio(5), mtree(5), tar(5)


 

Index

NAME
LIBRARY
SYNOPSIS
DESCRIPTION
RETURN VALUES
ERRORS
BUGS
SEE ALSO





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2020 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 10.3 ms