/etc/init/mounted-tmp.conf uses find, which is in /usr/bin

[Steve Langasek]

Binary package hint: mountall

On every boot, the console here shows a message that the mounted-tmp.conf job has exited with error code 127, because it relies on /usr/bin/find for cleaning /tmp and I have /usr as a separate filesystem.

Either this needs to be implemented without find, or find needs to be moved to /bin, or the job needs to somehow wait until both /usr and /tmp are mounted.

ProblemType: Bug
Architecture: amd64
Date: Wed Feb 17 18:17:52 2010
DistroRelease: Ubuntu 10.04
Package: mountall 2.5
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SourcePackage: mountall
Uname: Linux 2.6.32-13-generic x86_64

[Scott James Remnant (Canonical) (canonical-scott)]

Will not be fixed in Lucid, move back to tracking in "head"

[Joshua (joshudson)]

Or make /tmp a tmpfs filesystem

[Frederick J. Henderson (frederickjh)]

Sorry, I am bit new to this bug filing game what does *move back to tracking in "head"* mean?

[Frederick J. Henderson (frederickjh)]

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."

[Robbie Williamson (robbiew)]

Hi Fredrick, so are you confirming this issue still happens in Maverick? Or just trying to get it fixed in a lucid update.

[Frederick J. Henderson (frederickjh)]

No, confirmation for Maverick, but I think it would be wise to have a Lucid update. I have fixed my machine with the solution above.

Hopefully if this is too hard to implement in an update or against some rules because it is an LTS release, that folks can at least find the answer here.

[Scott James Remnant (Canonical) (canonical-scott)]

The solution you suggest is not a fix, since then it would mean that /tmp is being cleaned up while other parallel processes are potentially adding to it.

There isn't a known good fix for this yet

[Antti Miranto (software-antti)]

How about:
start on (mounted MOUNTPOINT=/tmp and mounted MOUNTPOINT=/usr)

Somehow this mounted-tmp.conf has to block others until it has done.

[Djoko (djk-srs)]

I use Ubuntu Karmic. I also experienced the same problem, which I never knew before. Problems arise when doing a new installation, and I make a /tmp on another partition, separate from / (root), the files in /tmp is never deleted. I have to delete them manually