-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 25 June 2003 12:21, Andras Mantia wrote:
> On Wednesday 2003 June 25 12:54, Waldo Bastian wrote:
> > On Wednesday 25 June 2003 07:50, Andras Mantia wrote:
> > > Hi,
> > >
> > >  I've noticed that if I try to kill a process started with KProcess, it
> > > won't be killed, altough the kill method returns true and the process
> > > emits the processExited signal. I've tried both with the default
> > > SIGTERM and the SIGKILL signal.
> > > But as it's a GUI application, I still see in the taskbar and can use
> > > it. Is this a normal behavior? Can I kill somehow for real?
> > > This is on CVS HEAD.
> >
> > What does ps -aux has to say about it? Which pid does KProcess try to
> > kill?
>
> I've added some debug output to find out the pid and I realized that
> KProcess kills the correct process. Why I saw the misbehavior was that the
> executable I have started with KProcess was a perl script which launched
> another executable (the one with a GUI). The script is killed, but the GUI
> app was still running. Should the child process also disappear? Any idea
> how can I kill also that one?

Maybe setsid() would help, not sure.

Cheers,
Waldo
- -- 
bastian@kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE++XkrN4pvrENfboIRAo0zAJ9pbKY823ym/zhPohW9zbiekQmJOACgp1bc
Q5gcypgr6IqOVNkZ3Zcm4Lo=
=sgcm
-----END PGP SIGNATURE-----
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<