Re: How to watch what wsapi.exe does?

[Gilles Ganault <gilles.ganault@...>]

On Thu, 20 May 2010 18:49:47 +0200, steve donovan
<steve.j.donovan@gmail.com> wrote:
>This makes sense if you consider how require() works. First it uses
>the package.path pattern to find Lua modules, and _if that fails_,
>look for binary modules using the package.cpath pattern. So it can't
>find 'lfs.lua', but then successfully finds 'lfs.dll', and likewise
>for the LuaSocket DLLs.

Indeed: After manually copying the following files/directories...
===========
Directory of C:\TEMP
<DIR>          socket
<DIR>          wsapi
<DIR>          xavante
coxpcall.lua
hello.lua
lfs.dll
wsapi.exe
wsapi.lua
xavante.lua
===========

... I started wsapi.exe, only to have it barf the following error
message:
===========
C:\TEMP>wsapi -9999
lua: fatal error: `[string "..."]:145: attempt to call field
'start_message' (a
nil value)
stack traceback:
        [string "..."]:145: in main chunk'
Content-type: text/plain

Configuration fatal error: see error log!
[string "..."]:145: attempt to call field 'start_message' (a nil
value)
stack traceback:
        [string "..."]:145: in main chunk
===========

So I copied wsapi.lua for the LfW directory, ran "wsapi -p9999", and
it started OK:
===========
C:\TEMP>wsapi -p9999
[Xavante launcher] Starting Xavante...
[2010-05-20 18:58:55] Xavante started on port(s) 9999
===========

Still, I'd like to run a monitoring application while I exercise
wsapi, to make sure I don't some file/directory/Reg entry that could
produce some nasty error after this application is out there. I'll see
if I can find something.

Meanwhile, I'll see how to add SQLite to the mix.

Thanks again.