Provided by: libpam-pkcs11_0.6.8-4_amd64 bug

NAME

       card_eventmgr - PCSC-Lite Event Manager

SYNTAX

       card_eventmgr   [debug]  [[no]daemon]  [timeout=<msecs>]  [config_file=<filename>]  [kill]
       [pidfile=<pidfile>]

DESCRIPTION

       card_eventmgr is a smart card monitoring tool that listen to the status of the card reader
       and  dispatch  actions  on several events.  card_eventmgr can be used for several actions:
       like screen lock on card removal.

       Three events are supported: card insertion, card removal  and  timeout  on  removed  card.
       Actions are specified in a configuration file.

OPTIONS

       debug  Enable debugging output.

       [no]daemon
              Runs  in  background  if daemon or in foreground if nodaemon (default). If debug is
              unset, the program dettaches itself from the tty.

       timeout=<msecs>
              Set polling timeout in milliseconds. Defaults to 1000 (1 second).

       config_file=<configuration file>
              Sets de configuration file. Default value is /etc/pam_pkcs11/card_eventmgr.conf.

       pidfile=<pidfile>
              Store the card_eventmgr process ID (pid) in the file pidfile.

       kill   Read a process id from pidfile and kill that process. You  must  use  the  argument
              pidfile=<pidfile> to use kill.

FILES

       /etc/pam_pkcs11/card_eventmgr.conf

EXAMPLES

       To run this program the standard way type:

        card_eventmgr

       Alternatively you can specify options:

        card_eventmgr debug nodaemon timeout=500 config_file=$HOME/.card_eventmgr.conf

       If you want to start and stop card_eventmgr automatically in an X11 session you can create
       a ~/.xsession file containing:
        # start the card autolock
        card_eventmgr pidfile=$HOME/.card_eventmgr.pid

        # start Gnome or something else
        /usr/bin/x-session-manager

        # kill the card autolock
        card_eventmgr kill pidfile=$HOME/.card_eventmgr.pid

BUGS

       Some applications like xscreensaver-command may fail due to external events  (eg:  try  to
       unlock an unlocked session).  In this case, the command incorrectly returns error code.

AUTHORS

       Juan Antonio Martinez <jonsito@teleline.es>
       Ludovic Rousseau <ludovic.rousseau@free.fr>

SEE ALSO

       pam_pkcs11(8), pkcs11_eventmgr(1), README.eventmgr, PAM-PKCS11 User Manual