Bug 515554 - Feature request: freenx-server initscript should support "status"
Summary: Feature request: freenx-server initscript should support "status"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: freenx-server
Version: 11
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Axel Thimm
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-04 18:09 UTC by Matt Castelein
Modified: 2009-12-18 04:34 UTC (History)
2 users (show)

Fixed In Version: 0.7.3-17.fc12
Clone Of:
Environment:
Last Closed: 2009-12-18 04:20:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matt Castelein 2009-08-04 18:09:47 UTC
The initscript for freenx-server currently does not have a status.  It would be nice if it did.  functions is already sourced so something like this would do it:

case "$1" in
  start)
        start
        ;;
  stop)
        stop
        ;;
  restart)
        restart
        ;;
  status)
	status nxagent
	;;
  *)
        echo $"Usage: $prog {start|stop|restart|status}"
        exit 1
esac

Comment 1 Matt Castelein 2009-08-04 18:56:49 UTC
I guess that was silly because "status nxagent" will only work if there is a connection, right?  But it would still be nice to have a status..

Comment 2 Matt Castelein 2009-08-04 19:03:04 UTC
Perhaps:

case "$1" in
  start)
        start
        ;;
  stop)
        stop
        ;;
  restart)
        restart
        ;;
  status)
        if [ -e "/var/lock/subsys/freenx-server" ]; then
          echo $"$prog is running"
        else
          echo $"$prog is stopped"
        fi
        ;;
  *)
        echo $"Usage: $prog {start|stop|restart|status}"
        exit 1
esac

Comment 3 Fedora Update System 2009-11-23 12:12:10 UTC
freenx-server-0.7.3-17.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/freenx-server-0.7.3-17.fc12

Comment 4 Fedora Update System 2009-11-23 12:12:34 UTC
freenx-server-0.7.3-17.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/freenx-server-0.7.3-17.fc11

Comment 5 Fedora Update System 2009-11-23 12:12:55 UTC
freenx-server-0.7.3-17.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/freenx-server-0.7.3-17.fc10

Comment 6 Fedora Update System 2009-11-25 14:54:48 UTC
freenx-server-0.7.3-17.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update freenx-server'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12032

Comment 7 Fedora Update System 2009-11-25 14:59:40 UTC
freenx-server-0.7.3-17.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update freenx-server'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-12041

Comment 8 Fedora Update System 2009-11-25 15:17:45 UTC
freenx-server-0.7.3-17.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update freenx-server'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-12123

Comment 9 Fedora Update System 2009-12-18 04:20:09 UTC
freenx-server-0.7.3-17.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2009-12-18 04:34:38 UTC
freenx-server-0.7.3-17.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


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