fifo

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Mplayer fifo.

Hi all, First of all, sorry for the pastebin link. The code tags aren't working for me. #!/bin/bash # while-menu-dialog: a menu driven - Pastebin.com This is a channel "changer" shell script i'm working on. It uses dialog to display the menus. It...

2. UNIX and Linux Applications

FIFO

Hello , I am working on unix FIFO IPC. i have a doubt regarding that. If the fifo is updated(write()) through one process....can we able to send any signal that fifo is updated and ready to get read...to other process.??

3. Programming

Help With FIFO problem...

=server.c= #include <stdio.h> #include <stdlib.h> #include <sys/stat.h> #include <sys/types.h> #include <unistd.h> #include <errno.h> #include <fcntl.h> #include <string.h> #include <signal.h> #define MSGSIZE 50

4. Programming

How to see a FIFO from all the threads?

Hello C programming fellows!!! I'm doing a program with multiple threads in gnu/linux, ubuntu for beeing precise... This program consist in multiple threads, as logical each thread do different things and communicate to each other using IPC. The problem is that in "process 1" I have a...

5. Programming

help About fifo and thread

hi, my problem is i have 10 thread for produces double two dimensional array these will produces 2d array 400 times ,then i have a thread to takes a two dimensional array then it inverse , and most 10 array can be in the fifo , and threads given takes one by one, now my problem is , i cant...

6. Programming

FIFO's and asynchronousity?

Hello, I have a FIFO which i would like to open O_WDWR | O_NONBLOCK | O_ASYNC and have a SIGIO signal generated when there is input on the FIFO, but there a re a bunch of bugs surrounding this (like for instance i read somewhere that you have to set O_ASYNC with fcntl etc. is this even...

7. UNIX for Dummies Questions & Answers

Doubts on FIFO

Hi , I m beginner for Unix and i want to use FIFO in my 2 Scripts . I want 1 script to read data from FIFO and other will write into FIFO. Despite reading so many articles/posts i am still unable sunchronize my scripts. My doubts are 1> Do We require both scripts as daemons to use...

8. Programming

how to use fifo

hi, I have a problem. I've done a lil program which gets from the server the given persons username a personal folder. I made it with a pipe calling popen with a command, but how can i make the same thing using fifo. I make the fifo with mkfifo() func. and than what. How do I tell the sertver using...

9. UNIX for Advanced & Expert Users

FIFO Pipes

Hi...Can anyone please guide me on FIFO Pipes in UNIX.I have lerant things like creating fifo pipes,using them for reads and writes etc.I want to know what is the maximum amount of memory that such a pipe may have? Also can anyone guide me on where to get info on this topic from?

10. UNIX for Advanced & Expert Users

FIFO over NFS

Hi All L2000-44 HP-UX 11.00 I am attempting to setup a FIFO over NFS. Directing and reading from the FIFO works fine on the local machine - however when I direct to the FIFO from a server which has the directory NFS mounted it does not work. The a process to read from the FIFO on the local...

LEARN ABOUT DEBIAN

gd_uninclude

gd_uninclude(3) 						      GETDATA							   gd_uninclude(3)

NAME

       gd_uninclude -- remove a format specification fragment from a dirfile

SYNOPSIS

       #include <getdata.h>

       int *gd_uninclude(DIRFILE *dirfile, int fragment_index, int del);

DESCRIPTION

       The gd_uninclude() removes the format specification fragment indexed by fragment_index from the specified dirfile, as well as any fragments
       the indicated fragment INCLUDEs.  Fields defined in the removed fragments will be removed from the dirfile.

       Before removing the specified fragment, all pending writes are flushed to RAW fields defined the the removed fragments.	If  del  is  zero,
       metadata  changes  will	also  be written to the removed fragments.  If del is non-zero, the format specification fragments will be deleted
       from disk, if possible.	Regardless of the value of del, binary data files associated with RAW fields defined in the removed fragments will
       not be deleted.	To delete these binary files, use gd_delete(3) before calling this function.

       The primary format specification (the fragment indexed by zero) cannot be removed from the dirfile.

RETURN VALUE

       On  success, gd_uninclude() returns zero.  On error, -1 is returned and the dirfile error is set to a non-zero error value.  Possible error
       values are:

       GD_E_ACCMODE
	       The supplied dirfile was opened in read-only mode.

       GD_E_ALLOC
	       The library was unable to allocate memory.

       GD_E_BAD_DIRFILE
	       The supplied dirfile was invalid.

       GD_E_BAD_INDEX
	       The supplied fragment index was out of range, or an attempt was made to remove the primary format specification.

       GD_E_FLUSH
	       A temporary file could not be opened into which to write the metadata of a modified, removed fragment, or  renaming  the  temporary
	       file over the original fragment failed.

       GD_E_PROTECTED
	       The metadata of the fragment which included the removed fragment was protected from change.

       GD_E_RAW_IO
	       An error occurred while trying to flush or close a removed field.

       The  dirfile error may be retrieved by calling gd_error(3).  A descriptive error string for the last error encountered can be obtained from
       a call to gd_error_string(3).  When finished with it, the DIRFILE object may be de-allocated with a call to gd_close(3), even if  the  open
       failed.

NOTES

       This  function  re-arranges the remaining format specification fragments in some unspecified way, except for the primary fragment, which is
       guaranteed to remain at index zero.  Callers which cache format specification fragment indices must re-initialise their cache after calling
       this function.

       Unlike  gd_delete(3), fields which depend on fields removed by this function are not automatically updated, nor is any check made to ensure
       that this function does not leave fields with missing input fields.  Because of this, a fragment inclusion may be  easily  moved  from  one
       fragment  to  another  with  a  combination of gd_uninclude() and gd_include(3).  However, if such checks are required, use gd_delete(3) to
       delete the fields defined in the removed fragments first.

SEE ALSO

       gd_delete(3),  gd_include(3),  gd_open(3),  gd_reference(3),   gd_error(3),   gd_error_string(3),   gd_fragmentname(3),	 gd_nfragments(3),
       dirfile(5), dirfile-encoding(5), dirfile-format(5)

Version 0.7.0							  15 October 2010						   gd_uninclude(3)

Programming