EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [BUGS] Bug #882: Cannot manually log in to database.
Giles Lean <[EMAIL PROTECTED]> writes:
> Either teach your /tmp cleaner not to clean out the socket files as
> Tom Lane suggested, or arrange to update the socket timestamps. I
Giles Lean <[EMAIL PROTECTED]> writes:
>>> utimes("/tmp/.s.PGSQL.5432", (const struct timeval *) 0);
>>
>> Hm, do you think that's portable?
> Hm ... yes, actually I do. I use it on HP-UX, and testing indicates
> that it works on FreeBSD, Linux, NetBSD and Tru64 as well.
> Thinking about it, a
Tom Lane <[EMAIL PROTECTED]> writes:
> Giles Lean <[EMAIL PROTECTED]> writes:
>
> > utimes("/tmp/.s.PGSQL.5432", (const struct timeval *) 0);
>
> Hm, do you think that's portable?
Hm ... yes, actually I do. I use it on HP-UX, and testing indicates
that it works on FreeBSD, Linux, NetBSD and
"Kinsey, Ben" <[EMAIL PROTECTED]> writes:
> Here's a little more detail as to how this socket file was getting deleted:
> On the system I'm using, if you attempt to start postmaster when an instance
> of it is already running, the socket file gets deleted. It was discovered
> that upon bootup of t
Giles Lean <[EMAIL PROTECTED]> writes:
> Either teach your /tmp cleaner not to clean out the socket files as
> Tom Lane suggested, or arrange to update the socket timestamps. I
> think it's easier to just keep updating the timestamps -- then I don't
> have to educate each new system administrator.
[ Where *did* that Reply-To: line come from -- it's broken ...
repl: bad addresses:
[EMAIL PROTECTED]; -- extraneous semi-colon
]
> Stopping and starting the postmaster daemon clears up this problem,
> but this problem creeps up about 2 times a week, and is a major
> annoyance.
Either
[EMAIL PROTECTED] writes:
> okapview# /opt/pgsql-7.1.3/bin/psql -U postgres -d AppliedView
> psql: connectDBStart() -- connect() failed: No such file or directory
> Is the postmaster running locally
> and accepting connections on Unix socket '/tmp/.s.PGSQL.5432'?
> Stopping and sta
