1 # This file tells the frr package which daemons to start.
3 # Sample configurations for these daemons can be found in
4 # /usr/share/doc/frr/examples/.
8 # When activating a daemon for the first time, a config file, even if it is
9 # empty, has to be present *and* be owned by the user and group "frr", else
10 # the daemon will not be started by /etc/init.d/frr. The permissions should
12 # When using "vtysh" such a config file is also needed. It should be owned by
13 # group "frrvty" and set to ug=rw,o= though. Check /etc/pam.d/frr, too.
15 # The watchfrr, zebra and staticd daemons are always started.
37 # If this option is set the /etc/init.d/frr script automatically loads
38 # the config via "vtysh -b" when the servers are started.
39 # Check /etc/pam.d/frr if you intend to use "vtysh"!
42 zebra_options=" -A 127.0.0.1 -s 90000000"
43 bgpd_options=" -A 127.0.0.1"
44 ospfd_options=" -A 127.0.0.1"
45 ospf6d_options=" -A ::1"
46 ripd_options=" -A 127.0.0.1"
47 ripngd_options=" -A ::1"
48 isisd_options=" -A 127.0.0.1"
49 pimd_options=" -A 127.0.0.1"
50 pim6d_options=" -A ::1"
51 ldpd_options=" -A 127.0.0.1"
52 nhrpd_options=" -A 127.0.0.1"
53 eigrpd_options=" -A 127.0.0.1"
54 babeld_options=" -A 127.0.0.1"
55 sharpd_options=" -A 127.0.0.1"
56 pbrd_options=" -A 127.0.0.1"
57 staticd_options="-A 127.0.0.1"
58 bfdd_options=" -A 127.0.0.1"
59 fabricd_options="-A 127.0.0.1"
60 vrrpd_options=" -A 127.0.0.1"
61 pathd_options=" -A 127.0.0.1"
64 # If you want to pass a common option to all daemons, you can use the
65 # "frr_global_options" variable.
67 #frr_global_options=""
70 # The list of daemons to watch is automatically generated by the init script.
71 # This variable can be used to pass options to watchfrr that will be passed
72 # prior to the daemon list.
74 # To make watchfrr create/join the specified netns, add the the "--netns"
75 # option here. It will only have an effect in /etc/frr/<somename>/daemons, and
76 # you need to start FRR with "/usr/lib/frr/frrinit.sh start <somename>".
81 # configuration profile
83 #frr_profile="traditional"
84 #frr_profile="datacenter"
87 # This is the maximum number of FD's that will be available. Upon startup this
88 # is read by the control files and ulimit is called. Uncomment and use a
89 # reasonable value for your setup if you are expecting a large number of peers
94 # Uncomment this option if you want to run FRR as a non-root user. Note that
95 # you should know what you are doing since most of the daemons need root
96 # to work. This could be useful if you want to run FRR in a container
100 # For any daemon, you can specify a "wrap" command to start instead of starting
101 # the daemon directly. This will simply be prepended to the daemon invocation.
102 # These variables have the form daemon_wrap, where 'daemon' is the name of the
103 # daemon (the same pattern as the daemon_options variables).
105 # Note that when daemons are started, they are told to daemonize with the `-d`
106 # option. This has several implications. For one, the init script expects that
107 # when it invokes a daemon, the invocation returns immediately. If you add a
108 # wrap command here, it must comply with this expectation and daemonize as
109 # well, or the init script will never return. Furthermore, because daemons are
110 # themselves daemonized with -d, you must ensure that your wrapper command is
111 # capable of following child processes after a fork() if you need it to do so.
113 # If your desired wrapper does not support daemonization, you can wrap it with
114 # a utility program that daemonizes programs, such as 'daemonize'. An example
115 # of this might look like:
117 # bgpd_wrap="/usr/bin/daemonize /usr/bin/mywrapper"
119 # This is particularly useful for programs which record processes but lack
120 # daemonization options, such as perf and rr.
122 # If you wish to wrap all daemons in the same way, you may set the "all_wrap"