Bug 137698

Summary:	Poststart-Skript of SCPM / Profile-Manager is not executed when choosing profile with grub
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Tob Sch <Tob_Sch>
Component:	Basesystem	Assignee:	Joachim Gleissner <joachim.gleissner>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Tob Sch 2005-12-08 22:49:41 UTC

A configured Poststart-Skript of a profile is not executed / is not working when I choose a different profile within grub boot menue at boot time.
When I change the profile within KDE (at runlevel 5 time), it is executed / is working without any problems.

Comment 1 Joachim Gleissner 2005-12-09 10:46:41 UTC

It's the intended behaviour. In boot mode, there is no start phase, therefore no start scripts are executed. Do you have specific needs to run scripts when a profile gets restored only?

Comment 2 Tob Sch 2005-12-09 15:29:15 UTC

I don't mean the simple restore case.
I change the profile within the grub boot menu by pressing F2, after that F3 and select the new profile, which is different from the actual profile.

Here is an example:
The computer has booted with profile 1 (e.g. at work). After that, I do a "shutdown -h".
After some time (hours, days), I want to boot with profile 2 (e.g. at home) by changing the actual profile 1 to profile 2 within the grub boot menu (I don't want to do it later after logging into KDE and using the "Profile Chooser" for a profile change).

Comment 3 Joachim Gleissner 2005-12-09 15:53:41 UTC

Selecting a profile in the boot menu results in this "simple restore case". SCPM only restores the saved resources, it does not start or stop any services, because this will be done by the regular init scripts later. So your poststart script does not get executed in that case. Could you please explain why this is a problem?

Comment 4 Tob Sch 2005-12-09 16:33:06 UTC

I had to change a parameter of a special configuration file dependent on the profile name.
I know, that I can solve that problem on a different way (e.g. bring some "if ... sed ... /proc/cmdline ... then ... fi" statements in the startup script of the daemon), but I expected from a comfortable profile manager with the possibilty to configure 4 kinds of pre- and post-scripts to pass through the same procedures during a profile change, independent wether the profile change is initiated before or after a desktopmanager or windowmanager is started.
For me, this behaviour is not very logical, because other files (e.g. in /etc/sysconfig/network) are copied in both cases, if you change the profile with grub or kde.

Comment 5 Joachim Gleissner 2005-12-09 16:46:47 UTC

How about adding that configuration file as a normal file resource? Seems to me much more reasonable than modifying it in the poststart script.

IMHO opinion it's not illogical to not run the poststart script at this point. As I said before, SCPM does not (and must not) start services when restoring a profile the system is going to boot into. Therefore it can't run the poststart script. It may run the prestart script, but this is currently also not done. I see no objections against permitting it, so I'll change scpm to do so.

Comment 6 Tob Sch 2005-12-09 20:17:05 UTC

Thank you very much for changing scpm.

You are right, for changing configuration files it's faster to define a new  resource or a new resource group.
Nevertheless, when a pre- or post-script is needed, the enhancement for scpm makes sense.

Comment 7 Joachim Gleissner 2006-02-09 16:35:38 UTC

Oops, forgot to close this bug. SCPM as in CVS and on 10.1 betas always run the prestart scripts.