FWIW, I’ve opened a bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229712
> Am 11.07.2018 um 23:41 schrieb Stefan Bethke :
>
> It’s been a while since I last dealt with serial devices. Apparently, when
> passing through a serial device on the host to a COM port in the VM, CTS/RTS
> are
class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gmail-MsoNoSpacing"
style="margin:0in 0in
0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Hi,
class="gmail-m_6350034823628897800gmail-m_-1605034654586745565gmail-m_-1881138833800936466gma
It appears that I just got lucky the one time. The same USB stick continues to
mount only about half the time; other USB devices also have problems. It
appears to me that the APU2 USB3 controller is not working correctly. I’ve
started a new thread over on freebsd-usb@
Stefan
> Am 09.07.2018
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Hi,
I run acme.sh with it configured to log to syslog. I use this
syslog.conf structure to log to a specific log file:
!-acme.sh
... other syslog.conf entries ...
!acme.sh
*.*/var/log/acme.log
!*
This has worked for ages, but I've just noticed it's no longer working
at all. It appear
13.07.2018 1:14, Matt Smith wrote:
> I run acme.sh with it configured to log to syslog. I use this syslog.conf
> structure to log to a specific log file:
>
> !-acme.sh
> ... other syslog.conf entries ...
> !acme.sh
> *.*/var/log/acme.log
> !*
>
> This has worked for ages, but I've just
On Jul 13 02:11, Eugene Grosbein wrote:
13.07.2018 1:14, Matt Smith wrote:
I run acme.sh with it configured to log to syslog. I use this syslog.conf
structure to log to a specific log file:
!-acme.sh
... other syslog.conf entries ...
!acme.sh
*.*/var/log/acme.log
!*
This has worked f
On a older server running FreeBSD 10.2 i have a number of jails. For
migration to FreeBSD I'm planning to shutdown the jail, move the data to
the new server and spin up the jail there. IP addresses are alse moved.
When I remove an IPv6 address with the following command 'ifconfig em0
inet6 v6addre
How did you assign the jails' IPv6 addresses in the first place? The usual
way is to assign them as /128 aliases, in which case the command to remove
them would include a "/128", not "/48". I think when you're deleting a
"/48" you're also removing some routes that the jail host is using.
-Alan
O
The routes are not affected. the strangest thing I find that the host
and jails are accessible from outside, and it can reach outside hosts
via v6, but everything that's staying on the server fails.
Alan Somers wrote:
> How did you assign the jails' IPv6 addresses in the first place? The usual
>
10 matches
Mail list logo
