On 2009-11-30, ~Lst <slack...@gmail.com> wrote: > On Tue, Dec 1, 2009 at 12:10 AM, Alexander Hall <alexan...@beard.se> wrote: >> ~Lst wrote: >> >>> Well gentlemen... >>> Right now, it looks like my bgplg has been running well, because of my >>> mistake that is the running of bgpd_flags in two places. >>> >>> 1. The bgpd_flags that is running via /etc/rc.conf.local >>> (bgpd_flags="-r /var/www/logs/bgpd.rsock" -> exactly like described in >>> the man pages). >>> 2. Had been running too in /etc/rc.conf (bgpd_flags=""). >> >> None of the above starts the daemon per se. They only tell the rc >> scripts that you want to run the daemon, and how. The entry in >> rc.conf.local overrides the one in rc.conf. >> >> If your problem is solved, fine. I just do not think that what you >> describe above would cause any problems, unless what you wanted was the >> setting in rc.conf. >> > > Yup, you're right. I just don't realized that I'd been already started > the socket through the rc.conf. > It might be a `mistake' for a newbie like me, if you want to running > one thing in rc.conf.local it overrides the one in rc.conf.
treat rc.conf as a part of the OS, not a user config file - you should leave it alone (except to upgrade it with the rest of the OS). if you want to make any changes, copy the relevant lines to rc.conf.local and edit as required.
