init: support mandatory arguments, or prevent starting of tasks without any arguments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Triaged
|
Wishlist
|
Unassigned | ||
mountall (Ubuntu) |
Fix Released
|
High
|
Scott James Remnant (Canonical) | ||
upstart (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: upstart
Summary: initctl start mounted-tmp erased all my data in /
I am running a lucid installation in a linux-vserver instance. While fiddling with the really annoing issues regarding upstart and linux-vserver, I executed initctl start mounted-tmp to test if the script was working correctly.
The script took quite long, and after it finished, I discovered that it did not only clean /tmp, but all existing files on the whole machine.
My guess is that the variable $MOUNTPOINT is not set correctly when the script is being started manually, hence this happened in / instead of /tmp:
find . -depth -xdev $TEXPR $EXCEPT ! -type d -delete
find . -depth -xdev $DEXPR $EXCEPT -type d -empty -delete
I am currently busy getting all (well, most. meh! ) data back from my backups, so I havent had the time to reproduce the issue, will try do to so as soon as the vm is back up and running in another testmachine, but this might take some days.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: upstart 0.6.5-6
Uname: Linux 2.6.31-20-vserver i686
NonfreeKernelMo
Architecture: i386
Date: Wed Apr 7 09:52:32 2010
ProcEnviron: SHELL=/bin/bash
SourcePackage: upstart
Related branches
- Scott James Remnant (Canonical) (community): Disapprove
-
Diff: 12 lines (+1/-1)1 file modifiedconf/mounted-tmp.conf (+1/-1)
tags: | added: patch |
I can confirm this problem (completely updated Lucid). The behavior of the system when you delete all you files is acutally quite interesting, see attached screenshot.