I thought you may always fake config file by puting all params in a file, like this: -root c:\www -ports 80,443s ... etc etc
and then call shttpd like this: "shttpd `cat my_config.txt`" The "ps -ef" thing is a valid point. On one hand, it is cool that you can always see the arguments, instead have them hidden somewhere (I ran multiple times into trouble running shttpd and having it run wrong way - because it was shttpd.conf hanging around, left by somebody, I dont know who ..). On the other hand, it may be a security issue. If this is a security issue, I can see two ways: 1. modify the command line after start - this is hacky 2. add an option to read command line args from stdin - will work, but sort of ugly. The situation when you're out of space for command line arguments is possible, but I hardly can think it is realistic. People may use different shells, and yes, different shell expressions may result in different arguments passed to shttpd. To fight this, I would use /bin/sh shell wrapper rather then a config file. On the other hand, I really do not want to hurt any SHTTPD user; so if you think that the reasons above are not really valid, please say so! Keeping people unhappy is not what I want. ------------------------------------------------------------------------- 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/ _______________________________________________ shttpd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shttpd-general
