Here is an idea of how to find the problem.

Find your gdm and move it to gdm.bin and create a bash script in it's place that dumps the env to a new log file alone with the parent PID that called gdm.

On my system this would be like this...
[EMAIL PROTECTED] which gdm
/usr/bin/gdm
[EMAIL PROTECTED] mv /usr/bin/gdm /usr/bin/gdm.bin
[EMAIL PROTECTED] vi /usr/bin/gdm

-- START OF SCRIPT --
#!/bin/bash

LOG_FILE="/tmp/wtf_is_up_with_gdm.log"
# Don't over write it only need to write it once
if [ ! -f $LOG_FILE ]; then
date > LOG_FILE
echo "Called gdm again" >> $LOG_FILE
echo "evn = " >> $LOG_FILE
env >> $LOG_FILE
echo "-------" >> $LOG_FILE
OUR_PID=$$
# This next line does not work with any version of busybox that I have tried.
PARENT_PID=`ps -fp $OUR_PID | grep $OUR_PID | gawk '{print $3}'`
echo "Parent PID of the app that is calling GDM = " >> $LOG_FILE
fi
/usr/bin/gdm.bin $@

-- END OF SCRIPT --
[EMAIL PROTECTED] chmod 755 /usr/bin/gdm
[EMAIL PROTECTED] exit

Then watch to see if you new log file is created. Read what it says. If you can't figure it out post the log here.



On Thu, 2006-03-09 at 10:31 -0500, Lonnie Cumberland wrote:
Hello All,

I have been monitoring my logs and have see that I am getting many 
messages filling up these logs and do not know why.

-------------------------
.
.
.
Mar  9 08:42:06 aphria gdm[26098]: gdm already running. Aborting!
Mar  9 08:42:07 aphria gdm[26135]: gdm already running. Aborting!
Mar  9 08:42:07 aphria gdm[26185]: gdm already running. Aborting!
Mar  9 08:42:07 aphria gdm[26228]: gdm already running. Aborting!
Mar  9 08:42:07 aphria gdm[26265]: gdm already running. Aborting!
Mar  9 08:42:07 aphria gdm[26302]: gdm already running. Aborting!
Mar  9 08:42:07 aphria gdm[26339]: gdm already running. Aborting!
Mar  9 08:42:07 aphria gdm[26376]: gdm already running. Aborting!
Mar  9 08:42:08 aphria gdm[26413]: gdm already running. Aborting!
Mar  9 08:42:08 aphria gdm[26450]: gdm already running. Aborting!
Mar  9 08:42:08 aphria gdm[26487]: gdm already running. Aborting!
Mar  9 08:42:08 aphria gdm[26524]: gdm already running. Aborting!
Mar  9 08:42:08 aphria gdm[26561]: gdm already running. Aborting!
Mar  9 08:42:08 aphria gdm[26598]: gdm already running. Aborting!
Mar  9 08:42:08 aphria gdm[26635]: gdm already running. Aborting!
Mar  9 08:42:08 aphria gdm[26672]: gdm already running. Aborting!
Mar  9 08:42:09 aphria gdm[26710]: gdm already running. Aborting!
Mar  9 08:42:09 aphria gdm[26747]: gdm already running. Aborting!
Mar  9 08:42:09 aphria gdm[26784]: gdm already running. Aborting!
Mar  9 08:42:09 aphria gdm[26821]: gdm already running. Aborting!
Mar  9 08:42:09 aphria gdm[26858]: gdm already running. Aborting!
Mar  9 08:42:09 aphria gdm[26895]: gdm already running. Aborting!
Mar  9 08:42:09 aphria gdm[26932]: gdm already running. Aborting!
Mar  9 08:42:10 aphria gdm[26969]: gdm already running. Aborting!
Mar  9 08:42:10 aphria gdm[27006]: gdm already running. Aborting!
Mar  9 08:42:10 aphria gdm[27043]: gdm already running. Aborting!
Mar  9 08:42:10 aphria gdm[27080]: gdm already running. Aborting!
Mar  9 08:42:10 aphria gdm[27117]: gdm already running. Aborting!
Mar  9 08:42:10 aphria gdm[27154]: gdm already running. Aborting!
Mar  9 08:42:10 aphria gdm[27191]: gdm already running. Aborting!
Mar  9 08:42:10 aphria gdm[27228]: gdm already running. Aborting!
Mar  9 08:42:11 aphria gdm[27265]: gdm already running. Aborting!
Mar  9 08:42:11 aphria gdm[27302]: gdm already running. Aborting!
Mar  9 08:42:11 aphria gdm[27339]: gdm already running. Aborting!
Mar  9 08:42:11 aphria gdm[27376]: gdm already running. Aborting!
Mar  9 08:42:11 aphria gdm[27413]: gdm already running. Aborting!
Mar  9 08:42:11 aphria gdm[27450]: gdm already running. Aborting!
.

.
-----------------------------
It did the same thing the other day and then stopped for a while but now 
is doing it again.

Any ideas as to what is happening here and how I can stop it?

Cheers,
Lonnie



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Royce Souther
www.SiliconTao.com
Let Open Source help your business move beyond.

For security this message is digitally authenticated by GnuPG.



Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to