donaldcallen at gmail.com
Fri Apr 2 17:44:58 UTC 2010
I do note that the README.SBo says "make sure rc.postgresql is
executable", which I overlooked on first reading. I still think this
is a bug, or at least an inconvenience. Why require the user to add
execute permission? The installation should just take care of it.
On Fri, Apr 2, 2010 at 12:25 PM, Donald Allen <donaldcallen at gmail.com> wrote:
> Here's another one, given that I performed so brilliantly on the first
> The postgresql page says:
> "Before you can run postgresql you'll need to create the database;
> please see README.SBo."
> README.SBo instructs you to add
> # Startup postgresql
> if [ -x /etc/rc.d/rc.postgresql ]; then
> /etc/rc.d/rc.postgresql start
> to /etc/rc.d/rc.local. But this doesn't work (the postgres server
> doesn't start) because /etc/rc.d/rc.postgresql doesn't have execute
> permission after installing the postgresql package that results from
> running postgresql.SlackBuild.
> Simply doing the obvious
> chmod +x /etc/rc.d/rc.postgresql
> in a root shell fixes the problem, but, of course, that shouldn't be
> necessary. I think the SlackBuild script, or, more likely, its
> associated doinst.sh, or the permissions on the
> postgresql/rc.postgresql.new (644) that results from from un-tarring
> the downloaded postgresql.tar.gz needs a little tweaking.
More information about the SlackBuilds-users