Hide Forgot
Description of problem: Are these all supposed to be executed by the admin or user? Or are some of them just used by other apps? Should some of them be moved to /usr/libexec? How many of them are launched from init scripts?
(In reply to comment #0) > Are these all supposed to be executed by the admin or user? Or are some of > them just used by other apps? Should some of them be moved to /usr/libexec? > - this is a bit difficult to decide, there is a use-case for all of these binaries where it makes sense to run them manually by admin or user - but right now they are mostly run by abrt > How many of them are launched from init scripts? only abrt-dump-oops
(In reply to comment #0) > Description of problem: > > Are these all supposed to be executed by the admin or user? They all may be executed by user in the process of analyzing or reporting a problem. > How many of them are launched from init scripts? One: abrt-dump-oops. It also may be used by a user in order to extract oopses from arbitrary files. Imagine a setup where /var/log/messages from a server farm are copied to central server and processed, looking for oopses... > Should some of them be moved to /usr/libexec? I don't think so.
(In reply to comment #1) > (In reply to comment #0) > > Are these all supposed to be executed by the admin or user? Or are some of > > them just used by other apps? Should some of them be moved to /usr/libexec? > > - this is a bit difficult to decide, there is a use-case for all of these > binaries where it makes sense to run them manually by admin or user > - but right now they are mostly run by abrt Well, in the same way you may say that "yum is run by shell" when you type "yum ..." - because shell performs fork+exec. Ultimately, yum is run by you, the user. Similarly, abrt-actions are run by user, mediated by GUI or CLI and event config files.
Ok we added policy for oops to be able to run as a helper and helpers to run out of initrc_t.