I took another look at my duplicate bug and there is a solution to this included that is quite simple. Not sure why it is such a hard thing to change one item (start on mounted MOUNTPOINT=/tmp ==> start on local-filesystems) in the /etc/init/mounted-tmp.conf upstart job to fix this.
"The problem seems to happen using a separate /usr partition.
According to /etc/init/mounted-tmp.conf, cleaning starts when /tmp is mounted:
start on mounted MOUNTPOINT=/tmp
However, the script needs /usr/bin/find to cleanup /tmp. Cleanup is failing since /usr is not there (is not mounted) when cleaning starts. Therefor, /tmp is never cleaned
Changing it to:
start on local-filesystems
solved the problem. The cleanup is only started when all local file systems are mounted.
I took another look at my duplicate bug and there is a solution to this included that is quite simple. Not sure why it is such a hard thing to change one item (start on mounted MOUNTPOINT=/tmp ==> start on local-filesystems) in the /etc/init/ mounted- tmp.conf upstart job to fix this.
https:/ /bugs.launchpad .net/ubuntu/ +source/ mountall/ +bug/602723
Quote from duplicate bug:
"The problem seems to happen using a separate /usr partition.
According to /etc/init/ mounted- tmp.conf, cleaning starts when /tmp is mounted:
start on mounted MOUNTPOINT=/tmp
However, the script needs /usr/bin/find to cleanup /tmp. Cleanup is failing since /usr is not there (is not mounted) when cleaning starts. Therefor, /tmp is never cleaned
Changing it to:
start on local-filesystems
solved the problem. The cleanup is only started when all local file systems are mounted.
I can confirm that this change does work."