OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Douglas Atique (datiqueterra.com.br)
Date: Sun Feb 03 2002 - 10:10:34 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Carlos,
    It sure is application responsibility, as the signal is delivered to
    the app, not the driver. I think pcsc-lite-1.0.2b3 corrects this, as
    I read its ChangeLog and found an entry about properly calling
    CloseChannel on the driver (if I recall it is the first entry in the
    ChangeLog).
    I'll give it a try tonight, as I am a bit far from my Solaris box
    right now.
    Thanks all for prompt responses.
    Regards,
    Douglas

    > ---------- Mensagem original -----------
    >
    > De : owner-sclinuxdrizzle.com
    > Para : sclinuxlinuxnet.com
    > Cc :
    > Data : Fri, 1 Feb 2002 11:50:36 -0800 (PST)
    > Assunto : Re: MUSCLE pcsc-lite-1.0.1 plus Solaris 8 x86 plus
    Towitoko ChipDrive Intern plus towitoko-2.0.4 drivers
    >
    > Hi,
    >
    > --- Douglas Atique <datiqueterra.com.br> wrote:
    > > Hi,
    > > I have also compiled towitoko drivers, both 2.0.4 and yesterday
    > > 2.0.5. The tester program works perfectly, only if I initialize
    the
    > > reader then kill the tester there is no provision for
    uninitializing
    > > the driver on a signal. I mean the LED on my ChipDrive Intern
    remains
    > >
    > > green until I start the tester (or pcsc-lite) again, in which
    case it
    > >
    > > is reinitialized and the LED turns off (if I have removed the
    card).
    >
    > Well, in fact I don't think this is driver responsability but
    > application responsability. You can create a signal handler and add
    a
    > call to CT_close() on it. The 'tester' app is just to dumb to
    implement
    > this but your application should if it's likely to be killed by a
    > signal.
    >
    > > Anyway I have compiled pcsc-lite with --enable-debug and tried it
    > > several times with the testpcsc client but the pcscd daemon
    didn't
    > > die before my eyes. Maybe it's something with the daemon
    mechanism. I
    > >
    > > am going to try building pcsc-lite again but now only with --
    enable-
    > > daemon, not --enable-syslog to check if this makes any difference.
    >
    > I think you need to use --disable-syslog and --disable-daemon to see
    > both the towitoko driver and the pcscd output in stdout.
    >
    > > Also, I wonder which signal Solaris sends pcscd when I shut
    Solaris
    > > down, as Solaris seems to hang on killing it (or something else
    which
    > >
    > > happens only when I have started pcscd as a daemon).
    >
    > As Lodovic requested, try his developer version that will call
    driver's
    > close function on receipt of the signal, and see if it changes
    > something.
    >
    > Carlos.
    >
    >
    > __________________________________________________
    > Do You Yahoo!?
    > Great stuff seeking new owners in Yahoo! Auctions!
    > http://auctions.yahoo.com
    > ***************************************************************
    > Unix Smart Card Developers - M.U.S.C.L.E.
    > (Movement for the Use of Smart Cards in a Linux Environment)
    > http://www.linuxnet.com/
    > To unsubscribe send an email to majordomolinuxnet.com with
    > unsubscribe sclinux
    > ***************************************************************
    >
    >

    ***************************************************************
    Unix Smart Card Developers - M.U.S.C.L.E.
    (Movement for the Use of Smart Cards in a Linux Environment)
    http://www.linuxnet.com/
    To unsubscribe send an email to majordomolinuxnet.com with
    unsubscribe sclinux
    ***************************************************************