Thanks changing the permissions on the folder solved the problem
--
View this message in context:
http://www.nabble.com/Data.fs.lock-permssions-error-t1273102.html#a3380103
Sent from the Zope - General forum at Nabble.com.
___
Zope maillist - Zope@zo
--On 13. März 2006 07:34:52 -0800 JulianRead <[EMAIL PROTECTED]>
wrote:
Hi i have just installed zope 2.8.6 on fedora core 3
I have created a zope instance however when i go to run this instane i get
the following error
IOError: [Errno 13] Permission denied:
'/home/default/inst1.isolve-un
+---[ JulianRead ]--
|
| Hi i have just installed zope 2.8.6 on fedora core 3
|
| I have created a zope instance however when i go to run this instane i get
| the following error
|
| IOError: [Errno 13] Permission denied:
| '/home/default/inst1.isolve-unix.co.uk/user/zope
On Thu, 29 Jun 2000 17:19:32 -0400, Shane Hathaway
<[EMAIL PROTECTED]> wrote:
>Quite simply, Data.fs is appended, not modified, except during a pack
>operation. Think of it like a binary log file. Therefore there are
>only two ways a simple, live backup of Data.fs can fail:
>
>1) You do the cop
On Thu, 29 Jun 2000, Wilkinson Charlie E wrote:
> This would be consistent with "atomic updates." What it means is
> that a transaction is not written to the Data.fs file until it has
> completed, and when it is finally written out, it's done as an
> atomic operation, i.e. at the system level it
Title: RE: [Zope] Backing Up Zope (was: Re: [Zope] Data.fs.lock?)
> -Original Message-
> From: Erik Enge [mailto:[EMAIL PROTECTED]]
>
> On Thu, 29 Jun 2000, Jeff K. Hoffman wrote:
>
> > It is my understanding that the ZODB on disk is always in a
> consistent
"Jeff K. Hoffman" wrote:
>
> On Thu, 29 Jun 2000, Erik Enge wrote:
>
> > On Thu, 29 Jun 2000, Jeff K. Hoffman wrote:
> >
> > > It is my understanding that the ZODB on disk is always in a consistent
> > > state; Jim has said, in the past, that you can simply make a copy of
> > > Data.fs, even whi
On Thu, 29 Jun 2000, Erik Enge wrote:
> On Thu, 29 Jun 2000, Jeff K. Hoffman wrote:
>
> > It is my understanding that the ZODB on disk is always in a consistent
> > state; Jim has said, in the past, that you can simply make a copy of
> > Data.fs, even while Zope is running, without problems.
>
> Wilkinson Charlie E wrote:
>
> Just to start by pointing out the bloody obvious:
>
> - Restoring from backup means you lose all data between
> backup date/time and system failure. Sucks, but it
> beats losing *all* your data. (RAID5 anyone?)
A) Please: no html!
B) I just had one weird
On Thu, 29 Jun 2000, Jeff K. Hoffman wrote:
> It is my understanding that the ZODB on disk is always in a consistent
> state; Jim has said, in the past, that you can simply make a copy of
> Data.fs, even while Zope is running, without problems.
But the Data.fs has to be updated sometimes. And i
On Thu, 29 Jun 2000, Wilkinson Charlie E wrote:
> Another random thought is that if ZODB transactions and
> writes are atomic, than none of this should be an issue.
> Anyone know the answer to that one?
It is my understanding that the ZODB on disk is always in a consistent
state; Jim has said, i
Title: RE: [Zope] Backing Up Zope (was: Re: [Zope] Data.fs.lock?)
Just to start by pointing out the bloody obvious:
- Restoring from backup means you lose all data between
backup date/time and system failure. Sucks, but it
beats losing *all* your data. (RAID5 anyone?)
- With that in
On Thu, 29 Jun 2000, Chris Withers wrote:
> Hmm, about extending this so you have 'rotating data.fs files' in the
> same way you have rotating log files?
In general, yes :-). Do you think it would be solving the right problem
the right way?
> Definitely, but I think it also needs to be solved
Erik Enge wrote:
>
> On Thu, 29 Jun 2000, Chris Withers wrote:
>
> > Hmm, about extending this so you have 'rotating data.fs files' in the
> > same way you have rotating log files?
>
> In general, yes :-). Do you think it would be solving the right problem
> the right way?
I think so, but tha
On Wed, 28 Jun 2000, Erik Enge wrote:
> >Pack and backup Data.fs.old.
>
> But what if the site is incredibly busy and transactions
> are going on _all the time_? And can you automate the
I beleive packing works fine in this situataion.
> Pack function? (If I wanted to do it during the
Erik Enge wrote:
> One could possibly have a function that put new transactions in a new
> file, and then - when told it was ok to do so - it could update the
> regular data.fs file.
Hmm, about extending this so you have 'rotating data.fs files' in the
same way you have rotating log files?
> Act
On Thu, 29 Jun 2000, Chris Withers wrote:
> Would this whole problem go away if Zope had a 'backup data.fs' funcion
> internally that could keep all transactions in memory while the
> appopriate files were copied?
It would, but keeping it in memory would be a bad thing. Say your data.fs
file wa
Erik Enge wrote:
>
> On Wed, 28 Jun 2000, Oleg Broytmann wrote:
>
> > On Wed, 28 Jun 2000, Chris Withers wrote:
> > >
> > > So, how should we backup data.fs without stopping Zope and ensuring the
> > > integrity of our data all the while?
> >
> >Pack and backup Data.fs.old.
>
> But what if
cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [Zope] Data.fs.lock?
06/28/00
On Wed, 28 Jun 2000, Oleg Broytmann wrote:
> On Wed, 28 Jun 2000, Chris Withers wrote:
> >
> > So, how should we backup data.fs without stopping Zope and ensuring the
> > integrity of our data all the while?
>
>Pack and backup Data.fs.old.
But what if the site is incredibly busy and transac
On Wed, 28 Jun 2000, Chris Withers wrote:
> So, how should we backup data.fs without stopping Zope and ensuring the
> integrity of our data all the while?
Pack and backup Data.fs.old.
Oleg.(All opinions are mine and not of my employer)
Oleg Broytmann Foundation for
Erik Enge wrote:
> How would you do it? In Unix you can't check if the file is being
> read to (can you?), so if you start backing up a 2GB Data.fs file
> and then the Zope process starts writing to it, you'll have garbage :-).
I don't think you'd have garbage since it's just transactions beign
On Wed, 28 Jun 2000, Chris Withers wrote:
> I'd say it's definitely a problem if you have to stop zope to do a
> backup :(
How would you do it? In Unix you can't check if the file is being
read to (can you?), so if you start backing up a 2GB Data.fs file
and then the Zope process starts writing
L PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [Zope] Data.fs.lock?
>
>
> Toby Dickenson wrote:
> > It's definitely normal, and arguably a problem.
>
> > net stop zope
> > copy c:/zope/var/data.fs c:/zope/var/backupdata.fs
> > net start zope
>
&
Toby Dickenson wrote:
> It's definitely normal, and arguably a problem.
> net stop zope
> copy c:/zope/var/data.fs c:/zope/var/backupdata.fs
> net start zope
I'd say it's definitely a problem if you have to stop zope to do a
backup :(
But then, I'd say it's a problem running (Zope on) Windows i
On Tue, 27 Jun 2000 16:30:30 -0500, [EMAIL PROTECTED] wrote:
>The tech that does backups on my new NT server (IIS) tells me that
>everything backs up ok except the \var\Data.fs.lock file.
>Is that normal or a problem?
It's definitely normal, and arguably a problem.
On Windows, any file opened f
26 matches
Mail list logo
