A tiny smatters of Linux distro are smushing both /tmp and /var/tmp. That one is never a good idea, not even in production servers nor embedded world. /tmp ge

A tiny smatters of Linux distro are smushing both /tmp and /var/tmp. That one is never a good idea, not even in production servers nor embedded world. /tmp gets emptied with each reboot. /var/tmp is about surviving across reboot. But the app would run just fine if it were ever to be emptied. # Alternatively Some have said that /var/cache would be the more appropriate use over /var/tmp. But /var/cache is used for daemon cold restart and reconstruction of internal structures after reboot, restart, reload, or worse, Ethernet cable disconnect under only systemd-networkd (daemon gets killed by systemd). Your prized networked daemon falls into this category. /var/tmp is generally for session-specific (that are expected to survive across reboot) as opposed to daemon’s internal structure. ISC DHCP client is one.