On 2014/06/01 01:02, Martin, Matthew wrote:
> > On 2014/05/31 19:50, Martin, Matthew wrote:
> > > > > I've not had any problems with this when I was using unbound from
> > > > > ports;
> > > > > I believe this is using the default path from login.conf... does your
> > > > > copy
> > > > > include /usr/local/sbin ?
> > > >
> > > > My login.conf does have have /usr/local/sbin; however, the effective
> > > > PATH seems to be the one set near line 220 in /etc/rc which does not
> > > > include /usr/local/{s,}bin. If I do a clean install of 5.5-release and
> > > > then pkg_add unbound, /usr/local/sbin/unbound-anchor, and add
> > > > pkg_scripts="unbound" to rc.conf.local I can reproduce the issue.
> > >
> > > Any updates on this patch?
> >
> > I'm not sure what to do with the patch really, it doesn't affect -current,
> > and I don't think that commiting it to -stable is going to help much, it's
> > probably easier to run unbound-control-setup manually the one time than
> > update to a port from -stable..
>
> The problem is that running unbound-control-setup once isn't enough.
Why not? It creates the files that the rc script checks for..
> Since unbound-control-setup isn't in PATH, unbound fails to start on
> boot if the rc script isn't edited. This means that I have to stick an
> ed kludge into my install.site just to make pkg_scripts="unbound" work.
>
> In my opinion the right thing to do would be patch the -stable port and
> then repackage for 5.5.
We would have needed to know about this in February to have been able
to fix the 5.5 packages.
