Tracey Emery <tra...@traceyemery.net> wrote: > On Tue, Apr 07, 2020 at 11:17:23AM -0400, Bryan Steele wrote: > > On Tue, Apr 07, 2020 at 04:56:31PM +0200, Martijn van Duren wrote: > > > This came up during u2k20 while discussing tempfiles for gotweb inside a > > > chroot. At the moment we don't include it by default and ports have to > > > create it themselves. Since I assume we want web applications to run > > > inside a /var/www chroot as much as possible and even some libc > > > functions depend on /tmp being available I'd argue we should include it > > > by default. > > > > WIth FastCGI, perhaps I'm confused, but why do web applications need to > > be inside the /var/www chroot? Can't they be anywhere, or even have a > > seperate chroot directory? Should we be handling things things that > > are not in base? > > Both slowcgi(8) and httpd(8) chroot to /var/www and are set to the www > user. The idea was to have /var/www/tmp created by default, but with > www:www ownership. This would eliminate multiple ports from creating the > directory and allow daily to clean the dir. > > To Theo's point, how was /var/tmp used in the past that it caused > problems? I'm struggling to find any info in past mailing lists.
Please, please, please why don't you try it. Create the directory. Now as a user, completely fill it. Now your /var is full. Just do it, on an actual machine. Actually do it, don't just talk about it. Now be observant and consider the consequences. This isn't rocket science.
