On Fri, Jan 26, 2001 at 11:55:16PM -0500, Bruce Momjian wrote:
> > I said:
> > > Yes, there are lots of systems that will clean /tmp --- and since the
> > > lock file is an ordinary file (not a socket) pretty much any tmp-cleaner
> > > is going to decide to remove it. I think that I had intended
"Oliver Elphick" <[EMAIL PROTECTED]> writes:
> /var/run/postgresql
There's another reason why the standard socket directory is /tmp,
and that's that it exists everywhere. Not all Unix systems even *have*
a /var hierarchy, let alone one that the admin will let you have a
playpen in.
Bruce Momjian wrote:
>> Note: programs that run as non-root users may be unable to create files un
>der
>> /var/run and therefore need a subdirectory owned by the appropriate user.
>
>This is the killer. We can't require root. Seems we are stuck with
>/tmp.
I'd be surprised to
> Jan Wieck wrote:
> >Peter Eisentraut wrote:
> >> Jan Wieck writes:
> >>
> >> > Exactly the way you want it to do (open(2) and close(2) of a
> >> > UNIX domain socket) was what I had to do to get an old
> >> > Mach3-4.3BSD combo into a kernel-panic.
> >>
> >> T
Jan Wieck wrote:
>Peter Eisentraut wrote:
>> Jan Wieck writes:
>>
>> > Exactly the way you want it to do (open(2) and close(2) of a
>> > UNIX domain socket) was what I had to do to get an old
>> > Mach3-4.3BSD combo into a kernel-panic.
>>
>> The lock file is an
On Fri, Jan 26, 2001 at 05:06:24PM -0500, Jan Wieck wrote:
> So the crazy-temp-vacuum-cleaner on linux doesn't touch the
> sockets?
The tmpwatch program that comes with many Linux distributions will only
unlink regular files and empty directories by default.
--
Bruce Guenter <[EMAIL PR
> I said:
> > Yes, there are lots of systems that will clean /tmp --- and since the
> > lock file is an ordinary file (not a socket) pretty much any tmp-cleaner
> > is going to decide to remove it. I think that I had intended to insert
> > a periodic touch of the lockfile and forgot to.
>
> Done
> On Fri, Jan 26, 2001 at 03:18:13PM -0500, Bruce Momjian wrote:
> > > The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
> > > file after the server has run 6 days. This will be a problem.
> > >
> > > We could touch (open) the file once every time the ServerLoop() runs
>
I said:
> Yes, there are lots of systems that will clean /tmp --- and since the
> lock file is an ordinary file (not a socket) pretty much any tmp-cleaner
> is going to decide to remove it. I think that I had intended to insert
> a periodic touch of the lockfile and forgot to.
Done now.
Peter Eisentraut wrote:
> Jan Wieck writes:
>
> > Exactly the way you want it to do (open(2) and close(2) of a
> > UNIX domain socket) was what I had to do to get an old
> > Mach3-4.3BSD combo into a kernel-panic.
>
> The lock file is an ordinary file.
So the crazy-temp-
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Bruce Momjian writes:
>> If we have to do it, let's make it an #ifdef __linux__ option.
> What does Linux have to do with it? FreeBSD does the same thing, only
> every three days. I dont' know whether it's not enabled on a fresh
> install, but it's
Bruce Momjian writes:
> If we have to do it, let's make it an #ifdef __linux__ option.
What does Linux have to do with it? FreeBSD does the same thing, only
every three days. I dont' know whether it's not enabled on a fresh
install, but it's there, you only need to flip the switch. I doubt /t
Jan Wieck writes:
> Exactly the way you want it to do (open(2) and close(2) of a
> UNIX domain socket) was what I had to do to get an old
> Mach3-4.3BSD combo into a kernel-panic.
The lock file is an ordinary file.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.
* Peter Eisentraut <[EMAIL PROTECTED]> [010126 12:11] wrote:
> The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
> file after the server has run 6 days. This will be a problem.
>
> We could touch (open) the file once every time the ServerLoop() runs
> around. It's not pe
Ross J. Reedstrom wrote:
> On Fri, Jan 26, 2001 at 03:18:13PM -0500, Bruce Momjian wrote:
> > > The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
> > > file after the server has run 6 days. This will be a problem.
> > >
> > > We could touch (open) the file once every time
On Fri, Jan 26, 2001 at 03:18:13PM -0500, Bruce Momjian wrote:
> > The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
> > file after the server has run 6 days. This will be a problem.
> >
> > We could touch (open) the file once every time the ServerLoop() runs
> > around.
> The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
> file after the server has run 6 days. This will be a problem.
>
> We could touch (open) the file once every time the ServerLoop() runs
> around. It's not perfect but it should work in practice.
If we have to do it, l
The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
file after the server has run 6 days. This will be a problem.
We could touch (open) the file once every time the ServerLoop() runs
around. It's not perfect but it should work in practice.
--
Peter Eisentraut [EMAIL
18 matches
Mail list logo
