Re: postgres install fails on sid
On 19:14 Sun 07 Oct , Florian Kulzer wrote:
> On Sun, Oct 07, 2007 at 16:35:44 +0000, John Masters wrote:
> > On 16:04 Sun 07 Oct, Florian Kulzer wrote:
> > > On Sun, Oct 07, 2007 at 13:49:11 +0000, John Masters wrote:
> > > > I have posted this to the Postgres list also.
> > > >
> > > > Cannot get Postgres 8.2 working on Debian sid using the Debian package.
> > > > At the config stage I get a message telling me to run:-
> > > >
> > > > pg_createcluster 8.2 main --start
> > > >
> > > I would start with the first problem that is reported: "sh: /dev/null:
> > > Permission denied". What are the permissions of the /dev/null node on
> > > your system? It should be writable by anyone:
> > >
> > > $ ls -l /dev/null
> > > crw-rw-rw- 1 root root 1, 3 2007-10-07 14:28 /dev/null
> > >
> > Thanks, that seems to be the problem. permissions for /dev/null
> > are -rw-r--r--
> > What is the c part of the permissions and how do you set it? I have
> > googled and searched my books but all I can find is that it is a
> > character device file but no mention of how to set the attribute.
> The "c" means that it is a special file to begin with; you cannot just
> set this property for an existing normal file. Such special files used
> to be created with the "mknod" command, but nowadays udev should take
> care of their creation.
> > Would it be OK to just chmod 666?
> The permission error will probably be gone then, but it would still be a
> normal file and not a real /dev/null, which is used to dump the output
> of all sorts of commands that are called in scripts. (The job of
> /dev/null is to swallow input without a trace.)
I've chmod 666 /dev/null and now postgres installs OK. However I
hesitate to go further as this server is on a VPS. Could that be why the
perms were not set properly? I have been running this server for about 3
weeks just with a basic mail setup - Postfix/Courier/Procmail passing
all mail through Spamassassin on another server, so some of the obvious
spam I have been sending to /dev/null which seems to work. I am
unfamiliar with the deployment of VPS's, I just use them, so I assume
this should have been setup when the VPS was created.