2009/9/1 Taavi Sannik <[email protected]>: > Lazy wrote: > > I wouldn't mind having backwards compatibility, but perhaps we should > use something like create_default_senv(), which creates a server > environment with default values (eg min and max processors according to > the configuration). Currently if we would make a create_processor(), > then it would need a lot of arguments (min_processors, max_processors, > min_free_processors along with chroot and other stuff). > > With create_default_senv(), the old Processor function would create the > senv, add uid/gid, name and chroot to it and passes it on to the > child_add(). The new Processor function would use it pretty much the > same, except it just sets more options.
patch against head of trunk, if ServerEnvironment has 2 or 3 arguments it creates a default senv named user_groutp_chroot, all 0.3 functions as setting Max Processors after ServerEnv seems to work this patch needs some more work ( removing some code duplication from cf_processor and senv_init, accepting Processor user group chroot directive (doing nothing), some additional comments ) but I would like to hear any comments about this approach all seems to work on my OSX, testing and any comments are welcomed -- Lazy
peruser-0.3-compat.patch
Description: Binary data
_______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
