https://bugzilla.novell.com/show_bug.cgi?id=395402
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=395402#c22
Jiří Suchomel changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |behlert@novell.com, jsrain@novell.com,
| |coolo@novell.com
AssignedTo|jkupec@novell.com |jsuchome@novell.com
Status|NEEDINFO |ASSIGNED
Info Provider|lmuelle@novell.com |
--- Comment #22 from Jiří Suchomel 2008-10-30 06:34:52 MDT ---
We already show a message
"This change only affects newly created processes and not already running
services. Restart your services manually or reboot
the machine to enable it for all services."
in yast2-(samba|ldap)-client modules, but only when they are run on installed
system. The situation when they are running during installation (in the
configuration part, called 2nd stage) is different. Such popup may be shown,
but may be confusing, because the YaST configuration continues after samba/ldap
and there is no place for user to do manual restart.
I'll try to summarize the options of what could be done. Remember that the
precondition is that we are in 2nd stage of installation, configuring Samba (or
LDAP). The restart of dbus is required so it can get the current information
from NSS (see bug 174589). We have these options:
1. Tell user to restart after Samba/LDAP is configured. As written above,
probably too confusing.
2. restart dbus and fix the application that are not able to survive it (zypp).
Problem: probably too costly and we do not know all the problematic
applications.
3. restart dbus at the end of 2nd stage, after everything is configured and
YaST exits (and zypp is also closed). This looks nice, but currently we do not
have an API to postpone some action (e.g. restart of certain service) from the
middle of 2nd stage to the end. (But theoretically it should not be such a big
deal, proper testing of such a thing is required)
4. reboot the machine once the Samba/LDAP configuration is done: similar
situation to rebooting after installation of kernel in 2nd stage. We do have an
API for it, but we need to test it properly, of course.
5. reboot the machine at the end of 2nd stage
a) unconditionally, so we really know everything is in perfect state before
first login. Many users would oppose as it is very much windows-like and in
most cases probably needless.
b) only when Samba/LDAP was configured before: similar to 3, it is postponing
some action to the end of installation (also technical solution would probably
be similar).
6. implement 'reload' command for dbus init script, which would not cause the
problems to applications like zypp, but reload the correct information that
could have been changed (like the nsswitch info from bug 174589). I have no
idea if this is possible and how difficult would it be.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.