please set /run/shm/snaps/@{APP_PKGNAME}/@{APP_VERSION}/ for apps
Bug #1443612 reported by
Jamie Strandboge
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snappy |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
Like we do with /tmp, we should also setup app-specific directories in /run/shm. I'm adding the following to the default policy:
/{dev,
/{dev,
/{dev,
/{dev,
as such, '/{dev,
Related branches
| description: | updated |
| Changed in snappy-ubuntu: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
Revision history for this message
| John Lenton (chipaca) wrote Re: [Bug 1443612] Re: please set /run/shm/snaps/@{APP_PKGNAME}/@{APP_VERSION}/ for apps | #1 |
| affects: | snappy-ubuntu → snappy |
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #2 |
| Changed in snappy: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
If apps are going to get their own /tmp/, shouldn't we do the same
with /dev/shm/ ?
The manpage says the argument to shm_open should be an object name of
the form /somename; adding a directory in there seems to be off-spec
(it'll work, no doubt, because it's just a filename on a tmpfs,
but...)
Maybe, if they don't get their own /dev/shm, we want to override
shm_open and friends to prepend that?
(things creating files in /dev/shm by hand deserve to keep the pieces
when things break, but people doing it properly should carry on
working, surely?)
On 29 April 2015 at 09:25, Michael Vogt <email address hidden> wrote:
> ** Changed in: snappy-ubuntu
> Status: New => Confirmed
>
> ** Changed in: snappy-ubuntu
> Importance: Undecided => High
>
> --
> You received this bug notification because you are a member of Snappy
> Developers, which is subscribed to snappy-ubuntu.
> https:/
>
> Title:
> please set /run/shm/
>
> To manage notifications about this bug go to:
> https:/