Bug 194278 - Port net/quagga: rc.d/quagga script not working properly
Summary: Port net/quagga: rc.d/quagga script not working properly
Status: Closed Not A Bug
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: Mathieu Arnold
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-09 20:42 UTC by Ricardo
Modified: 2015-02-17 14:56 UTC (History)
0 users

See Also:

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 Ricardo 2014-10-09 20:42:46 UTC 
After installing the net/quagga port and setting the quagga_enable="NO" in /etc/rc.conf the /usr/local/etc/rc.d/quagga script tries to start the daemons. If quagga_enable="YES" then it works as expected.

# egrep quagga /etc/rc.conf
quagga_enable="NO"
quagga_daemons="zebra ripd ospfd"

# /usr/local/etc/rc.d/quagga status
Cannot 'status' zebra. Set quagga_enable to YES in /etc/rc.conf or use 'onestatus' instead of 'status'.
Cannot 'status' ripd. Set quagga_enable to YES in /etc/rc.conf or use 'onestatus' instead of 'status'.
Cannot 'status' ospfd. Set quagga_enable to YES in /etc/rc.conf or use 'onestatus' instead of 'status'.

# /usr/local/etc/rc.d/quagga
[: =: unexpected operator
[: =: unexpected operator
[: =: unexpected operator
Usage: /usr/local/etc/rc.d/quagga [fast|force|one|quiet](start|stop|restart|rcvar|enabled|configtest|status|poll)

# /usr/local/etc/rc.d/quagga start
Checking zebra.conf
OK
Cannot 'start' zebra. Set quagga_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.
Checking ripd.conf
OK
Cannot 'start' ripd. Set quagga_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.
Checking ospfd.conf
2014/10/09 17:37:56 OSPF: ASBR[Status:1]: Update
2014/10/09 17:37:56 OSPF: ASBR[Status:2]: Update
2014/10/09 17:37:56 OSPF: ASBR[Status:2]: Already ASBR
2014/10/09 17:37:56 OSPF: ASBR[Status:3]: Update
2014/10/09 17:37:56 OSPF: ASBR[Status:3]: Already ASBR
OK
Cannot 'start' ospfd. Set quagga_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.

# /usr/local/etc/rc.d/quagga onestart
Starting zebra.
Starting ripd.
Starting ospfd.
2014/10/09 17:38:12 OSPF: ASBR[Status:1]: Update
2014/10/09 17:38:12 OSPF: ASBR[Status:2]: Update
2014/10/09 17:38:12 OSPF: ASBR[Status:2]: Already ASBR
2014/10/09 17:38:12 OSPF: ASBR[Status:3]: Update
2014/10/09 17:38:12 OSPF: ASBR[Status:3]: Already ASBR

# /usr/local/etc/rc.d/quagga onestop
Stopping zebra.
Waiting for PIDS: 62355.
Stopping ripd.
Waiting for PIDS: 18584.
Stopping ospfd.
Waiting for PIDS: 96746.

# vi /etc/rc.conf (setting to yes)
# egrep quagga /etc/rc.conf
quagga_enable="YES"
quagga_daemons="zebra ripd ospfd"

# /usr/local/etc/rc.d/quagga status
zebra is not running.
ripd is not running.
ospfd is not running.

# /usr/local/etc/rc.d/quagga 
[: =: unexpected operator
[: =: unexpected operator
[: =: unexpected operator
Usage: /usr/local/etc/rc.d/quagga [fast|force|one|quiet](start|stop|restart|rcvar|enabled|configtest|status|poll)

# /usr/local/etc/rc.d/quagga start
Checking zebra.conf
OK
Starting zebra.
Checking ripd.conf
OK
Starting ripd.
Checking ospfd.conf
2014/10/09 17:40:48 OSPF: ASBR[Status:1]: Update
2014/10/09 17:40:48 OSPF: ASBR[Status:2]: Update
2014/10/09 17:40:48 OSPF: ASBR[Status:2]: Already ASBR
2014/10/09 17:40:48 OSPF: ASBR[Status:3]: Update
2014/10/09 17:40:48 OSPF: ASBR[Status:3]: Already ASBR
OK
Starting ospfd.
2014/10/09 17:40:48 OSPF: ASBR[Status:1]: Update
2014/10/09 17:40:48 OSPF: ASBR[Status:2]: Update
2014/10/09 17:40:48 OSPF: ASBR[Status:2]: Already ASBR
2014/10/09 17:40:48 OSPF: ASBR[Status:3]: Update
2014/10/09 17:40:48 OSPF: ASBR[Status:3]: Already ASBR

# /usr/local/etc/rc.d/quagga stop
Stopping ospfd.
Waiting for PIDS: 25800.
Stopping ripd.
Waiting for PIDS: 47923.
Stopping zebra.
Waiting for PIDS: 55664.
Comment 1 Bugzilla Automation freebsd_committer freebsd_triage 2014-10-09 20:42:46 UTC 
Maintainers CC'd
Comment 2 Mathieu Arnold freebsd_committer freebsd_triage 2015-02-17 14:56:59 UTC 
I've read all that carefully, and what you describe is the normal way for the port to operate, so, closing this.