Re: [gentoo-desktop] Re: strange problem with kdm

[John Manko]

Duncan wrote:

>Liu Chuan posted <19f373bf05082804001fe9cd47@××××××××××.com>, excerpted
>below,  on Sun, 28 Aug 2005 19:00:35 +0800:
>
>
>
>>After unset all environment variable, it can still start kdm from
>>command line. What are the some other factors that may cause the
>>problem? It there any info that can be deduced from following error
>>message.
>>
>>
>>>>kdm[5526]: unknow session exit code 0 (sig 9) from manager process
>>>>
>>>>
>
>
>

I hope this is not a stupid question, but who/what is generating the sig 9?

>Note that I'm just a user, and I don't know much about xdm/kdm in
>particular since I don't use them...
>
>Normally, signal-9 refers to the unblockable kill signal (as opposed to
>the blockable sig-15 terminate), which would only be used if the
>controller thought the child process  had gone into never-never-land and
>wasn't responding, because otherwise, a sig-term (sig-15) would be used,
>to allow the application to clean up any open files and the like.  Note
>that the logging process itself couldn't have received the sig-9, or  it
>wouldn't have had time to log it before it was forcibly killed.  Thus, the
>message is a bit strange.
>
>What I normally do in situations such as this, when I'm tracing
>init-script or similar issues, is place tell-tail echo statements at
>strategic points in the script, telling me which branch it's taking on IF
>statements and the like, until I narrow the problem down to a small
>section.  At that point, I'll use echo var=$var type statements to peek at
>what the vars look like in the section, and eventually find the specific
>problem line, either finding the problem itself, or tracing it into a
>called program.  If the called program is another script, I'll continue
>tracing in it.  If it's a C program or the like, since I don't know C, at
>least I know what's being called and with what parameters, and can fill
>out a bug report with that info.
>
>If you know sh/bash scripting, that's what I'd suggest you do.  If not,
>perhaps it's time to learn. =8^)  Tracing scripts is how I learned, well,
>with a bit of help from the bash chapter of my trusty Linux in a Nutshell
>guide, of course.  (The bash manpage can be useful for details, but it's
>waayyy to long and complex for learning bash to begin with.)  If you'd
>prefer not to buy a book, try one of the many online BASH tutorials
>available.
>
>Or... of course, you can wait and see if anyone else comes up with another
>possibility...
>
>
>
-- 
gentoo-desktop@g.o mailing list