Re: How to configure (aka deal with) /tmp in the best way?

[DdB <debianlist@potentially-spam.de-bruyn.de>]

Am 05.10.2022 um 13:24 schrieb Greg Wooledge:
> You're going to have to figure out what's mounting your /tmp file system
> in the first place.  If it's not /etc/fstab then it could be a dedicated
> systemd unit, or a command in /etc/rc.local, or a crontab @reboot entry,
> or an /etc/init.d/ script, ....

Thx for the pointers. This is what i found:
> datakanja@NewSimul:/etc$ grep -wl tmp init.d/*
> init.d/vboxadd
> init.d/x11-common
> 
> datakanja@NewSimul:/etc$ ls rc.local
> ls: Zugriff auf 'rc.local' nicht möglich: Datei oder Verzeichnis nicht gefunden
> 

> datakanja@NewSimul:/etc$ grep -wrl tmp systemd/*
> systemd/system/tmp.mount
> 
> datakanja@NewSimul:/etc$ cat systemd/system/tmp.mount
> # Automatically generated by systemd-fstab-generator
> 
> [Unit]
> SourcePath=/etc/fstab
> Documentation=man:fstab(5) man:systemd-fstab-generator(8)
> Before=local-fs.target
> 
> [Mount]
> Where=/tmp
> What=tmpfs
> Type=tmpfs
> Options=defaults,size=50m,nosuid,mode=1777
> datakanja@NewSimul:/etc$ 

So this gives answer to the question, where that mount was coming from.
And the web also points to:

> Please note that using /etc/fstab is still the preferred approach with systemd!
> 
> See the man page for systemd.mount which states:
> 
>     In general, configuring mount points through /etc/fstab is the preferred approach.
> 
> systemd ships systemd-fstab-generator which converts those to mount units.

As an experiment, i removed that file and rebootet. Result: /tmp is no
longer a tmpfs. Was that your suggestion?