Thorsten Froehlich wrote:
>>yes.  both to /root/.povray.conf and /home/myself/.povray.conf,
>>and they're mode 644, the user & group are also correct, i've
>>verified this more than once already... :/
> 
> Why don't you just delete both?

because if i do, i get:

----
# povray +I/usr/local/share/povray-3.5/scenes/lights/laser.pov +O/tmp/
Persistence of Vision(tm) Ray Tracer Version 3.5 Unix (.Linux.gcc)
   This is an official version prepared by the POV-Ray Team. See the
    documentation on how to contact the authors or visit us on the
    internet at http://www.povray.org/.
Copyright 1991-2002 POV-Ray Team(tm)
INI File Error: Reading from /usr/local/etc/povray.ini is not permitted.
Check the configuration in /usr/local/etc/povray.conf or ~/.povray.conf.
----

which is definitely one step back, i could at least
read the .ini file (and the scene .ini file) before...


r.

-- 
++ mailto:gim### [at] psicoch ++ http://www.psico.ch/ ++

Post a reply to this message

gimi wrote:
> which is definitely one step back, i could at least
> read the .ini file (and the scene .ini file) before...

oops, meant to say "the scene (.pov) file"

-- 
++ mailto:gim### [at] psicoch ++ http://www.psico.ch/ ++

Post a reply to this message

In article <3e70af8a@news.povray.org> , gimi <gim### [at] psicoch>  wrote:

> # povray +I/usr/local/share/povray-3.5/scenes/lights/laser.pov +O/tmp/
> Persistence of Vision(tm) Ray Tracer Version 3.5 Unix (.Linux.gcc)
>    This is an official version prepared by the POV-Ray Team. See the
>     documentation on how to contact the authors or visit us on the
>     internet at http://www.povray.org/.
> Copyright 1991-2002 POV-Ray Team(tm)
> INI File Error: Reading from /usr/local/etc/povray.ini is not permitted.
> Check the configuration in /usr/local/etc/povray.conf or ~/.povray.conf.

Assuming you really don't have some other incorrect configuration file
somewhere (I don't think so, you most likely have some file somewhere), this
would be a bug.  However, your problem much more likely sounds like some
messed up file somewhere.  The only question is how you managed to get the
file to wherever it is...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
> Assuming you really don't have some other incorrect configuration file
> somewhere (I don't think so, you most likely have some file somewhere), this
> would be a bug.  However, your problem much more likely sounds like some
> messed up file somewhere.  The only question is how you managed to get the
> file to wherever it is...

i can't think of any other place where i could put such a
configuration file, so povray would read it.  AFAIK povray
reads both /usr/local/etc/povray.conf and ~/.povray.conf, and
uses the settings that are more strict (at least this is
what the docs say - see below).

the docs are not really helpful, however, as they say
that the feature is not implemented at the moment:

----
1.4  I/O Restrictions
NOTE: I/O Restrictions are not yet available under POV-Ray for Unix 3.5, 
but will be available in a future minor release. The following 
documentation describes planned functionality.
----

anyway... i have now copied the original config content from
my first post in this thread back into vi, saved it, and copied
it to ~/.povray.conf again. - miraculously, it works now, so i
won't touch it again -- ever! ;)


thanks,

g.

-- 
++ mailto:gim### [at] psicoch ++ http://www.psico.ch/ ++

Post a reply to this message

> anyway... i have now copied the original config content from
> my first post in this thread back into vi, saved it, and copied
> it to ~/.povray.conf again. - miraculously, it works now, so i
> won't touch it again -- ever! ;)

	So here is what's wrong with your initial .povray.conf
file: there is 1 extra space caracter at the end of each line.
For instance, in your file you had:

"[File I/O Security] \n"
"none \n"

	while for some mysterious reason povray expects:

"[File I/O Security]\n"
"none\n"

	when it does string comparisons to parse the file. See the
UNIX_Process_Povray_Conf() function in src/unix.cpp. Obviously
the strcmp() should be at least strncmp(). I guess most of this
code is essentially a quick hack before something cleaner.

	- NC

Post a reply to this message

Nicolas Calimet wrote:
>     So here is what's wrong with your initial .povray.conf
> file: there is 1 extra space caracter at the end of each line.
> For instance, in your file you had:
> 
> "[File I/O Security] \n"
> "none \n"
> 

you are partly right, as the WS at EOL would indeed cause
povray to refuse to render (i tried it).

but i copied the message text into my editor again to check
this, and there appears to be no whitespace, but rather a
carriage return (\015) character, followed by the linefeed
(\012), as you would expect from a dos-ish text (i use
mozilla1.3b/win32 to read usenet).

the CRs *aren't* present in the unix files, however (verified
with hexdump), and it appears that vi removes CRs from DOS-
files upon writing (this might indeed have been the solution
for the problem in the first place).  i loaded one of them
into my win32-editor, switched from unix- to dos-text and
saved - guess what, povray does no longer render..

this should definitely not happen, neither because of white-
space in general, nor because of a CR in particular!

thank you for pointing this out, i hope that the pov-team
will fix this soon.


g.

-- 
++ mailto:gim### [at] psicoch ++ http://www.psico.ch/ ++

Post a reply to this message

This has been an excellent thread. I was having the same problems 
myself, and my sysadmin (who installed POV) couldn't help either. Thanks 
to this, it works now!

/ martin

Post a reply to this message