You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Created by mfriedrich on 2012-01-27 18:21:25 +00:00
Assignee: (none)
Status: Rejected (closed on 2012-03-04 12:36:13 +00:00)
Target Version: (none)
Last Update: 2012-03-04 12:36:13 +00:00 (in Redmine)
profiling the core remains difficult even when run in foreground. while profiling a cgi is mostly the same as debugging, the core forks, and more importantly, it drops root privilegues after startup.
profiling is somewhat different to debugging, because it uses a cache/out file which is created as root, but then tried to be written as icinga user.
this fails heavily, and in order not to have remove the drop_privilegues function when doing some profiling, it would be nice to have a switch on runtime, -debug or similar, where specialities like dropping privilegues does not happen because we know what we are doing and not running it in production.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2289
Created by mfriedrich on 2012-01-27 18:21:25 +00:00
Assignee: (none)
Status: Rejected (closed on 2012-03-04 12:36:13 +00:00)
Target Version: (none)
Last Update: 2012-03-04 12:36:13 +00:00 (in Redmine)
profiling the core remains difficult even when run in foreground. while profiling a cgi is mostly the same as debugging, the core forks, and more importantly, it drops root privilegues after startup.
profiling is somewhat different to debugging, because it uses a cache/out file which is created as root, but then tried to be written as icinga user.
this fails heavily, and in order not to have remove the drop_privilegues function when doing some profiling, it would be nice to have a switch on runtime, -
debug or similar, where specialities like dropping privilegues does not happenbecause we know what we are doing and not running it in production.Changesets
2012-01-27 18:55:50 +00:00 by mfriedrich 8f6b043
Relations:
The text was updated successfully, but these errors were encountered: