On Wed, Oct 16, 2002 at 02:09:07PM +0200, Pavel Rozenboim wrote: > > > -----Original Message----- > > From: Jose Romildo Malaquias [mailto:romildo@uber.com.br] > > Sent: Wed, October 16, 2002 12:45 PM > > To: psyche-list@redhat.com > > Subject: INIT: Id "x" respawning too fast: disabled for 5 minutes > > > > > > On Wed, Oct 02, 2002 at 04:59:36PM -0300, José Romildo > > Malaquias wrote: > > > > > > My new installed RHL 8.0 system was configured > > > to login using gdm. But, except for the first > > > time the system was started, I was unable to > > > run the X Window System. After system > > > initialization, I get the message telling > > > me that > > > > > > INIT: Id "x" respawning too fast: disabled for 5 minutes > > > > > > and after 5 five minutes the message repeats > > > on my Linux console, periodically. > > > > > > When changed from the graphical login to the > > > text login, and restarting X manualy with > > > startx, the problem does not appear. > > > > > > Any clues on what is going on and how to > > > solve the problem? > > > > I have conducted some tests: > > > > # cat /etc/sysconfig/desktop > > DESKTOP="GNOME" > > # /etc/X11/prefdm -nodaemon > > # echo $? > > 2 > > # /usr/bin/gdm -nodaemon > > /usr/bin/gdm: line 175: `mc-transparent-set': not a valid identifier > > # echo $? > > 2 > > # sh /usr/bin/gdm -nodaemon > > /usr/bin/gdm: line 175: `mc-transparent-set': not a valid identifier > > # echo $? > > 2 > > # ls -l /bin/sh > > lrwxrwxrwx 1 root root 4 Oct 1 18:10 /bin/sh -> bash* > > # bash /usr/bin/gdm -nodaemon > > > It think, bash simulates traditional sh behaviour, when run as /bin/sh, and > advanced bash scripts may be incompatible with it. Correct. From the bash man page: "If bash is invoked with the name sh, it tries to mimic the startup behavior of historical versions of sh as closely as possible, while conforming to the POSIX standard as well." > > The last command succeeded. Conclusion: it does make a difference if > > the /usr/bin/gdm script is started with /bin/sh or /bin/bash, > > although /bin/sh is a symbolic link to /bin/bash. Editing the > > script /usr/bin/gdm and changing the first line, which reads > > > > #!/bin/sh > > > > to > > > > #!/bin/bash > > > > and running > > > > # /usr/bin/gdm -nodaemon > > > > also succeeds. > > > > Is there any reason for me seeing this behaviour in my RHL 8.0 > > box? Is anybody else seeing this? I remember seeing a report > > of this error in the limbo-list when (null) was being > > tested, but no satisfactory solution. > > I'm running gdm on 2 Psyche machines without a problem, and I also used it > successfully with (null). I never had to modify either prefdm or gdm > scripts. Btw, your gdm script complains about line 175, while mine has only > 11 lines. But my /usr/bin/gdm script is also only 11 lines and it does not use any advanced bash features, althogh it sources the /etc/profile script, which in turn source all /etc/profile.d/*.sh scripts wich are readable. It turns out that I have a custom script /etc/profile.d/localsetup.sh which defines a function named mc-transparent-set and then, in line 175, defines a new function using the same name. When in POSIX mode, bash (called as sh) flags an error at this line. When in normal mode, bash (called as bash) flags no error. So, what shells are expected to source the /etc/profile script at startup? Both sh and bash? If so, the scripts /etc/profile.d/*.sh should not use any non sh behaviour of bash, right? This same script /etc/profile.d/localsetup.sh was present in my box running RHL 7.3 (before installing 8.0) and there was no such problem. Does anybody still have /usr/bin/gdm from RHL 7.3 to compare with the one from RHL 8.0? > > Any clues? Romildo -- Prof. José Romildo Malaquias romildo@uber.com.br Departamento de Computação malaquias@iceb.ufop.br Univ. Federal de Ouro Preto http://uber.com.br/romildo -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
