|
Bugzilla – Full Text Bug Listing |
| Summary: | KDM started too early | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Michael Stather <kontakt> |
| Component: | Basesystem | Assignee: | Dr. Werner Fink <werner> |
| Status: | RESOLVED WORKSFORME | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Michael Stather
2006-01-31 09:53:45 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.
|