On Fri, 20 Aug 2004, Ara.T.Howard wrote:
> > NFS locks can get stale if you have network problems. The server loses the
> > client, the lock remains on the server, nobody can lock the file. Everyone
> > using NFS eventually runs into this, but good network setup and good kernel
> > choices can of
can you do this using passphrases in a manner that works across
reboots w/o embedding passphrases?
The authorization is stored either in RAM or on disk. Storing it in
RAM does not work across reboots on client side. Storing it on disk does.
Elmar
On Fri, 20 Aug 2004, Elmar Haneke wrote:
ssh only. period. nothing gets in or out except
on 22.
You can forward the database-access through an SSH-tunnel.
can you do this using passphrases in a manner that works across reboots w/o
embedding passphrases? i can't figure out how to - at some point
> ssh only. period. nothing gets in or out except
on 22.
You can forward the database-access through an SSH-tunnel.
additionally this system must be 24/7 and setting up HA setups for
postgresql is tricky (i've done it twice before).
Perhaps you should look at FirebirdSQL it is suitable for 24/7
On Fri, 20 Aug 2004, Matt Sergeant wrote:
Right, but regardless of what locking you ADD to the system, sqlite is still
going to do the lockd NFS locking itself. At least until you provide patches
to make NFS locking safe :-)
my current scheme, which may not be entirly fool proof, i first obtain a r
On 20 Aug 2004, at 15:45, Ara.T.Howard wrote:
i am wrapping any code that will grab a write
lock with an nfs safe lockfile creation to ensure only one process on
the
system will even ask for write locks at a time. this, suprisingly,
also gives
a massive performance boost as my timeout algorithim
On Fri, 20 Aug 2004, Andrew Piskorski wrote:
On Fri, Aug 20, 2004 at 08:45:06AM -0600, Ara.T.Howard wrote:
On Fri, 20 Aug 2004, Matt Sergeant wrote:
As far as linux -> nfs access goes it all depends on the quality of
the NFS implementation, and the kernel drivers you're using. It's
not easy to crea
On Fri, Aug 20, 2004 at 08:45:06AM -0600, Ara.T.Howard wrote:
> On Fri, 20 Aug 2004, Matt Sergeant wrote:
>
> >As far as linux -> nfs access goes it all depends on the quality of
> >the NFS implementation, and the kernel drivers you're using. It's
> >not easy to create a stable NFS locking system.
On Fri, 20 Aug 2004, Matt Sergeant wrote:
As far as linux -> nfs access goes it all depends on the quality of the NFS
implementation, and the kernel drivers you're using. It's not easy to create
a stable NFS locking system. We've had lots of problems with it. If you can,
go with local disk.
i canno
On 18 Aug 2004, at 23:13, Ara.T.Howard wrote:
has anyone out there used sqlite from a windows machine when the db
resided on
an nfs filesystem mounted using the windows nfs client? if so, does
it work?
have you attempted concurrent access from other windows machines?
other *nix
machines?
i'm
has anyone out there used sqlite from a windows machine when the db resided on
an nfs filesystem mounted using the windows nfs client? if so, does it work?
have you attempted concurrent access from other windows machines? other *nix
machines?
i'm considering an application where process from both
11 matches
Mail list logo