Problem with aio_write() function


 
Thread Tools Search this Thread
Top Forums Programming Problem with aio_write() function
# 1  
Old 06-04-2002
Data Problem with aio_write() function

Hello,

How to execute a call back function after aio_write() or aio_read() in Sun Solaris 5.7?

I have filled the control block struct aiocb as follows:
aio_sigevent.sigev_signo = SIGEV
aio_sigevent.sigev_notify = SIGEV_THREAD

Then I have filled the call back function in
aio_sigevent.sigev_notify_function and the argument in sigev_value.

But, this does not execute the call back function though the asynchronous write is completed in the file.

Can someone explain why this is happening & how to correct it ?

Regards,
Murali
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Bash function problem

I am trying to figure out why I am having a "problem" with some functions in a bash script I am running. The reason for air quoting is that the functions are working, they are just not displaying anything to screen when called from another function. Here's an example: function Create_Input {... (6 Replies)
Discussion started by: dagamier
6 Replies

2. Shell Programming and Scripting

Function problem

hey guys, im trying to learn bourne shell atm and I'm having some issues with functions. so heres my code: #!/bin/bash ##functions memory () { free -m } space () { df -h } ip () { (5 Replies)
Discussion started by: hawkfro12
5 Replies

3. Shell Programming and Scripting

Problem using function in awk

I created two functions that output two random variables. I want to output them in the output file. But it does not seem to work. # Function rgaussian1(r1, r2) # Gaussian random number generator function rgaussian1(r1, r2) { pi = 3.142 v1 = sqrt( -2 * log(rand()) ) v2... (18 Replies)
Discussion started by: kristinu
18 Replies

4. Shell Programming and Scripting

Calling Function Problem

Hi, I had a scripts which calls two function. One function will call another function, script is working fine but the second function is not calling the first function. Below is the script #!/usr/bin/ksh fun1() { echo $DATETIME >> Test1.ksh return 0 } fun2() { typeset DATETIME=`date... (5 Replies)
Discussion started by: somu_june
5 Replies

5. Shell Programming and Scripting

mail function problem

Hello all, I'm attempting to sent an e-mail with the following funtion in my script. The tested that the logic is correct with another native os command, but I can't seem to get mail to work. I played with the "", just can't seem to get it right. Any ideas? Thanks. $my_mail = `mail... (4 Replies)
Discussion started by: jwholey
4 Replies

6. Shell Programming and Scripting

problem, with if condition in function

Hi All, I have a function which reads parameter and gets the value from config file. The entry in the file can be either of two Name=value or Name=value so if the variant is not present it should return me the generic value ie Name without variant. I am first searching for variant in... (4 Replies)
Discussion started by: gurukottur
4 Replies

7. Shell Programming and Scripting

Problem with function script.

Need an extra set of eyes. Can't find function. Can someone help, please. Thanks echo " Is this the correct list of tapes to eject (y/n)?" read option echo $option case $option in y|Y) TAPE_ROUTINE;; ... (3 Replies)
Discussion started by: gzs553
3 Replies

8. Shell Programming and Scripting

Function Problem and CoreDump

Hi, i have a question: i build this function: function WriteLog { .... ... print $* print $* >> FileLog .... .... } the function are called with this sintax: ..... ..... (8 Replies)
Discussion started by: ZINGARO
8 Replies

9. Shell Programming and Scripting

Problem with Recursive function

Hi all, I have to move all the files in a tree directory structure to a single directory. Inorder to know which file is from which directory , i'll have to add the name of the directory to the file name. For this i wrote a recursive function which is as follows... (4 Replies)
Discussion started by: malle
4 Replies

10. Shell Programming and Scripting

PERL function problem

I have perl script as follow. ------------------------------------------------------------------------ #! /usr/bin/env perl use strict; sub printLines { print "Inside the function.............\n"; my (@file , $count , $key ) = $_; print $count , $ key ; #... (2 Replies)
Discussion started by: avadhani
2 Replies
Login or Register to Ask a Question
LIO_LISTIO(3)						     Linux Programmer's Manual						     LIO_LISTIO(3)

NAME
lio_listio - initiate a list of I/O requests SYNOPSIS
#include <aio.h> int lio_listio(int mode, struct aiocb *const aiocb_list[], int nitems, struct sigevent *sevp); Link with -lrt. DESCRIPTION
The lio_listio() function initiates the list of I/O operations described by the array aiocb_list. The mode operation has one of the following values: LIO_WAIT The call blocks until all operations are complete. The sevp argument is ignored. LIO_NOWAIT The I/O operations are queued for processing and the call returns immediately. When all of the I/O operations complete, asyn- chronous notification occurs, as specified by the sevp argument; see sigevent(7) for details. If sevp is NULL, no asynchronous notification occurs. The aiocb_list argument is an array of pointers to aiocb structures that describe I/O operations. These operations are executed in an unspecified order. The nitems argument specifies the size of the array aiocb_list. NULL pointers in aiocb_list are ignored. In each control block in aiocb_list, the aio_lio_opcode field specifies the I/O operation to be initiated, as follows: LIO_READ Initiate a read operation. The operation is queued as for a call to aio_read(3) specifying this control block. LIO_WRITE Initiate a write operation. The operation is queued as for a call to aio_write(3) specifying this control block. LIO_NOP Ignore this control block. The remaining fields in each control block have the same meanings as for aio_read(3) and aio_write(3). The aio_sigevent fields of each control block can be used to specify notifications for the individual I/O operations (see sigevent(7)). RETURN VALUE
If mode is LIO_NOWAIT, lio_listio() returns 0 if all I/O operations are successfully queued. Otherwise, -1 is returned, and errno is set to indicate the error. If mode is LIO_WAIT, lio_listio() returns 0 when all of the I/O operations have completed successfully. Otherwise, -1 is returned, and errno is set to indicate the error. The return status from lio_listio() provides information only about the call itself, not about the individual I/O operations. One or more of the I/O operations may fail, but this does not prevent other operations completing. The status of individual I/O operations in aiocb_list can be determined using aio_error(3). When an operation has completed, its return status can be obtained using aio_return(3). Individual I/O operations can fail for the reasons described in aio_read(3) and aio_write(3). ERRORS
The lio_listio() function may fail for the following reasons: EAGAIN Out of resources. EAGAIN The number of I/O operations specified by nitems would cause the limit AIO_MAX to be exceeded. EINVAL mode is invalid, or nitems exceeds the limit AIO_LISTIO_MAX. EINTR mode was LIO_WAIT and a signal was caught before all I/O operations completed. (This may even be one of the signals used for asyn- chronous I/O completion notification.) EIO One of more of the operations specified by aiocb_list failed. The application can check the status of each operation using aio_return(3). If lio_listio() fails with the error EAGAIN, EINTR, or EIO, then some of the operations in aiocb_list may have been initiated. If lio_lis- tio() fails for any other reason, then none of the I/O operations has been initiated. VERSIONS
The lio_listio() function is available since glibc 2.1. CONFORMING TO
POSIX.1-2001, POSIX.1-2008. NOTES
It is a good idea to zero out the control blocks before use. The control blocks must not be changed while the I/O operations are in progress. The buffer areas being read into or written from must not be accessed during the operations or undefined results may occur. The memory areas involved must remain valid. Simultaneous I/O operations specifying the same aiocb structure produce undefined results. SEE ALSO
aio_cancel(3), aio_error(3), aio_fsync(3), aio_return(3), aio_suspend(3), aio_write(3), aio(7) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. 2012-05-08 LIO_LISTIO(3)