6.0.0-beta1
7/6/25

[#14985] After uninstall lock files remain
Summary After uninstall lock files remain
Queue Horde Base
Queue Version 5.2.21
Type Bug
State No Feedback
Priority 2. Medium
Owners
Requester jack (at) teleworm (dot) com
Created 01/30/2020 (1984 days ago)
Due 01/30/2020 (1984 days ago)
Updated 03/12/2020 (1942 days ago)
Assigned
Resolved 03/12/2020 (1942 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch Yes

History
03/12/2020 08:14:57 PM Jan Schneider State ⇒ No Feedback
 
01/30/2020 11:39:43 AM build+horde (at) de-korte (dot) org Comment #2 Reply to this comment
Which uninstall procedure do you mean? Could you provide a link?
01/30/2020 11:35:29 AM jack (at) teleworm (dot) com Comment #1
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ After uninstall lock files remain
Due ⇒ 01/30/2020
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ Yes
Reply to this comment
After following the uninstall procedure mysql lock files remain.
Some function require less thann 125 locks per kernel (my 
understanding please check - anacron?)
therefore spurious locks could cause issues on the system (in my case 
amavisd-new fails randomly - for yet another reason!)

Therefore I am suggesting a note on the uninstall page to restart 
mysqld after uninstalling horde.
eg.
service mysqld restart
This clears the lock files.

run lslk to check the locks have gone


Saved Queries