[Bug 261094] net/babeld
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261094] net/babeld"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261094] net/babeld"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261094] net/babeld"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 261094] net/babeld"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 10 Jan 2022 21:07:58 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261094 Bug ID: 261094 Summary: net/babeld Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: dennis.noordsij@alumni.helsinki.fi CC: gaod@hychen.org CC: gaod@hychen.org Flags: maintainer-feedback?(gaod@hychen.org) Having just installed babeld, I wondered why it was not picking up my configuration file (for which it installs a sample) at /usr/local/etc/babeld.conf Changing the initd script to read: command_args="-D -I /var/run/${name}.pid -c $babeld_config" instead of command_args="-D -I /var/run/${name}.pid $babeld_config" fixes this and causes my config file to be read. man babeld: -c filename Specify the name of the configuration file. This flag can be repeated multiple times. The default is /etc/babeld.conf. (I don't know if this is on purpose as I'm not otherwise familiar with using babeld) -- You are receiving this mail because: You are the assignee for the bug.