explain_write_or_die(3) Library Functions Manual explain_write_or_die(3)NAME
explain_write_or_die - write to a file descriptor and report errors
SYNOPSIS
#include <libexplain/write.h>
void explain_write_or_die(int fildes, const void *data, long data_size);
DESCRIPTION
The explain_write_or_die function is used to call the write(2) system call. On failure an explanation will be printed to stderr, obtained
from explain_write(3), and then the process terminates by calling exit(EXIT_FAILURE).
This function is intended to be used in a fashion similar to the following example:
ssize_t result = explain_write_or_die(fildes, data, data_size);
fildes The fildes, exactly as to be passed to the write(2) system call.
data The data, exactly as to be passed to the write(2) system call.
data_size
The data_size, exactly as to be passed to the write(2) system call.
Returns:
This function only returns on success. On failure, prints an explanation and exits.
SEE ALSO write(2)
write to a file descriptor
explain_write(3)
explain write(2) errors
exit(2) terminate the calling process
COPYRIGHT
libexplain version 0.52
Copyright (C) 2008 Peter Miller
explain_write_or_die(3)
Check Out this Related Man Page
explain_pread_or_die(3) Library Functions Manual explain_pread_or_die(3)NAME
explain_pread_or_die - seek and read from a file descriptor and report errors
SYNOPSIS
#include <libexplain/pread.h>
ssize_t explain_pread_or_die(int fildes, void *data, size_t data_size, off_t offset);
ssize_t explain_pread_on_error(int fildes, void *data, size_t data_size, off_t offset))
DESCRIPTION
The explain_pread_or_die function is used to call the pread(2) system call. On failure an explanation will be printed to stderr, obtained
from the explain_pread(3) function, and then the process terminates by calling exit(EXIT_FAILURE).
The explain_pread_on_error function is used to call the pread(2) system call. On failure an explanation will be printed to stderr, obtained
from the explain_pread(3) function, but still returns to the caller.
fildes The fildes, exactly as to be passed to the pread(2) system call.
data The data, exactly as to be passed to the pread(2) system call.
data_size
The data_size, exactly as to be passed to the pread(2) system call.
offset The offset, exactly as to be passed to the pread(2) system call.
RETURN VALUE
The explain_pread_or_die function only returns on success, see pread(2) for more information. On failure, prints an explanation and exits,
it does not return.
The explain_pread_on_error function always returns the value return by the wrapped pread(2) system call.
EXAMPLE
The explain_pread_or_die function is intended to be used in a fashion similar to the following example:
ssize_t result = explain_pread_or_die(fildes, data, data_size, offset);
SEE ALSO pread(2)
read from a file descriptor at a given offset
explain_pread(3)
explain pread(2) errors
exit(2) terminate the calling process
COPYRIGHT
libexplain version 0.52
Copyright (C) 2009 Peter Miller
explain_pread_or_die(3)
Hello,
I need to write this C program:
MyProgram <user>
that write on myfile.txt file all <users> 'process.
MyProgram must call the ps -u <user> command, but with an exec or with a system?
can any one help me?
Thank you (0 Replies)
Dear Friends,
I write a c program to list the directories recursively. For this I write a function called my_readdir to read the content of directory. For this I use read system call it returns -1, then I use readdir system call it gives comment terminated error or segmentation... (1 Reply)
Hello,
Please can any one explain about the parameters to the write systemcalls??
How are they passed?? and how is the address of the user buffer is handled by the kenel??
for ex: write(fd,buf,count);
How does the kernel handles this user buffer address??
After write does the kernel write... (1 Reply)
I'm trying to write an integer to a file using the write() function, but write() requires the parameter to be written to be a const void*.
How would I go about doing this?
also: using itoa() produces a " warning: implicit declaration of function 'itoa' " even though i have #included stdlib.h (2 Replies)