unmerge 224047 reopen 224047 tag 224047 - fixed-in-experimental tag 224047 thanks
Sorry, I merged that bug to another one which was not quite the same.
Jörgen Tegnér [2005-06-16 10:40 +0200]:
> G'day,
>
> when I upgraded today to
> postgresql-7.4 7.4.8-9 object-relational SQL database,
> version 7.4
> I noticed that the post-upgrade started the server. It didn't run before
> upgrading.
>
> May I suggest that the idea from ssh be used? That is, if a certain file
> exists, then don't try starting the server. Code below from my
> init.d/postgresql-7.4.
>
> check_for_no_start() {
> # forget it if we're trying to start, and /etc/ssh/sshd_not_to_be_run
> exists
> if [ -e /etc/ssh/sshd_not_to_be_run ]; then
> echo "OpenBSD Secure Shell server not in use
> (/etc/ssh/sshd_not_to_be_run)"
> exit 0
> fi
Hm, of course I won't check /etc/ssh/sshd_not_to_be_run in PostgreSQL.
:-) Also, such a tag file is evil (checking /etc/default/<package> is
the recommended way of doing such a thing).
Adding such a check to the init script is not really what you want
either. If you did that, you could not start the database manually any
more. If you want to disable a service in a particular runlevel,
remove the /etc/rcN.d/ symlink.
However, it should be possible to not start the postmasters if they
were not running before the upgrade; that's what you really want as
far as I can see. I'll look into that.
Martin
--
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntulinux.org
Debian Developer http://www.debian.org
signature.asc
Description: Digital signature
