On Wed, May 7, 2008 at 7:59 PM, Vasiljevic Zoran <[EMAIL PROTECTED]> wrote: > > On 07.05.2008, at 19:15, Vlad Seryakov wrote: > >> Once you started the server, it is not Tcl package anymore, need >> nscp to >> access it. > > > Depends. If you think in the box, yes. If you step out > of the box then yes and no. > > What I actually think is to marry the rw-config module > with the code and make the server configuration from > Tcl. Say, each new virtual server gets its own Tcl > command that can be used to modify the config on the > fly etc.pp. The whole idea is still in a very very > rudimentary state. What I would like to achieve is > really to get more people evaluate the server by > simply snap-in the package and fire-up one or more > virtual servers. All under exteral (Tcl) control. > > This would mean some considerable re-plumbing in > ns_main.c but it ls doable. Allright, perhaps > some more plumbing... >
Some kind of ns_daemon command as a module, incorporating all the startup guts such as the forking into the background, session id stuff, changing user/group, chroot, windows service/unix watchdog. That would be a genuinely useful standalone Tcl module, and might actually clean up some of the startup code. So 'nsd' would be a Tcl script which parses the command line, calls ns_daemon -user .. -group .. -chroot .. (or whatever) and then jumps into the main main libnsd binary. The 'daemon' stuff seems to be a logical chunk of functionality. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
