I fixed the problem and given the impending builds merged it
immediately. Can be seen here:
https://cgit.freebsd.org/src/commit/?id=4e29933d0936fd053f7591ee118dc1fc42617514
Should you run into any other problems, they can be temporarily worked
around with:
sysctl vfs.cache_fast_lookup=0
For probl
On 02/02/2021 19:20, Mateusz Guzik wrote:
I fixed the problem and given the impending builds merged it
immediately. Can be seen here:
https://cgit.freebsd.org/src/commit/?id=4e29933d0936fd053f7591ee118dc1fc42617514
Should you run into any other problems, they can be temporarily worked
around wi
On Tue, Feb 2, 2021 at 10:42 AM Kristof Provost wrote:
>
> On 2 Feb 2021, at 14:05, Johan Hendriks wrote:
> > On 01/02/2021 22:48, Johan Hendriks wrote:
> >> I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now
> >> i can not start varnish anymore.
> >> This is on two machines.
>
On 2 Feb 2021, at 14:05, Johan Hendriks wrote:
On 01/02/2021 22:48, Johan Hendriks wrote:
I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now
i can not start varnish anymore.
This is on two machines.
if i start varnish it errors out as the startup script does a config
file c
On 01/02/2021 22:48, Johan Hendriks wrote:
I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now
i can not start varnish anymore.
This is on two machines.
if i start varnish it errors out as the startup script does a config
file check.
If i try to do a test of the config file
On 01/02/2021 22:48, Johan Hendriks wrote:
I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now
i can not start varnish anymore.
This is on two machines.
if i start varnish it errors out as the startup script does a config
file check.
If i try to do a test of the config file
I just updated my FreeBSD 13.0-APLPHA3 to the latest revision and now i
can not start varnish anymore.
This is on two machines.
if i start varnish it errors out as the startup script does a config
file check.
If i try to do a test of the config file i get the following error.
root@jhost002:~
