Peter Samuelson wrote:
[Olaf van der Spek]
But where does it check whether the service is supposed to run in the
current runlevel? I didn't see that check in the script itself.
It doesn't. No init script does. That is the job of invoke-rc.d.
invoke-rc.d decides whether to run the script or
I upgraded apache:
[REMOVE, NOT USED] libapr0
[INSTALL, DEPENDENCIES] apache2.2-common
[REMOVE, DEPENDENCIES] apache2-common
[UPGRADE] apache2 2.0.55-4.1 -> 2.2.3-3.1
[UPGRADE] apache2-mpm-prefork 2.0.55-4.1 -> 2.2.3-3.1
[UPGRADE] apache2-utils 2.0.55-4.1 -> 2.2.3-3.1
[UPGRADE] libapache2-mod-php4
Hi,
I did an upgrade of a simple setup of apache 2.0+php4 and it worked
quite well. The only issues were:
- the 000-default symlink was added to sites-enabled (see Bug#394462)
- there were some error messages that stopping apache failed (but it
was not running anymore when dpkg asked for confi
[Olaf van der Spek]
> >invoke-rc.d decides whether to run the script or not, based on the
> >current runlevel. invoke-rc.d always runs a script for 'reload' or
> >'force-reload' even if the runlevel doesn't include the service, but
> >the same is _not_ true for 'start' or 'restart'.
>
> What's t
Peter Samuelson wrote:
[Olaf van der Spek]
invoke-rc.d decides whether to run the script or not, based on the
current runlevel. invoke-rc.d always runs a script for 'reload' or
'force-reload' even if the runlevel doesn't include the service, but
the same is _not_ true for 'start' or 'restart'.
Your message dated Sun, 3 Dec 2006 00:56:25 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#399808: solved after php5 stuff updated to 5.2.0-7
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
6 matches
Mail list logo
