After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 136942 - why retry 4 times?
why retry 4 times?
Status: RESOLVED WONTFIX
Product: gdm
Classification: Core
Component: general
2.4.1.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2004-03-11 23:35 UTC by Jerome Haltom
Modified: 2004-05-29 01:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Description Jerome Haltom 2004-03-11 23:35:50 UTC 
Why does GDM need to retry 4 times to start the X server? Why would the
same server, with teh same configuration not work 3 times, but then work
the 4th?

It is totally annonying to have to sit and wait for it to start X 4 times
in the case of a problem. And I dont think it really could solve a problem:
so. I suggest it be set to 1 time.
Comment 1 George Lebl 2004-05-28 19:37:39 UTC 
I changed it to 3 times just today, but yes it does make sense to try more then
1 time because of possible races.  There are times when X will in fact start in
a few seconds when it can't start right away on system startup.  That's why it's
done.
Comment 2 Jerome Haltom 2004-05-29 01:54:16 UTC 
I don't get it. One can assume if one "starts X", it will do one of two things
a) successfully start or b) not. In the case of a, it may take an unknown length
of time for it to be ready to connect to. In the case of b, it will never happen.

What happens is that in the case of b, GDM starts X again. I don't see why it
can't just attempt to start X, and then attempt to connect to it for N number of
tries... no need to start another instance of the X server when it clearly
exited with an error code.

I must be missing something.