Bug 130056

Summary:	rcsubdomain stop doesn't always stop sd-event-dispatch or tail -F
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Seth R Arnold <seth.arnold>
Component:	AppArmor	Assignee:	Jesse Michael <jmichael>
Status:	RESOLVED FIXED	QA Contact:	Dominic W Reynolds <dreynolds>
Severity:	Normal
Priority:	P5 - None	CC:	mrueckert
Version:	unspecified
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Seth R Arnold 2005-10-21 18:21:15 UTC

Marcus Rueckert reports that rcsubdomain stop doesn't always stop
sd-event-dispatch or the tail -F process that sd-event-dispatch uses for
listening. He strongly suggests using Perl's File::Tail module to replace our
execution of tail -- it is likely to make killing the sd-event-dispatch more
reliable.

Comment 1 Dominic W Reynolds 2006-01-31 00:09:28 UTC

Jesse is this something that has already been adressed?

Comment 2 Marcus Rückert 2006-02-07 12:17:42 UTC

i submitted a patch to your mailinglist for this.

Comment 3 Seth R Arnold 2006-02-07 18:36:49 UTC

Two approaches: (1) convert to using File::Tail (patch submitted by mrueckert, waiting on kukuk's opinion on including the File::Tail module in the 'default install' as well as additional testing) (2) sbeattie's already included patch to the initscript to pass -G to killproc.

Comment 4 Jesse Michael 2006-02-08 09:28:09 UTC

steve's initscript fix worked reliably in testing and has already been pushed to autobuild for beta4.

we're still hoping to get marcus' patch included as well to clean things up further, but that depends on getting the perl-File-Tail package included in CODE10.

however, i just noticed that this bug is filed against 10.0, not a 10.1 beta....  do we have a defined set of fixes we want to get batched up to go out as a 10.0 update?

Comment 5 Marcus Rückert 2006-02-08 12:22:55 UTC

thorsten said he has no problem with the patch and pulling in the package. :)

Comment 6 Jesse Michael 2006-04-05 10:05:01 UTC

this has been fixed in code10 for several betas.

do we want to do a maintanence release for 10.0?

Comment 7 Steve Beattie 2007-01-30 21:25:37 UTC

I don't believe we'll be issuing a fix for this on 10.0; it's been addressed in 10.1 and SLE10. Closing bug.