>A no_chroot flavour does seem reasonable, do you fancy sending a diff? I am staying out of ports matters.
>Changing to not chrooting by default is more problematic because >existing users will loose chroot (and may not notice this, especially >if updating from an OpenBSD version with nginx in base), and may need >to adjust the config file if they're using chroot-relative paths in it. Correct. The impact would be severe. The most important question of the conversation was: Why did nginx not accept a diff to add chroot to mainline? All of you, feel free to ask their developers. Yeah, I know this will come off as political. But this is a significant and intentional oversight in their software. Like removing syslog support. Perhaps if you want chroot, you have to pay extra?
