KWTm
03-01-2003, 09:08 PM
I notice that when I leave my computer for a long time, the windows seem to disappear by themselves, the programs having turned off. This applies to several different programs, including consoles (Eterm), editors (kate) and browsers (Mozilla 1.0.0). They are not on screen, not on the taskbar, and not even on the windows list of programs, but when I do a "ps -U", they show up. Somewhere in limbo there floats my programs.
In fact, now I have a problem starting Kate, the editor, because I set it to restrict to only one instance. (That one instance would edit multiple files.) When I start Kate by menu or by command line, nothing happens.
There must be some lockfile or something that signals that somewhere, there is another copy of Kate running. Except there isn't --something shut it down, and I'm guessing that it's IceWM.
1. How do I tell my computer not to close the windows just because I fell asleep for 8 hours?
2. How do I regain control of my floating-in-limbo jobs? Here is the partial output from "ps -e":
PID TTY TIME CMD
10397 ? 00:00:19 kate
You can see that kate has no TTY output. I don't know how to use the "fg" command to bring it to the front.
3. Where is that signal or lockfile or config file or whatever that tells Kate that there is another copy running? I'd like to wipe that.
-----
Anyway, I'm happy to say that I'm making the big jump to using Linux even on my main computer. I'm using LibraNet 2.0 (Debian-based). The default IceWM has a better feel for me as a long-time Win2k user than either GNOME or KDE. (Eventually I hope to use KDE with IceWM as the window manager.) I'd love to hear comments about IceWM in general from anyone, especially cage-47, who seems quite happy with it.
In fact, now I have a problem starting Kate, the editor, because I set it to restrict to only one instance. (That one instance would edit multiple files.) When I start Kate by menu or by command line, nothing happens.
There must be some lockfile or something that signals that somewhere, there is another copy of Kate running. Except there isn't --something shut it down, and I'm guessing that it's IceWM.
1. How do I tell my computer not to close the windows just because I fell asleep for 8 hours?
2. How do I regain control of my floating-in-limbo jobs? Here is the partial output from "ps -e":
PID TTY TIME CMD
10397 ? 00:00:19 kate
You can see that kate has no TTY output. I don't know how to use the "fg" command to bring it to the front.
3. Where is that signal or lockfile or config file or whatever that tells Kate that there is another copy running? I'd like to wipe that.
-----
Anyway, I'm happy to say that I'm making the big jump to using Linux even on my main computer. I'm using LibraNet 2.0 (Debian-based). The default IceWM has a better feel for me as a long-time Win2k user than either GNOME or KDE. (Eventually I hope to use KDE with IceWM as the window manager.) I'd love to hear comments about IceWM in general from anyone, especially cage-47, who seems quite happy with it.