Bug 619089 - portreserve service is always reported as "running"
Summary: portreserve service is always reported as "running"
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: portreserve
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-28 14:34 UTC by Denys Vlasenko
Modified: 2011-06-24 18:34 UTC (History)
1 user (show)

Fixed In Version: portreserve-0.0.4-6.fc13
Clone Of:
Environment:
Last Closed: 2010-11-18 17:53:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Denys Vlasenko 2010-07-28 14:34:51 UTC
# service portreserve stop
Stopping portreserve: 

# service portreserve status; echo $?
portreserve is stopped
0

# service portreserve status; echo $?
portreserve is stopped
0

Compare this with other services, say, ip6tables:

# service ip6tables stop
ip6tables: Flushing firewall rules:                        [  OK  ]
ip6tables: Setting chains to policy ACCEPT: filter         [  OK  ]
ip6tables: Unloading modules:                              [  OK  ]
# service ip6tables status; echo $?
ip6tables: Firewall is not running.
3


Among other things, this makes the service "unstoppable" in GUI service
config (System->Administration->Services): you can press on "stop" button
however many times you like, the service is still "running". One side effect of
bogus "running" status is that it can not be *started* using GUI: GUI thinks it
already is, and "start" button is greyed out!

Comment 1 Fedora Update System 2011-06-24 18:34:02 UTC
portreserve-0.0.5-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/portreserve-0.0.5-1.fc15

Comment 2 Fedora Update System 2011-06-24 18:34:42 UTC
portreserve-0.0.5-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/portreserve-0.0.5-1.fc14


Note You need to log in before you can comment on or make changes to this bug.