| 1 |
Liu Chuan posted <19f373bf05082804001fe9cd47@××××××××××.com>, excerpted |
| 2 |
below, on Sun, 28 Aug 2005 19:00:35 +0800: |
| 3 |
|
| 4 |
> After unset all environment variable, it can still start kdm from |
| 5 |
> command line. What are the some other factors that may cause the |
| 6 |
> problem? It there any info that can be deduced from following error |
| 7 |
> message. |
| 8 |
>> > kdm[5526]: unknow session exit code 0 (sig 9) from manager process |
| 9 |
|
| 10 |
Note that I'm just a user, and I don't know much about xdm/kdm in |
| 11 |
particular since I don't use them... |
| 12 |
|
| 13 |
Normally, signal-9 refers to the unblockable kill signal (as opposed to |
| 14 |
the blockable sig-15 terminate), which would only be used if the |
| 15 |
controller thought the child process had gone into never-never-land and |
| 16 |
wasn't responding, because otherwise, a sig-term (sig-15) would be used, |
| 17 |
to allow the application to clean up any open files and the like. Note |
| 18 |
that the logging process itself couldn't have received the sig-9, or it |
| 19 |
wouldn't have had time to log it before it was forcibly killed. Thus, the |
| 20 |
message is a bit strange. |
| 21 |
|
| 22 |
What I normally do in situations such as this, when I'm tracing |
| 23 |
init-script or similar issues, is place tell-tail echo statements at |
| 24 |
strategic points in the script, telling me which branch it's taking on IF |
| 25 |
statements and the like, until I narrow the problem down to a small |
| 26 |
section. At that point, I'll use echo var=$var type statements to peek at |
| 27 |
what the vars look like in the section, and eventually find the specific |
| 28 |
problem line, either finding the problem itself, or tracing it into a |
| 29 |
called program. If the called program is another script, I'll continue |
| 30 |
tracing in it. If it's a C program or the like, since I don't know C, at |
| 31 |
least I know what's being called and with what parameters, and can fill |
| 32 |
out a bug report with that info. |
| 33 |
|
| 34 |
If you know sh/bash scripting, that's what I'd suggest you do. If not, |
| 35 |
perhaps it's time to learn. =8^) Tracing scripts is how I learned, well, |
| 36 |
with a bit of help from the bash chapter of my trusty Linux in a Nutshell |
| 37 |
guide, of course. (The bash manpage can be useful for details, but it's |
| 38 |
waayyy to long and complex for learning bash to begin with.) If you'd |
| 39 |
prefer not to buy a book, try one of the many online BASH tutorials |
| 40 |
available. |
| 41 |
|
| 42 |
Or... of course, you can wait and see if anyone else comes up with another |
| 43 |
possibility... |
| 44 |
|
| 45 |
-- |
| 46 |
Duncan - List replies preferred. No HTML msgs. |
| 47 |
"Every nonfree program has a lord, a master -- |
| 48 |
and if you use the program, he is your master." Richard Stallman in |
| 49 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 50 |
|
| 51 |
|
| 52 |
-- |
| 53 |
gentoo-desktop@g.o mailing list |
Archives