[opensuse-packaging] insserving services
Hi, some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2007-10-26 21:27:43 +0200, Jan Engelhardt wrote:
some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files?
http://en.opensuse.org/Packaging/SUSE_Package_Conventions/RPM_Macros#3.6._.2... -y sets START variables to “yes” by default. It is ignored if X-UnitedLinux-Default-Enabled is specified in the init script. -Y forces setting the START variable to “yes”. This means the service is always activated regardless of the setting before an update. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Oct 26 2007 21:47, Marcus Rueckert wrote:
On 2007-10-26 21:27:43 +0200, Jan Engelhardt wrote:
some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files?
http://en.opensuse.org/Packaging/SUSE_Package_Conventions/RPM_Macros#3.6._.2...
-y sets START variables to “yes” by default. It is ignored if X-UnitedLinux-Default-Enabled is specified in the init script. -Y forces setting the START variable to “yes”. This means the service is always activated regardless of the setting before an update.
Right, and how can that ideally fly without recompiling the package? Trying to spin a suse derivate (makesusedvd) where apache should be started by default. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fr 26 Okt 2007 22:12:49 CEST Jan Engelhardt
-y sets START variables to “yes” by default. It is ignored if X-UnitedLinux-Default-Enabled is specified in the init script. -Y forces setting the START variable to “yes”. This means the service is always activated regardless of the setting before an update.
Right, and how can that ideally fly without recompiling the package? Trying to spin a suse derivate (makesusedvd) where apache should be started by default.
What about creating a "dummy" package which prerequires apache and has %fillup_and_insserv -Y apache ? Other solution: use AutoYast (because this is what autoyast is for)... Greetings, Lars --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, Jan Engelhardt wrote:
some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files?
PreReq: %insserv_prereq ... %post %{fillup_and_insserv -f scriptname} ... %postun %insserv_cleanup Packages which are not enabled by default don't have that. (There are more parameters handling upgrades from SuSE Linux before 8.0 but I don't think you need those) Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2007-10-26 21:48:55 +0200, Wolfgang Rosenauer wrote:
Jan Engelhardt wrote:
some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files?
PreReq: %insserv_prereq ... %post %{fillup_and_insserv -f scriptname}
according to http://en.opensuse.org/Packaging/SUSE_Package_Conventions/RPM_Macros#3.6._.2... is -f skips the fillup part. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Marcus Rueckert wrote:
On 2007-10-26 21:48:55 +0200, Wolfgang Rosenauer wrote:
Jan Engelhardt wrote:
some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files? PreReq: %insserv_prereq ... %post %{fillup_and_insserv -f scriptname}
according to http://en.opensuse.org/Packaging/SUSE_Package_Conventions/RPM_Macros#3.6._.2... is -f skips the fillup part.
True. He asked about how "insserving" is handled and not fillup ;-) Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2007-10-26 22:31:57 +0200, Wolfgang Rosenauer wrote:
Marcus Rueckert wrote:
On 2007-10-26 21:48:55 +0200, Wolfgang Rosenauer wrote:
Jan Engelhardt wrote:
some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files? PreReq: %insserv_prereq ... %post %{fillup_and_insserv -f scriptname}
according to http://en.opensuse.org/Packaging/SUSE_Package_Conventions/RPM_Macros#3.6._.2... is -f skips the fillup part.
True. He asked about how "insserving" is handled and not fillup ;-)
sure but the point was "how to enable the service on installation. that is -y. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag, 26. Oktober 2007 21:27:43 schrieb Jan Engelhardt:
Hi,
some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files?
Lokk into the SUSE Packaginig Conventions at http://en.opensuse.org/Packaging/SUSE_Package_Conventions . The macros %fillup_and_insserv, %insserv_cleanup, %insserv_force_if_yast and %restart_on_update and the Chapter about init scripts are what you need. Herbert --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (5)
-
Herbert Graeber -
Jan Engelhardt -
Lars Vogdt -
Marcus Rueckert -
Wolfgang Rosenauer