Bug 112707 - race between earlykdm and xdm init scripts
Summary: race between earlykdm and xdm init scripts
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 2
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Stephan Kulow
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-24 13:41 UTC by Takashi Iwai
Modified: 2005-09-06 07:29 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Takashi Iwai 2005-08-24 13:41:39 UTC 
earlykdm and xdm init scripts can be racy.

It might be harmless in practice, but better to use a lock file (e.g.
/var/lock/subsys/xdm) ?

As another optimization, we can extend startpar to skip the service which has
the certain lock in /var/lock/subsys...
Comment 1 Dr. Werner Fink 2005-08-24 13:47:19 UTC 
Do you have ever seen such a race?
Comment 2 Takashi Iwai 2005-08-24 13:52:58 UTC 
Yes, I saw yesterday the line "starting kdm" twice during boot.  No real problem
happend, though.

The booted services are fairly optimized by myself, so this should happen very
unlikely per default installation, I guess.
Comment 3 Dr. Werner Fink 2005-08-24 13:56:54 UTC 
A simple solution would be to add earlykdm to
Should-Start line of the /etc/init.d/xdm.
Comment 4 Stephan Kulow 2005-08-24 14:51:43 UTC 
It would still say "starting kdm" twice during boot.
Comment 5 Stephan Kulow 2005-09-06 07:29:21 UTC 
it's fixed good enough now