When run under valgrind the process wont have the name "pcscd" but rather will
be called "valgrind" as you sent in your previous mail, either that or kill the
pid directly rather than using killall.
Does SIGTERM correctly kill the process when it's running outside of valgrind?
Ashley,
On 20 Jan 2010, at 18:58, Vasanta wrote:
> killall command should send SIGTERM, but I tried to send either killall or
> "kill -1 3371", neither work.
>
> # killall pcscd
> killall: pcscd: no process killed
> # killall /pfrm2.0/bin/pcscd
> killall: /pfrm2.0/bin/pcscd: no process killed
> #
>
>
>
>
> On Wed, Jan 20, 2010 at 1:53 PM, Ashley Pittman <[email protected]> wrote:
>
> On 20 Jan 2010, at 18:34, Vasanta wrote:
>
> > Ashely / Tom:
> > Initially this pcscd runs, then it forks, that is why PID is diff, I run
> > with trace-children=yes, didn't get much info since program is keep running
>
> This is what you'd expect, errors will be reported as it runs, leak checking
> will be performed when it exits.
>
> > I don't know how can I forcefully exit, the main function in this below
> > link for pcscdaemon.c file. also I tried --foreground, gives error for that
> > option. any idea can I force exit pcscd?
>
> This is entirely down to pscsd, how do you normally shut it down? Sending
> SIGTERM is often the best way to stop deamons unless they implement their own
> exit case.
>
> Ashley,
>
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
