Hi,
I just updated my server's libssl1.0.0 package to 1.0.1e-2+deb7u6, and
the postinst code that restarts the daemons works pretty good:
libssl1.0.0:i386 (1.0.1e-2+deb7u6) wird eingerichtet ...
Checking for services that may need to be restarted...done.
Checking init scripts...
WARNING: init script for postgresql-9.1 not found.
Restarting services possibly affected by the upgrade:
Restarting SpamAssassin Mail Filter Daemon: spamd.
Restarting OpenBSD Secure Shell server: sshd.
Stopping NTP server: ntpd.
Starting NTP server: ntpd.
Stopping FreeRADIUS daemon: freeradius.
Starting FreeRADIUS daemon: freeradius.
Stopping MTA for restart: exim4_listener.
Restarting MTA: exim4.
Restarting Cyrus IMAPd: cyrmaster.
Stopping ClamAV virus database updater: freshclam.
Starting ClamAV virus database updater: freshclam.
Stopping ClamAV daemon: clamd Waiting . . .
Starting ClamAV daemon: clamd .
Stopping domain name service...: bind9Reloading Squid configuration files.
done.
waiting for pid 12176 to die
.
Starting domain name service...: bind9Reloading Squid configuration files.
done.
.
Services restarted successfully.
Unfortunately though, it overlooked the installed Apache server. I
believe this is due to the fact that
/var/lib/dpkg/info/libssl1.0.0:i386.postinst looks for a package
"apache2-common", but the name is in fact "apache2.2-common":
dev2.iserv.eu ~ # dpkg -S /etc/init.d/apache2
apache2.2-common: /etc/init.d/apache2
There are also a few other package names that seem to be outdated; for
example, aptitude doesn't find anything for apache-ssl or
libapache-mod-ssl. The whole list should probably be checked against the
Debian archive.
Oh, and the postgres init script is called /etc/init.d/postgresql, the
script seems to be looking for /etc/init.d/postgresql-9.1 and therefore
can't restart postgres either.
Martin
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
