aplexus (jhz) 126: ./bwdemo
file open failed
while executing
"mk::file open mk4vfs1 ./bwdemo -nocommit"
(eval body line 1)
invoked from within
"eval [list mk::file open $db $file] $args"
.....
I downloaded source and rebuilt tclkit for solaris and linux. I got the
same results on both. The rebuilt version for solaris runs fine, but the
linux version has the exact same problem. I get the same results using:
plexus (jhz) 1267: tclkit bwdemo
Any ideas?
I really like (love?) the tclkit concept, and have built some special
documents using it for solaris and windows, but need linux to work.
--
============================
John H. Zouck
The Johns Hopkins University
Applied Physics Laboratory
============================
> I have downloaded binaries for tclkit, and run the binaries on Solaris
> and Windows XP with no problem. However, on linux (red hat 6.0 and 7.1
> both) I have a problem running tclkit with scripted documents, although
> it works fine as a standalone shell. I get:
>
> aplexus (jhz) 126: ./bwdemo
> file open failed
> while executing
> "mk::file open mk4vfs1 ./bwdemo -nocommit"
> (eval body line 1)
> invoked from within
> "eval [list mk::file open $db $file] $args"
> .....
Hm, could be a protection issue. Make sure you try it first with mode
writable (chmod 777 bwdemo), because scripted docs currently get opened
r/w by default.
I'm about to reverse that default to r/o, because there probably is a
way to start that way and re-open r/w when modifications are to be made.
In the meantime, you can force a scripetd document to open r/o with the
following incantations:
sdx sd2fs bwdemo
sdx fs2sd bwdemo -readonly
(You need a recent version of sdx for this to work)
> I really like (love?) the tclkit concept, and have built some special
(Aha, a convert! ... :)
> documents using it for solaris and windows, but need linux to work.
I've just verified that bwdemo works with my copy of tclkit on Linux,
and it definitely is supported (I develop tclkit mostly on Linux).
-jcw
That was the problem. Over the weekend I changed permissions to 777 from 555
and things worked as expected.
This scripted document approach is a great idea and has much promise,
althought in my case I plan to use it first to 'wrap' applications that
might not be called documents exactly. I appreciate all the work you and the
community has put into the tclkit, kitten, etc.
Thanks for the help.
Jean-Claude Wippler wrote:
--