fifo's are nothing more than files. stat (either the system call, or the the stat command (Linux) or ls -l) gives you the same kind of information about the file.
Oddly enough not all OSes give a filesize result that has the same meaning. Which is probably due to implementation differences.
From solaris man page for stat:
Linux stat man page defines no such limitation. (struct stat) st_size works out to be the number of unread bytes living in the fifo when the stat call is made. (See tstat.c p. 283 example code in M Kerrisk 'The LINUX Programming Interface', which is derived originally from Ed 1 of Stevens).
Therefore you can use stat or ls -l to get file metadata information about a fifo.
hello i am making a client server program
that communicates via FIFOS and i cannot get it to not hang
i also am forking exec-ing the client from the server
my logic (i will spare you the code )
in the server
i make two fifos in my server my file permissions
are 0644
i then open both... (1 Reply)
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... (3 Replies)
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... (0 Replies)
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... (0 Replies)
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... (0 Replies)
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... (1 Reply)
Dear friends
i'm want to implement a program which one file is split into fragments by the server (by some random size) and sent to some processes, so these processes get randomly the fragments of the original file from the server, then the downloader randomly connects to some of these processes... (0 Replies)
Does anyone know why this could be happening? User tries to save into a directory, but gets the error message.
I checked permissions on directory and see the following:
drwxrwxr-x 10 root pm 1024 Nov 22 14:46 Folder 1
drwxrwxr-x 10 root pm 1024 Oct 19 ... (1 Reply)
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.?? (0 Replies)
Discussion started by: Harry443
0 Replies
LEARN ABOUT DEBIAN
explain_stat_or_die
explain_stat_or_die(3) Library Functions Manual explain_stat_or_die(3)NAME
explain_stat_or_die - get file status and report errors
SYNOPSIS
#include <libexplain/stat.h>
void explain_stat_or_die(const char *pathname, struct stat *buf);
DESCRIPTION
The explain_stat_or_die function is used to call the stat(2) system call. On failure an explanation will be printed to stderr, obtained
from explain_stat(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:
explain_stat_or_die(pathname, buf);
pathname
The pathname, exactly as to be passed to the stat(2) system call.
buf The buf, exactly as to be passed to the stat(2) system call.
Returns:
This function only returns on success. On failure, prints an explanation and exits.
SEE ALSO stat(2) get file status
explain_stat(3)
explain stat(2) errors
exit(2) terminate the calling process
COPYRIGHT
libexplain version 0.52
Copyright (C) 2008 Peter Miller
explain_stat_or_die(3)