Bug 30468

Summary: add_fstab_entry: ignore loop* and ram* devices
Product: Z_Univention Corporate Client (UCC) Reporter: Felix Botner <botner>
Component: Client managementAssignee: Felix Botner <botner>
Status: CLOSED FIXED QA Contact: Erik Damrose <damrose>
Severity: normal    
Priority: P5 CC: gohmann, jmm, walkenhorst
Version: unspecified   
Target Milestone: UCC 1.0-errata   
Hardware: Other   
OS: Linux   
What kind of report is it?: --- What type of bug is this?: ---
Who will be affected by this bug?: --- How will those affected feel about the bug?: ---
User Pain: Enterprise Customer affected?:
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional):
Max CVSS v3 score:

Description Felix Botner univentionstaff 2013-02-15 13:54:19 CET
When booting a client add_fstab_entry is called about 25 times with ram* and loop* devices.

This leads to 25 times 

eval "$(univention-config-registry shell)"
if ! is_ucr_true 'ucc/mount'; then

which leads to a very high system load.

We can easly ignore ram* and loop* devices in add_fstab_entry before "ucr shell".
Comment 1 Felix Botner univentionstaff 2013-04-03 10:23:31 CEST
added a test to ignore ram* and loop* devices in add_fstab_entry, but usb stick's should still be mounted

2013-04-02-univention-ucc-remote-mount.yaml
Comment 2 Erik Damrose univentionstaff 2013-04-09 16:19:06 CEST
ram and loop devices are ignored in add_fstab_entry: OK
USB Sticks still mountable on thin- and desktop-image: OK
YAML: OK

-> Verified
Comment 3 Janek Walkenhorst univentionstaff 2013-04-24 17:26:24 CEST
http://errata.univention.de/ucc/1.0/4.html