[Bug 268711] 20 m default for /tmp – tmpmfs="YES" in rc.conf(5) – is too little for things such as ports-mgmt/pkg pkg-update( 8) and Electron-based applications

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268711

Graham Perrin <grahamperrin@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|maintainer-feedback?(pkg@Fr |
                   |eeBSD.org)                  |
           See Also|https://reviews.freebsd.org |
                   |/D28097,                    |
                   |https://reviews.freebsd.org |
                   |/D28209                     |
            Summary|ports-mgmt/pkg              |20 m default for /tmp –
                   |pkg-update(8) and           |tmpmfs="YES" in rc.conf(5)
                   |Electron-based applications |– is too little for things
                   |fail when /tmp is from      |such as ports-mgmt/pkg
                   |tmpmfs="YES" in rc.conf(5)  |pkg-update(8) and
                   |                            |Electron-based applications
                 CC|chromium@FreeBSD.org        |
                URL|https://cgit.freebsd.org/sr |https://www.freebsd.org/cgi
                   |c/tree/libexec/rc/rc.d/tmp  |/man.cgi?query=rc.conf&sekt
                   |                            |ion=5&manpath=FreeBSD

--- Comment #7 from Graham Perrin <grahamperrin@freebsd.org> ---
(In reply to Ceri Davies from comment #6)

Thanks!

I'll remove chromium@ from the CC list here. 

Also found, from
<https://lists.freebsd.org/pipermail/freebsd-current/2019-July/073881.html>: 

> … As to how we arrived at 20m, I recall an OSF/1 course where the 
> instructor intimated that 20m was industry best practice at the time 
> and OSF/1 being BSD. That was a lifetime ago. Maybe it's time to 
> consider a higher default for 2019. …

2007 bug 80907 comment 4 did consider POLA, albeit not with regard to size. 

----

Background: this bug report arose from #helpdesk and #storage discussions in
Discord, where advice to use tmpmfs did not (also) include advice to specify
tmpsize. The then assumption was that tmpmfs alone should work, subsequent
discovery of the 20 m default caused some astonishment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.