On Thu, Aug 14, 2003, Michael Schloh wrote:
> Modified files:
> openpkg-src/mico mico.spec rc.mico
> openpkg-web news.txt
>
> Log:
> Complete for compliance with features described by ticket #202
>
>[...]
>
> +%pre
> + # before upgrade, save status and stop service
> + [ $1 -eq 2 ] || exit 0
> + eval `%{l_rc} mico status 2>/dev/null | tee %{l_tmpfile}`
> + %{l_rc} mico stop 2>/dev/null
> + exit 0
> +
> +%post
> + if [ $1 -eq 2 ]; then
> + # after upgrade, restore status
> + eval `cat %{l_tmpfile}`; rm -f %{l_tmpfile}
> + [ ".$mico_active" = .yes ] && %{l_rc} mico start
> + fi
> + exit 0
> +
> +%preun
> + # before erase, stop service
> + [ $1 -eq 0 ] || exit 0
> + %{l_rc} mico stop 2>/dev/null
> + exit 0
>
This is sort of troubling because of how MICO works. As soon as the name
service daemon quits, all of its servant bindings are lost. To regain them
(after it starts again in %post), the external CORBA servants have to
reregister themselves.So I guess I'm asking myself if we should make an exception and not stop the MICO daemons on package upgrades, or at least provide a conditional choice to the administrator? -- [EMAIL PROTECTED] Development Team, Operations Northern Europe Cable & Wireless Telecommunications Services GmbH
pgp00000.pgp
Description: PGP signature
