6.0.0-git
2020-02-20

[#14985] After uninstall lock files remain
Summary After uninstall lock files remain
Queue Horde Base
Queue Version 5.2.21
Type Bug
State Unconfirmed
Priority 2. Medium
Owners
Requester jack (at) teleworm (dot) com
Created 2020-01-30 (21 days ago)
Due 01/30/2020 (21 days ago)
Updated 2020-01-30 (21 days ago)
Assigned
Resolved
Milestone
Patch Yes

History
2020-01-30 11:39:43 build+horde (at) de-korte (dot) org Comment #2 Reply to this comment
Which uninstall procedure do you mean? Could you provide a link?
2020-01-30 11:35:29 jack (at) teleworm (dot) com Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ After uninstall lock files remain
Due ⇒ 2020-01-30
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