File Init Error: Cannot open output file. (Message 1 to 5 of 5)
From: Greg M Johnson
Subject: File Init Error: Cannot open output file.
Date: 12 Mar 2007 21:56:14
Message: <45f612ce@news.povray.org>
I've "suddenly" run into this problem with an animation.
It happens at the frames where I start accessing a bitmap to be used in a
pigment. It worked yesterday.
Any clues on debugging what this error message means?
From: Greg M Johnson
Subject: Re: File Init Error: Cannot open output file.
Date: 12 Mar 2007 22:07:14
Message: <45f61562@news.povray.org>
Whoa. My distro (kubuntu) apparently changed perms to r--r--r-- on the
previous renderings of these frames, and so wouldn't let me change it by
outputting on top of it. W.T.H.
A chmod 766 *.* took care of it.
Greg M. Johnson wrote:
> I've "suddenly" run into this problem with an animation.> It happens at the frames where I start accessing a bitmap to be used in a> pigment. It worked yesterday.> > Any clues on debugging what this error message means?
From: Leroy
Subject: Re: File Init Error: Cannot open output file.
Date: 12 Mar 2007 22:31:21
Message: <45F628E7.6010801@joplin.com>
Greg M. Johnson wrote:
> I've "suddenly" run into this problem with an animation.> It happens at the frames where I start accessing a bitmap to be used in a> pigment. It worked yesterday.> > Any clues on debugging what this error message means?
Has the bitmap change from yesterday?
I have gotten that error when I tried to access a corrupted bitmap.
Leroy <lrw### [at] joplincom> wrote:
> Greg M. Johnson wrote:> > I've "suddenly" run into this problem with an animation.> > It happens at the frames where I start accessing a bitmap to be used in a> > pigment. It worked yesterday.> >> > Any clues on debugging what this error message means?>> Has the bitmap change from yesterday?> I have gotten that error when I tried to access a corrupted bitmap.
I had rendered a set of frames from a large anim on this HDD and a set on
another.
CORRECTION: it wasn't choking when it hit a bitmap to be read, but when a
frame of the animation already existed on the HDD. And this
already-residing bitmap had r--r--r-- on it. I had gone through this
pattern of re-rendering the same exact ANIMFILE.POV dozens of times in the
past month without hitting a permissions problem.
One possibility is that the very last time I rendered the anim, I did so as
root. But I've seen other queeriness with permissions on kubuntu 6.10 that
I hadn't in other distro versions.