On Wed, Apr 15, 2015 at 4:07 PM, Matthew Miller mattdm@mattdm.org wrote:
On Wed, Apr 15, 2015 at 03:55:34PM -0500, Les Mikesell wrote:
Is there a generic way that processes written to share files with (say) apache in /tmp can figure out that they are running on an OS with systemd and in that case, where the daemon in question thinks /tmp is?
For example, twiki has a backup/restore add-in where the backup part is normally done from cron with a command line script but the resulting archives that go in /tmp are supposed to be seen in the web interface where you can choose and restore from them. How should that have been written so the file lands where systemd has remapped /tmp for httpd if it happens to be running on a host with systemd?
Why does this directory have to be /tmp rather than a specific directory belonging to twiki?
Twiki is a perl web application run under apache. It doesn't have its own uid. It doesn't 'have' to be anywhere in particular but that is the way it was written and thus has very confusing results when trying to move it to CentOS 7. Is there some generic approach to fixing this kind of breakage (that is, to make it work and not confusing, not to say it was broken as designed)? To function as a backup, it probably shouldn't default to being in the same directory as the files it backs up.