Sponsored Content
Top Forums UNIX for Advanced & Expert Users Why not SIGPIPE for readers of pipe/FIFO? Post 302422978 by Corona688 on Wednesday 19th of May 2010 11:43:42 PM
Old 05-20-2010
Think about it. Is reading still potentially possible when the writing process terminates?
 

9 More Discussions You Might Find Interesting

1. Programming

Magnetic card readers

i can't find any info on developing for magnetic card readers in the unix environment. I'm developing a POS system and i want it to include credit card verification. Any direction would be hot... (6 Replies)
Discussion started by: Gekko
6 Replies

2. Programming

Pipe & fifo....

Could someone Help me with this code please? #include <stdio.h> #include <unistd.h> #include <sys/types.h> #include <sys/stat.h> #include <string.h> #include <fcntl.h> #define SIZE_B 256 /*buffer's size */ #define NUM_ARG 20 /* max number of args for any command */ int... (4 Replies)
Discussion started by: M3xican
4 Replies

3. UNIX for Advanced & Expert Users

PIPE and FIFO buffer size

Hello! How I can increase (or decrease) the predefined pipe buffer size? Thanks! (1 Reply)
Discussion started by: Jus
1 Replies

4. Shell Programming and Scripting

Reading from blocking fifo pipe in shell script

Hi!! I have a problem reading from a fifo pipe in shell script. The idea is simple, I have a C program with two pipe files: An input pipe I use to send commands in shell script to the C program (echo "command" > input.pipe) An output pipe that I read the result of the command also in... (4 Replies)
Discussion started by: victorin
4 Replies

5. UNIX for Dummies Questions & Answers

fifo or named pipe working?

Can someone explain to me the working of fifo() system call using simple C programs so that I can implement them in the UNIX environement? (1 Reply)
Discussion started by: lvkchaitanya
1 Replies

6. Programming

Pipe & fifo size limit

Hi guys. 1. how much is the size of pipe?(i mean the buffer size) 2. is this size different in various UNIX derivations? 3. what happens if we write to a full pipe? does it block until get some free space(the other side receive data) or returns an error? 3. FIFO s are physical files on the... (2 Replies)
Discussion started by: majid.merkava
2 Replies

7. Shell Programming and Scripting

awk reading from named pipe (fifo)

I'm trying to read a fifo using awk and comming across some problems. I'm writing to the fifo from multiple processes invoked by GNU Parallel: mkfifo my_fifo awk '{ a = a + $2 } END { for (i in a) print i, a }' my_fifo | sort -nk1 > sorted_output grep -v '^@' massive_file | parallel... (3 Replies)
Discussion started by: nathanhaigh
3 Replies

8. Programming

SIGPIPE and EPIPE

When a write() writes on a broken pipe, with no readers, it generates a SIGPIPE signal and the process exits. When the write() returns -1 and errno is EPIPE? Do I have an handler for SIGPIPE, or can I ignore it? (2 Replies)
Discussion started by: hurricane
2 Replies

9. Shell Programming and Scripting

UNIX fifo concurrent read from a named pipe

I have created a fifo named pipe in solaris, which writes the content of a file, line by line, into pipe as below: $ mkfifo namepipe $ cat books.txt "how to write unix code" "how to write oracle code" $ cat books.txt >> namepipe & I have a readpipe.sh script which reads the named... (2 Replies)
Discussion started by: naveen mani
2 Replies
pthread_exit(3T)														  pthread_exit(3T)

NAME
pthread_exit() - cause the calling thread to terminate SYNOPSIS
PARAMETERS
value_ptr The calling thread's exit status. DESCRIPTION
terminates the calling thread. The calling thread returns an exit status in value_ptr. This value is returned to a joining thread calling on the terminating thread. Only threads created with the detachstate attribute value can return an exit status to The exit status of a detached thread is lost when the thread terminates. When a thread terminates, process-shared resources are not released. Examples of process-shared resources include mutexes, condition vari- ables, semaphores, message queue descriptors, and file descriptors. The routines are not called when a thread terminates as this is a process termination action. An implicit call to is made when a thread returns from its start routine. The function's return value serves as the thread's exit status (see pthread_create(3T)). If the main thread returns from without calling the process will exit using the return value from as the exit status. If the main thread calls the process will continue executing until the last thread terminates or a thread calls After the last thread in the process terminates, the process will exit with an exit status of zero. Any installed cancellation cleanup handlers will be popped and executed in the reverse order that they were installed. After the cancella- tion cleanup handlers have been executed, if the thread has any non-NULL thread-specific data values with associated destructor functions, the destructor functions are called. The order in which these destructor functions are called is unspecified. Calling from a cancellation cleanup handler or destructor function that was invoked because of thread termination results in undefined behavior. After a thread has terminated, the result of access to local (auto) variables of the thread is undefined. The terminating thread should not use local variables for the value_ptr parameter value. RETURN VALUE
None. ERRORS
None, this function does not return. AUTHOR
was derived from the IEEE POSIX P1003.1c standard. SEE ALSO
pthread_create(3T), pthread_join(3T), exit(2), wait(2). STANDARDS CONFORMANCE
Pthread Library pthread_exit(3T)
All times are GMT -4. The time now is 03:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy