Description of problem: When ser cannot startup due to its ports already being opened by someone else, "service ser start" still reports "OK". Version-Release number of selected component (if applicable): ser-0.9.6-6.fc5 How reproducible: Every time. Steps to Reproduce: 1. Start software binding to port 5060, e.g. ekiga. 2. Run "service ser start" with a config binding to the same port. Actual results: "service ser start" reports "[ OK ]", but ser does not start. Expected results: "service ser start" reports "[ FAILED ]" as ser cannot start.
Marking as WONTFIX. ser exits with errorlevel 0 even if it is not starting up correctly. Upstream claimes, this will be fixed in the next major release...