# \[Buildroot\] \[autobuild.buildroot.net\] Your daily results for 2021-02-04

- From: Yann E. MORIN \<hidden\>
- Date: 2021-02-05 21:34:53 
- List: buildroot
- Page: https://ratatoskr.run/buildroot/2021/02/11655458
- Thread: https://ratatoskr.run/buildroot/2021/02/11655438/t.md

```text
Peter, All,

On 2021-02-05 19:35 +0100, Peter Korsgaard spake thusly:
> >>>>> "Heiko" == Heiko Thiery [ref] writes:
>  >> mipsel    |        netopeer2-1.1.53        | http://autobuild.buildroot.net/results/da0e36543cf68e4e9bbe819945a884193f33819a
[--SNIP--]
>  > So I see here 3 possible solutions:
>  > 1. do the PRE_INSTALL_HOOK to remove the files every time (disclaimed by Yann).
>  > 2. remove this files by hand (no long term solution).
>  > 3. disable the installation of the yang modules .. but then we have a
>  > non functional installation available and we leave the installation of
>  > the yang modules to the user.
> 
> Ideally the package should be fixed to create those files in
> $DESTDIR/dev/shm rather than mess around with the host /dev/shm.
> 
> But as /dev/shm is not persistent, how does this work at runtime? What
> do those files do exactly?

They are shared memory.

From shm_overview(7):

    On Linux, shared memory objects are created in a (tmpfs(5)) virtual
    filesystem, normally mounted under /dev/shm. [...]

There is in fact nothing wrong in creating such shm objects during the
build.

What is wrong, is leaving them lingering about...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
```