05-20-2010
Quote:
My doubt is why not the reader gets SIGPIPE when write process terminates/ no write process exists.
Because there simply is no need to signal the reader as the reader already has a mechanism to detect this condition.
9 More Discussions You Might Find Interesting
1. Programming
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
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
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
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
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
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
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
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
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
PCSCD(8) PC/SC Lite PCSCD(8)
NAME
pcscd - PC/SC Smart Card Daemon
SYNOPSIS
pcscd [options]
OPTIONS
-a, --apdu
log APDUs and SW using the debug method (see --debug).
-c, --config file
Specifies the file file as an alternate location for /etc/reader.conf.
-f, --foreground
Runs pcscd in the foreground and sends log messages to stderr instead of syslog(3).
-d, --debug
use the lowest log level. Any log message of this level or above will be sent to stderr or syslog(3) depending on the use of --fore-
ground.
--info use info log level. This is the default log level.
--error
use error log level.
--critical
use critical log level.
The log levels are ordered as: debug < info < error < critical. Use a log level l will log this level and all the levels above it.
-h, --help
Displays information about the pcscd command line
-v, --version
Displays the program version number
-H, --hotplug
Ask pcscd to rescan the USB buses for added or removed readers and re-read the /etc/reader.conf file to detect added or removed non-
USB readers (serial or PCMCIA).
DESCRIPTION
pcscd is the daemon program for pcsc-lite and the MuscleCard framework. It is a resource manager that coordinates communications with smart
card readers and smart cards and cryptographic tokens that are connected to the system.
pcscd is normally started at boot time from /etc/init.d/pcscd. It allows applications to access smart cards and readers without knowing
details of the card or reader.
pcscd coordinates the loading of drivers for card readers.
The purpose of pcsc-lite is to provide a cross compatible API (called winscard) for migrating Windows based PC/SC applications to Unix.
At startup, pcscd loads the smart card reader drivers specified in the /etc/reader.conf file (or specified using --config file).
SERIAL SMART CARD READER DRIVERS
Smart card reader drivers are placed in the /usr/lib64/readers directory. Each driver is simply an .so file. pcscd locates the driver
using the /etc/reader.conf file. See the reader.conf(5) manual page for more information. Drivers are available at http://www.muscle-
card.com/drivers.html.
USB SMART CARD READER DRIVERS
USB smart card reader drivers are located in /usr/lib64/readers directory as a bundle. You shall not add a USB driver in /etc/reader.conf
file.
FILES
/etc/reader.conf : Reader configuration file
/etc/init.d/pcscd : pcscd startup script
/var/run/pcscd/pcscd.pid : process id of the running pcscd
/usr/lib64/readers : directory containing bundles for USB drivers
SEE ALSO
bundleTool(8), reader.conf(5), syslog(3)
AUTHORS
David Corcoran <corcoran@musclecard.com> and Ludovic Rousseau <ludovic.rousseau@free.fr>
Muscle January 2007 PCSCD(8)