Bug 10835 - stap-stop-server doesn't work for failed starts
Summary: stap-stop-server doesn't work for failed starts
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: runtime (show other bugs)
Version: unspecified
: P2 enhancement
Target Milestone: ---
Assignee: Dave Brolley
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-23 15:01 UTC by Charley
Modified: 2010-03-08 20:31 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

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 Charley 2009-10-23 15:01:44 UTC 
If an avahi publish server doesn't start, sending the SIGTERM to stap-serverd
appears to do nothng, but terminating the stap-gen-cert will cause stap-serverd
to stop as well. (If the publish server does start, terminating stap-serverd
will kill everything, as intended.)

Also, it would be nice if stap-stop-server without any PID arguments given would
still terminate a stap-server if only one instance of stap-server is running.
Comment 1 Dave Brolley 2010-03-08 20:31:41 UTC 
These issues have been addressed long ago by enhancements to stap-start-server
and the stap-server initscript.