Bug 146896 - KDM started too early
Summary: KDM started too early
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 2
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Dr. Werner Fink
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-31 09:53 UTC by Michael Stather
Modified: 2006-01-31 09:58 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Stather 2006-01-31 09:53:45 UTC
In the latest beta kdm is started before other services (e.g. network) on startup. IMHO this is wrong since KDM and the desktop started by it rely on all the other things and it´s theoretically possible that they haven´t come up at the time the desktop is started. KDM should (like in other SuSE versions) be started after all other services.
Comment 1 Dr. Werner Fink 2006-01-31 09:58:18 UTC
No, this is intentional. If your home would be mounted ovbe NFS
the kdm would be started after network and nfs import script.
Just do a

        ls -lG /etc/init.d/rc5.d/S*[kx]dm

as an example:

/suse/werner> ls -lG /etc/init.d/rc5.d/S*[kx]dm
lrwxrwxrwx 1 root 11 Jan 23 16:06 /etc/init.d/rc5.d/S01earlykdm -> ../earlykdm
lrwxrwxrwx 1 root  6 Jan 23 16:06 /etc/init.d/rc5.d/S08xdm -> ../xdm

as an eplanation, the earlykdm is an wrapper which calls after
some checks the xdm script.