Univention Bugzilla – Bug 30514
lock for computerroom does not get released
Last modified: 2013-06-07 21:38:42 CEST
A customer had the problem that the lock for the computerroom module was not released after several days.
The only way i could reproduce this was to "kill -9 $PID_of_computerroom_module" when the teacher already left the computerroom module. Otherwise a update-request will immediately start a new process (which would release the lock after quiting). So this probably was caused due to a crash of the computerroom module (we had such cases caused by italc!?) when the teacher closed the computerroom module or selected another room in that moment.
The behavior was adapted to also write the process id of the umc computerroom module to the lockfile. If the pid does not run or is not an computerroom module process the lockfile will be overwritten by the new room owner.
*** Bug 31178 has been marked as a duplicate of this bug. ***
OK - not able to reproduce this behavior (even with "kill -9 $PID_of_computerroom_module") OK - PID is written to lock file OK - changelog
UCS@school 3.1 R2 has been released: http://download.univention.de/doc/release-notes-ucsschool-3.1-rev2.pdf If this error occurs again, please use "Clone This Bug".