04-05-2002
functionalities of PFILES
Hello every body.
Do anyone describe to me functionalities of PFILES
5 More Discussions You Might Find Interesting
1. Red Hat
Can someone tell me the Linux equivalent for pstack and pfiles and ptree which are Solaris commands. (1 Reply)
Discussion started by: bdsffl
1 Replies
2. Solaris
Hi,
When I use pfiles PID, it displays the below output and i just see the inode, can i able to get the full path and file name? pl help me on this.
Current rlimit: 8192 file descriptors
0: S_IFCHR mode:0620 dev:308,0 ino:12582968 uid:1001378434 gid:7 rdev:24,26
O_RDWR
... (3 Replies)
Discussion started by: balamv
3 Replies
3. Shell Programming and Scripting
Hi,
I Have downloaded script for pfiles command, It is written to make it run on Linux, But I could not make out on which language it is written,kindly help me in executing this script:(
link: http://sourceware.org/systemtap/examples/process/pfiles.stp (1 Reply)
Discussion started by: thehulkom
1 Replies
4. Solaris
What is the significance of pfiles?
What is the use of it and how and where to use it?:wall: (2 Replies)
Discussion started by: varunksharma87
2 Replies
5. UNIX for Dummies Questions & Answers
May i know what is the equivalent tool in linux for pflies in solaris. ? (2 Replies)
Discussion started by: mohtashims
2 Replies
LEARN ABOUT SUSE
ne_set_request_body_buffer
NE_SET_REQUEST_BODY_(3) neon API reference NE_SET_REQUEST_BODY_(3)
NAME
ne_set_request_body_buffer, ne_set_request_body_fd, ne_set_request_body_fd64 - include a message body with a request
SYNOPSIS
#include <ne_request.h>
void ne_set_request_body_buffer(ne_request *req, const char *buf, size_t count);
int ne_set_request_body_fd(ne_request *req, int fd, off_t begin, off_t length);
DESCRIPTION
The ne_set_request_body_buffer function specifies that a message body should be included with the body, which is stored in the count bytes
buffer buf.
The ne_set_request_body_fd function can be used to include a message body with a request which is read from a file descriptor. The body is
read from the file descriptor fd, which must be a associated with a seekable file (not a pipe, socket, or FIFO). count bytes are read,
beginning at offset begin (hence, passing begin as zero means the body is read from the beginning of the file).
For all the above functions, the source of the request body must survive until the request has been dispatched; neither the memory buffer
passed to ne_set_request_body_buffer nor the file descriptor passed to ne_set_request_body_fd are copied internally.
SEE ALSO
ne_request_create
AUTHOR
Joe Orton <neon@lists.manyfish.co.uk>
Author.
COPYRIGHT
neon 0.28.4 25 February 2009 NE_SET_REQUEST_BODY_(3)