Bug 115929 - sd-event-dispatch daemon is started even if apparmor is not started
Summary: sd-event-dispatch daemon is started even if apparmor is not started
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: AppArmor (show other bugs)
Version: RC 1
Hardware: Other All
: P5 - None : Normal
Target Milestone: RC 2
Assignee: Jesse Michael
QA Contact: Keiran Haggerty
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-08 17:40 UTC by Dominic W Reynolds
Modified: 2005-09-09 10:44 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dominic W Reynolds 2005-09-08 17:40:40 UTC 
The sd-event-dispatch daemon is started out of the post of subdomain-utils.
Jesse I think that we had chosen to leave this even with AA disabled. Can we
rethink and get a solution that starts the deamon when started from YaST and
still inits the event DB.

I guess this just leaves a window where rcsubdomain can be start/stopped but
doesn't start up the event daemon. 

What do you think?
Comment 1 Michael Matz 2005-09-08 18:41:33 UTC 
Btw. I don't understand the need for initializing any DB when AA is 
disabled.  And certainly just for initializing a DB there is no need 
for a process running in the background the whole time, stealing 
7MB memory for no good on a default install.  Btw. I consider this 
bug a blocker, not the other one (bug 115926).  CCing Andreas to decide.
Comment 2 Jesse Michael 2005-09-09 08:36:24 UTC 
we've removed the separate sd-event-dispatcher init script and made the main
subdomain init script start and stop this daemon so it won't run when subdomain
is disabled.

fixes are in our tree and are getting packaged up to be pushed into autobuild.
Comment 3 Dominic W Reynolds 2005-09-09 10:44:07 UTC 
Pushed to autobuild.