On May 21, 2006, at 8:30 AM, Luis Lavena wrote: >>>> Why better we don't start leaving these new options to the config >>>> file >>>> and keep params to the minimum? >> >> Since both mongrel_rails and mongrel_cluster support config file >> generation, we still need a way to specify what options to write to >> the config file. > > My concern is that -u is user in win32 to set the processor affinity, > and some user that follow win32->linux path will found issues with > their declarations on how mongrel should be running.
I agree and that's why I removed -u and -g. My point is that we still need to add options to support configuration file generation. However, I think we can prevent name clashes by only using long option names like --user and --group. > Also, I'll be adding options for user context to the service stuff, > what will allow run a mongrel service on accounts different than > LocalService. You should be able to add --user/--group and not have any conflicts. The question is whether Process::GID and Process::UID are supported on Win32. The Ruby doc describes them as "a collection of module functions which can be used to portably get, set, and switch the current process’s real, effective, and saved group IDs." Although I don't know if the "portably" part includes Win32. If not, it should be possible to add a platform check in Mongrel::Configurator::change_privilege that calls ImpersonateSecurityContext (or similar function) instead. > Its a excelent work Brad, and I think we should keep differences in > params between platform to the minimun, so docs don't get a lot of > "this only works on posix" "this stuff don't work on win32", "this is > for my poor win32 machine" and so on. Thanks. I agree. Regards, Bradley Taylor ------ Rails Machine Simplified Ruby on Rails application deployment http://railsmachine.com _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
