To: "https://lists.freebsd.org/mailman/listinfo/freebsd-ports;
+ BCC Bernhard & Astrid
Jitsi Meet & Server now in FreeBSD ports/ www/jitsi-meet
net-im/jitsi-videobridge (Bernhard, might make NetBSD easier too ?)
https://svnweb.freebsd.org/ports/head/www/jitsi-meet/pkg-descr?view=markup
03.05.2020 0:29, The Doctor via freebsd-ports wrote:
> Then let's look at the file:
[skip]
Quickest way to unbreak your server: take default named.conf from the
installation of version 9.16
and add your changes to it manually but keep default paths within lines
"pid-file" and alike.
That is,
03.05.2020 1:13, Per olof Ljungmark wrote:
> On 2020-05-02 19:29, The Doctor via freebsd-ports wrote:
>> On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote:
>>> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
> [snip]
>
>> //Use with the following in
On 2020-05-02 19:29, The Doctor via freebsd-ports wrote:
On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote:
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
[snip]
//Use with the following in named.conf, adjusting the allow list as needed:
key "rndc-key"
On Sat, May 02, 2020 at 06:53:18PM +0200, Christoph Moench-Tegeder wrote:
> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
>
> > > > Subject: Bind 9.16 port error still lingers
> > >
> > > "Still"?
>
> You seemed to imply that there was a known problem in our bind port.
> While I
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
> > > Subject: Bind 9.16 port error still lingers
> >
> > "Still"?
You seemed to imply that there was a known problem in our bind port.
While I doubt the existence of a problem with this severity (at least
my and other people's bind
On 5/2/20 11:16 AM, The Doctor via freebsd-ports wrote:
> On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote:
>> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
>>
>>> Subject: Bind 9.16 port error still lingers
>>
>> "Still"?
>>
>>> May 1 21:29:02 gallifrey
On Sat, May 02, 2020 at 05:20:27PM +0200, Per olof Ljungmark wrote:
> On 2020-05-02 17:16, The Doctor via freebsd-ports wrote:
> > On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote:
> >> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
> >>
> >>> Subject: Bind
On 2020-05-02 17:16, The Doctor via freebsd-ports wrote:
On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote:
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
Subject: Bind 9.16 port error still lingers
"Still"?
May 1 21:29:02 gallifrey named[90441]:
On Sat, May 02, 2020 at 04:32:10PM +0200, Christoph Moench-Tegeder wrote:
> ## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
>
> > Subject: Bind 9.16 port error still lingers
>
> "Still"?
>
> > May 1 21:29:02 gallifrey named[90441]: Required root permissions to open
> >
## The Doctor via freebsd-ports (freebsd-ports@freebsd.org):
> Subject: Bind 9.16 port error still lingers
"Still"?
> May 1 21:29:02 gallifrey named[90441]: Required root permissions to open
> '/var/run/named.pid'.
> May 1 21:29:02 gallifrey named[90441]: Please check file and directory
>
May 1 21:29:00 gallifrey named[3026]: invalid command from 127.0.0.1#16349:
bad auth
May 1 21:29:00 gallifrey named[3026]: stopping command channel on 127.0.0.1#953
May 1 21:29:02 gallifrey named[3026]: exiting
May 1 21:29:02 gallifrey named[90441]: starting BIND 9.16.2 (Stable Release)
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
13 matches
Mail list logo
