summaryrefslogtreecommitdiffstats
path: root/etc
diff options
context:
space:
mode:
authorBrian Behlendorf <[email protected]>2011-03-07 10:10:20 -0800
committerBrian Behlendorf <[email protected]>2011-03-09 15:26:48 -0800
commit9ac97c2a939aef0f9899244920007c605387949a (patch)
treec6750083fbdebd56a657c8ce7e72f4ffc8b3bf96 /etc
parentd53368f6755ff67342f68e2e536c4157409fd047 (diff)
Print mount/umount errors
Because we are dependent of the system mount/umount utilities to ensure correct mtab locking, we should not suppress their error output. During a successful mount/umount they will be silent, but during a failure the error message they print is the only sure way to know why a mount failed. This is because the (u)mount(8) return code does not contain the result of the system call issued. The only way to clearly idenify why thing failed is to rely on the error message printed by the tool. Longer term once libmount is available we can issue the mount/umount system calls within the tool and still be ensured correct mtab locking. Closed #107
Diffstat (limited to 'etc')
0 files changed, 0 insertions, 0 deletions