* Julian Elischer <[EMAIL PROTECTED]> [030624 19:01]:
> As of last testing (yesterday my laptop (non SMP) acted the same..
>
> I'm not sure what to suggest.
> can you confirm that you are running the newest of everything..
> (though as far as I know it was ok, even several weeks ago).
I'll re-cv
On Tue, 24 Jun 2003, Julian Elischer wrote:
> I can not duplicate this..
> ON a system (SMP) compiled this afternoon (checked out this afternoon
> too), ksetest responds immediatly to ^C and ^Z in the expected manner.
>
> I am using the csh as my shell and was running as root AND as myself
> for t
On Tue, 24 Jun 2003, Michael Edenfield wrote:
[...]
> thread_start() : 0x84af000 84af000
> kse_create() -> 0
> A*.kse_create() -> -1
> [...]
> *R*.S.*T*.^C^D^Z
>
> (no response on this tty, so I close it).
I can not duplicate this..
ON a system (SMP) compiled this afternoon (checked out this a
If it's duplicatable on recent systems I'll see it on my test system...
thanks..
On Tue, 24 Jun 2003, Michael Edenfield wrote:
> * Julian Elischer <[EMAIL PROTECTED]> [030624 14:47]:
>
> > > I had the same experience just running the KSE test application from
> > > /usr/src/tools last night.
* Julian Elischer <[EMAIL PROTECTED]> [030624 14:47]:
> > I had the same experience just running the KSE test application from
> > /usr/src/tools last night. I ended up with three unkillable ksetest
> > applications and ultimately rebooted to get rid of them. I was
> > planning to report it a
On Tue, 24 Jun 2003, Julian Elischer wrote:
> what about kill -9 887
> ?
> The signals in libKSE are known to be 'delicate'.
> We are working on (well, actually David Xu is working on)
> a set of code to make the signal more robust.
> Hopefully this will fix the problem you are seeing..
Kill -9 d
On Tue, 24 Jun 2003, Michael Edenfield wrote:
> * Wesley Morgan <[EMAIL PROTECTED]> [030624 12:45]:
>
> > Thought I would give libKSE a try making use of the 'libmap.conf' library
> > translations. KDE loads fine, but when I tried to run Firebird I get a
> > process with 3 threads, and it is co
what about kill -9 887
?
The signals in libKSE are known to be 'delicate'.
We are working on (well, actually David Xu is working on)
a set of code to make the signal more robust.
Hopefully this will fix the problem you are seeing..
Any other comments?
Other than not being able to kill it, how as t
* Wesley Morgan <[EMAIL PROTECTED]> [030624 12:45]:
> Thought I would give libKSE a try making use of the 'libmap.conf' library
> translations. KDE loads fine, but when I tried to run Firebird I get a
> process with 3 threads, and it is completely unkillable. It also is
I had the same experience
