 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I just accidentally destroyed a 14 hour render, by accidentally
repeating the render command--within seconds of it completing, so no
backup. Don't you hate when that happens?
I'm using GNU/Linux, where file undeletion requires a 3-credit semester
course to learn how to do it.
Do you with the 3 week renders ever have that problem?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25/08/2024 19:37, Cousin Ricky wrote:
> I just accidentally destroyed a 14 hour render, by accidentally
> repeating the render command--within seconds of it completing, so no
> backup. Don't you hate when that happens?
>
> I'm using GNU/Linux, where file undeletion requires a 3-credit semester
> course to learn how to do it.
>
> Do you with the 3 week renders ever have that problem?
It's sorrow, but not fatal - 14 hours is not too much. Just start it
again, go to bed, sleep, wake up, have a good breakfast, go for a walk,
get back and it will be ready !
--
YB
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25/08/2024 19:37, Cousin Ricky wrote:
> I just accidentally destroyed a 14 hour render, by accidentally
> repeating the render command--within seconds of it completing, so no
> backup. Don't you hate when that happens?
It's sorrowful, but not fatal - 14 hours is not too much. Just start it
again, go to bed, sleep, wake up, have a good breakfast, go for a walk,
get back and it will be ready !
--
YB
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Cousin Ricky <ric### [at] yahoo com> wrote:
> I just accidentally destroyed a 14 hour render, by accidentally
> repeating the render command--within seconds of it completing, so no
> backup. Don't you hate when that happens?
>
> I'm using GNU/Linux, where file undeletion requires a 3-credit semester
> course to learn how to do it.
>
> Do you with the 3 week renders ever have that problem?
Now it's time to learn how to make an automatic backup after each render. If you
take a moment chatgpt can create it for you.
BGimeno
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Cousin Ricky <ric### [at] yahoocom> wrote:
> I just accidentally destroyed a 14 hour render, by accidentally
> repeating the render command--within seconds of it completing, so no
> backup. Don't you hate when that happens?
Oh, I hear you my brother.
http://news.povray.org/povray.windows/thread/%3Cweb.5887512288c6897ec437ac910%40news.povray.org%3E/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25.08.2024 19:37, Cousin Ricky wrote:
> I just accidentally destroyed a 14 hour render, by accidentally
> repeating the render command--within seconds of it completing, so no
> backup. Don't you hate when that happens?
Sounds like you are complete computer novice and never pressed Ctrl+S
instead of Ctrl+Z before ;-)
With POVRay I have the opposite problem: parsing starts, takes time, and
stops and I'm going to search for the error, and all I see is
"interrupted by user".
"It's not a brake, it's slow full throttle".
--
Ilyich the Toad
https://dnyarri.github.io/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Cousin Ricky <ric### [at] yahoocom> wrote:
> I'm using GNU/Linux, where file undeletion requires a 3-credit semester
> course to learn how to do it.
Sorry to disappoint you, but there is no need for a dedicated course. You got
two options.
First one (under Linux Mint with Caja file manager) is found in the Edit menu,
option Undo (accessible by Ctrl+Z). After some delay, the last deleted
file should reappear ...
Second option is a bit more involving: open Trash in your file manager and sort
it by date (from newest to oldest). You could find the requested file near the
top of the list of files, which appears after a more or less long list of
folders.
The second option can help you recover a file deleted some time ago. The first
one is an immediate action.
I hope this will help you a little. BTW, no shame having fat fingers: it happens
to me from time to time !
Kelumden a.k.a. Vincent Dumont
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 27.08.2024 15:36, Kelumden wrote:
> The second option can help you recover a file deleted some time ago. The first
> one is an immediate action.
According to description provided, file was not deleted. File was
overwritten.
--
Ilyich the Toad
https://dnyarri.github.io/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2024-08-27 08:36 (-4), Kelumden wrote:
>
> First one (under Linux Mint with Caja file manager) is found in the Edit menu,
> option Undo (accessible by Ctrl+Z). After some delay, the last deleted
> file should reappear ...
If I had known 3 years ago what I know today, I would have bought a
Linux Mint machine. However, the KDE Dolphin file manager has the same
feature. Not that it matters; see below.
> Second option is a bit more involving: open Trash in your file manager and sort
> it by date (from newest to oldest). You could find the requested file near the
> top of the list of files, which appears after a more or less long list of
> folders.
The problem is that these only work if you delete the file via the file
manager, or via an app that uses the trash folder (such as Gwenview).
This file was deleted by POV-Ray as part of the process of rendering a
new image. It never went to the trash.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
Cousin Ricky <ric### [at] yahoocom> wrote:
> ...
> The problem is that these only work if you delete the file via the file
> manager, or via an app that uses the trash folder ...
has me wonder if, perhaps, using a filesystem which supports "snapshots"[*], one
could set up a trigger, to fire when POV-Ray closes the output file. (wild
speculation :-))
[*] like 'btrfs' and 'zfs'.
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
