-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add jemalloc LD_PRELOAD to systemd drop-in file #3483
Comments
Comment from mhonek (@kenoh) at 2019-06-06 09:31:17 As Viktor pointed out, we should not preload jemalloc in case of ASAN build. Therefore, I would suggest to have a separate drop-in file doing this, which would then be installed only when necessary (similarly to xsan.conf, but in the other case). Also, seems like *-initconfig files are not necessary after the recent cleanup either. Changes along the patch attached should fix this. |
Comment from mhonek (@kenoh) at 2019-06-06 09:31:18 Metadata Update from @kenoh:
|
Comment from mreynolds (@mreynolds389) at 2019-06-06 14:29:42 I also have a working patch for this(needs some cleanup though), but preloading jemalloc must be the default behavior. |
Comment from mreynolds (@mreynolds389) at 2019-06-06 16:00:28 @kenoh do we still need those init files for non-systemd systems? It's going to complicate the spec file otherwise. |
Comment from mreynolds (@mreynolds389) at 2019-07-16 00:00:53 Filed #3557 We need to get this addressed one way or another, and sooner than later. I filed a PR but its just one of many ways we could solve this. |
Comment from mreynolds (@mreynolds389) at 2019-07-16 21:25:04 Commit 7466be33 relates to this ticket |
Comment from mreynolds (@mreynolds389) at 2019-07-16 21:28:57 Metadata Update from @mreynolds389:
|
Comment from mhonek (@kenoh) at 2019-07-17 15:08:44 Commit 76c0e75a relates to this ticket |
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50425
Issue Description
With the very recent changes to systemd we "lost" our LD_PRELAOD of jemalloc. We need to add it back to the new custom drop-in file
The text was updated successfully, but these errors were encountered: