.TH "chipcardd" "1" "0.9.1" "Martin Preuss" "LibChipCard"
.SH "NAME"
.LP 
chipcardd \- LibChipCard's card reader daemon
.SH "SYNTAX"
.LP 
chipcardd [\fIoptions\fP]
.br 

.SH "DESCRIPTION"
.LP 
This is the LibChipCard card reader server. You need this to access your card readers via LibChipCard.
.BR 

In normal cases chipcardd does not need any root privileges in order to run. So I recommend against running it as root.
.BR 

However, running it as a normal user needs some precautions.
.BR 
The chipcardd must be allowed to write the pidfile and to read the configuration file. You can give each of them as command line arguments.
.BR 
.SH "OPTIONS"
.LP 
.TP 
\fB\-C\fR <\fIconfigfile\fP>
Uses the given configuration file. If omitted the file \fI/etc/chipcardd.conf\fR is used.
.TP 
\fB\-h\fR
Output help information and exit.
.TP 
\fB\-V\fR
Output version information and exit.
.TP 
\fB\-\-pidfile\fR <\fIpidfile\fP>
Use the given file to store the process id. This is used by some init scripts to determine whether the daemon is running. It defaults to \fI/var/run/chipcardd.pid\fR.
.TP 
\fB\-\-logfile\fR <\fIlogfile\fP>
Use the given file to store the log messages. It defaults to \fI/var/log/chipcardd.log\fR. This only applies if the \fBlogtype\fR is \fIfile\fR (see below).
.TP 
\fB\-\-logtype\fR <\fIlogtype\fP>
Use the given log type. Currently the following \fIlogtypes\fR are supported: \fIstderr\fR, \fIfile\fR and \fIsyslog\fR. The last type is only supported on systems using syslog to log system messages (all Linuxes and BSDs)
.TP 
\fB\-f\fR
Dont fork. If you give this option then chipcardd will not fork but stay in foreground. If omitted (and your system supports it) the daemon will fork itself into background.
.TP
\fB\--exit-on-error\fR
Normally the supervising process simply suspends chipcardd if there was a 
setup error and waits either for a HUP or CONT signal. With this option
chipcardd will exit completely upon setup error.



.SH "SIGNALS"
.LP 
The chipcard daemon responds to some signals:
.TP 
\fBTERM\fR
Terminates the daemon smoothly.
.TP 
\fBINT\fR
Terminates the daemon smoothly. The daemon receives this signal if you press 
CTRL\-C while it is running in foreground (with option \fB\-f\fR).
.TP 
\fBUSR1\fR
Increases the verbosity of chipcardd.
.TP 
\fBUSR2\fR
Decreases the verbosity of chipcardd.
.TP 
\fBTSTP\fR
Resumes the daemon until the signal \fICONT\fR is received.
This signal is used by \fIKCardSetup\fR to temporarily suspend the daemon.
.TP 
\fBCONT\fR
Resumes the daemon if it has been suspended by the signal \fITSTP\fR.
This has the side effect that the daemon reloads its configuration file.
.TP 
\fBHUP\fR
Restart the daemon thereby forcing it to reload its configuration file.
.BR 

.LP 
You can send a signal using the command
.br 
\fIkillall \-USR1 chipcardd\fR
.br 
Don't be misled by the name \fIkillall\fR, this is a standard unix tool to send signals to processes. 
.br 
The example above would make chipcardd log more detailed information.
.br 

.SH "FILES"
.LP 
\fI/etc/chipcardd.conf\fP 
.br 
\fI/var/run/chipcardd.pid\fP 
.br 
\fI/var/log/chipcardd.log\fP
.BR 
.SH "ENVIRONMENT VARIABLES"
.LP 
The chipcardd does not use any environment variables
.BR 
.SH "EXAMPLES"
.LP 
To run this program the standard way type:
.LP 
chipcardd
.LP 
If you want to log to a logfile:
.LP 
chipcardd \-\-logtype file \-\-logfile ~/chipcardd.log
.LP 
If you want to use your own pidfile:
.LP 
chipcardd \-\-pidfile ~/chipcardd.pid
.LP 
To watch the daemon for debugging purposes:
.LP 
chipcardd \-\-logtype stderr \-f \-\-pidfile ~/chipcardd.pid
.BR 

.SH "AUTHORS"
.LP 
Martin Preuss <martin@libchipcard.de>
.SH "SEE ALSO"
.LP 
libchipcard.conf(5) chipcardd.conf(5) chipcardc.conf(5)