On Mon, Apr 09, 2001 at 10:14:32AM -0400, Trond Eivind Glomsrød wrote:
> > Does nobody have an answer for this?
>
> I've never seen it happen[1], but that doesn't help you much. If you
> didn't start the programs from an xterm, but from a menu, you might
> find more info in $HOME/.xsession-errors.
>
> [1] Except for Netscape and mozilla
I can live with NS dying on me; it used to happen before and I'm not
surprised.
I looked in .xsession-errors, and I have many lines like these:
undecodable
token:
undecodable
token:
undecodable
token:
undecodable
token:
And some other odd ones like:
\1b[8;33;80t\1b[8;33;80t\1b[8;33;80tundecodable
token:
kwm: X_ConfigureWindow(0x1200616): BadMatch (invalid parameter attributes)
Nothing saying 'died' or 'crashed', unless the above means that.
Most of the application crashes occur when the application is sitting
in the background, and I'm not working with it, so it can't be something
I've triggered by moving/sizing/clicking on the application.
I was thinking about resource limits. Can they cause an application
to be killed off? My limits, as reported by an interactive bash shell,
running in "konsole":
core file size (blocks) 1000000
data seg size (kbytes) unlimited
file size (blocks) unlimited
max locked memory (kbytes) unlimited
max memory size (kbytes) unlimited
open files 1024
pipe size (512 bytes) 8
stack size (kbytes) 8192
cpu time (seconds) unlimited
max user processes 2048
virtual memory (kbytes) unlimited
But my applications are started from the KDE panel, so I don't know if
it has a different set of limits.
--
Anand
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
