1. Is there a way to "adopt" ;) an orphan X app (orphan process)
Hi,
I'm asking this question here because of the rare nature of the
problem, I guess only experienced programmers will have an answer (but
then I'm a linux newbie, so maybe everyone and his mother knows the
answer of my stupid question, bear with me then. ;-).
Scenario: I've got Mozilla and several other X apps working on my
Linux (kernel 2.4.10, KDE 2.2.1). I press the "K" in kde and the
system becomes hosed. I can move the mouse but clicking everywhere
does not produce any effects. Everything indicates that KDE, X, or
maybe both, have entered some form of do-nothing loop, or crashed.
(well, I can move my mouse and the pointer is drawn, so I guess X is
actually working :o).
I login from my Winblows machine on the home lan via ssh, and notice
the system (text mode) is working perfectly, as I suspected. :o).
I proceed to "kill -9" everything with "kde" on its name (by looking
at the 'ps -A' output).
Finally I look at my system which was previously crashed, and find KDE
has restarted, so I'm back at the kde user login screen. :o)
BUT, the old X apps that I had opened (specially Mozilla) ARE still
there on the 'ps -A' output, I just can't bring them back. (In fact I
was writing a long and very important e-mail at the time of the crash,
but that's just Murphy's Law at work, as usual :-).
Stupid question, is there any way in which I, logged as root, can
attempt to bring back the Mozilla that's still running, in the
darkness, in a parallel universe, so I can save (or finish) my email?.
:o)
I guess the answer is NO. (maybe, "no, go away!" ;-), but I must be a
masochist, because I insist on asking about it here.
Thanks in advance for your time.
Willy
2. Mail Gateway
3. Help on setting IDE mult sectors w/hdparm
4. I have problems with my CD-Rom
5. WARNING about hdparm
6. NFS mounting with two Linux boxes
7. ufsdump: Warning - cannot read sector #
8. RH5.2 no go on SCSI Barracuda 10G
9. Boot sector virus warning with FreeBSD boot loader
10. warning: xx sectors in last cylinder unallocated (?)
11. Warning: 1 sector(s) in last cylinder unallocated
12. sector-by-sector copy of while drive?
13. write sector by sector...