Bug 30421 - vm-writeback gets overwritten after being set in upstart script ucc-base
vm-writeback gets overwritten after being set in upstart script ucc-base
Status: CLOSED FIXED
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: Hardware and device support
unspecified
Other Linux
: P5 normal
: UCC 1.0
Assigned To: Moritz Muehlenhoff
Erik Damrose
: interim-4
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-13 14:17 CET by Erik Damrose
Modified: 2013-03-26 09:14 CET (History)
1 user (show)

See Also:
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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2013-02-13 14:17:01 CET
ucc-base sets two sysctl values on a thinclient: 
/proc/sys/vm/dirty_expire_centisecs
/proc/sys/vm/dirty_writeback_centisecs
After normal system boot dirty_writeback_centisecs is however set to its default value 500. If the upstart script is called manually, the value is set back to 10.
Comment 1 Moritz Muehlenhoff univentionstaff 2013-02-13 14:22:07 CET
We should set this in a LightDM session setup script.
Comment 2 Moritz Muehlenhoff univentionstaff 2013-02-13 14:45:15 CET
The configuration of the writeback settings has been moved into the session setup script, which already tightens the permissions of /run/drives.
Comment 3 Erik Damrose univentionstaff 2013-02-13 15:40:02 CET
The writeback settings are set to the correct values after a succesful login -> OK

-> Verified
Comment 4 Moritz Muehlenhoff univentionstaff 2013-03-26 09:14:00 CET
UCC 1.0 has been released: 
http://forum.univention.de/viewtopic.php?f=26&t=2417
http://forum.univention.de/viewtopic.php?f=54&t=2418

If this error occurs again, please use "Clone This Bug".