On Sun, 2005-10-16 at 17:57, Ross Cathriner wrote: > HAPPY, HAPPY, JOY, JOY > > httpd how fully operational on MacOSX. Put another feather in your > hat.
> The full transscript can be viewed > here: http://homepage.mac.com/rnc/startup_log.txt > > The key factor is the --foreground, and terminal window must stay > open, with or without error printing. Maybe a problem with the way it > talks to stdout? Note a malloc warning at the end of the startup_log. > So daemon() call on MacOS X works in some other way compared to other systems? It's supposed to fork off the process into background and close stdout and stdin file-descriptors. Can you explain why you did "killall owhttpd" ? Isn't it enough to press Ctrl-C in the terminal windows, or does the program start in the background even if you start it with "--foreground" option? Perhaps it's working better for you if you put it in background with your shells "&" function instead. Then you should be able to close your terminal window I guess. Try something like: owhttpd --foreground --error_print=2 -u -p 3001 & (And then close the window.) Does it work? > These are things I can live with, because I'am a happy camper now. > Thanks for making this happen. > Ross > Houston, TX Nice to hear that it's possible to start it at least, but we might add some other arch-specific calls to make it work in both foreground and background on MacOS X... I don't know. When I find a MacOS X server with the development kit I'll make some more experiments. I should be able to find the free() bug I guess... I'll be back with more info about this. /Christian ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
