On Tue, Oct 20, 2015 at 2:07 AM, C. Brouerius van Nidek

wrote:

...

After the last update my system hang with the information that it could not proceed with the boot process because my /tmp was full. Skype with close to 100 entrances was one of the big users f /tmp but also chromium was well present. Deleted the /tmp content and got my system working again.

I remember that in former versions of SUSE the contents of /tmp could be controlled. Looked into Yast and could find this possibility. Could somebody point me out where to find this setting?

edit .let's say: /etc/tmpfiles.d/tmp-local.conf

v /tmp 1777 root root 10d v /var/tmp 1777 root root 30d

then..

mkdir -p /etc/systemd/system/local-fs.target.wants ln -s /usr/lib/systemd/system/tmp.mount /etc/systemd/system/local-fs.target.wants/tmp.mount

reboot. Thanks. That is close what was formerly supplied in Yast -- Linux User 183145 using KDE4 Tumbleweed on a Pentium IV ,

On Wednesday, October 21, 2015 10:22:46 PM Cristian Rodríguez wrote: powered by openSUSE 20151014 (x86_64) Kernel: 4.2.3-4.g549889b-default KDE Development Platform: 4.14.12 09:30am up 1 day 15:43, 2 users, load average: 0.58, 0.37, 0.25 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 22.10.2015 um 06:16 schrieb Cristian Rodríguez:

the second snippet will turn /tmp into an in-memory filesystem, so ensure you do not write huge files there if you are short of RAM!, be aware some buggy apps may still do that..(big files should go to /var/tmp instead! )

Firefox and Thunderbird does that per default. A privacy breach. If both would default to my encrypted ~/Download instead of the unencrypted /tmp ... Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Hello, On Oct 22 01:16 Cristian Rodríguez wrote (excerpt):

the second snippet will turn /tmp into an in-memory filesystem, so ensure you do not write huge files there if you are short of RAM!, be aware some buggy apps may still do that..(big files should go to /var/tmp instead! )

Applications that work in compliance with FHS can write as much as they like to /tmp/. Applications that work in compliance with FHS and do not want their temporary stuff to be preserved between system reboots cannot use /var/tmp/. See https://en.opensuse.org/openSUSE:Tmp_on_tmpfs#.2Ftmp.2F_versus_.2Fvar.2Ftmp.... I guess the above definition of "buggy apps" comes from systemd's way how the world has to behave to suffice their point of view. Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg)