kdm upstart profile network awareness
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kde-workspace (Ubuntu) |
Expired
|
Wishlist
|
Unassigned | ||
Bug Description
kdm should be started later, after Networking is up and Remote Filesystems are also up.
Reason: in Enterprise environments a Desktop system is used by non-admin users. After showing up the logon screen an successful logon of a user must be possible.
Nearly all Linux Entrerprise Desktops are using IMHO NIS+NFS. So an user Logon may show/usable after User Athorisation (NIS) and the User $HOME (normally served as NFS) is avaible.
in /etc/init/kdm.conf should read as follow:
----- x----x----x----
[ ... ]
start on ((filesystem
and runlevel [!06]
and local-filesystems and remote-filesystems and net-device-up
and started dbus
and (drm-device-added card0 PRIMARY_
or stopped udev-fallback-
or runlevel PREVLEVEL=S)
[...]
This closes here also Bug #599812 (NIS Problem).
BTW: It silences the Helpdesk lines dramatically ...
| Jürgen Sauer (juergen-sauer) wrote | #1 |
| Harald Sitter (apachelogger) wrote | #2 |
| Changed in kde-workspace (Ubuntu): | |
| importance: | Undecided → Wishlist |
| status: | New → Incomplete |
| summary: |
- kdm upstart profile + kdm upstart profile network awareness |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in kde-workspace (Ubuntu): | |
| status: | Incomplete → Expired |
This would potentially downgrade startup performance on "common" desktop installations making it not a particularly lovely change unfortunately.
We have discussed this a bit and here are some thoughts on the matter:
a) the change as is is not qualifying for default behavior
b) however since kdm is no longer default it could be the enterprise opt-in to use kdm over lightdm, continuing to focus on the regular home desktop with lightdm and kdm for enterprise
c) have a secondary package upstart-kdm-network (for example) that provides a config with the presented changes, as an admin one would then simply have to install and select the right config (this approach would also be portable to lightdm)
d) leave it as it is. seeing as there is a known workaround and upstart configs will not simply be overwritten on an upgrade so carrying along a delta to the stock package config is entirely possible if perhaps not entirely convenient
thoughts welcome