XScreenSaver must bu rerun as demon on new login in Xfce 4.14

2019-10-18 Thread Dmitry Postolov
Hi to FreeBSD Community! Sorry for my very bad English... FreeBSD-12.1-RC2-amd64. Xfce 4.14 from the "latest" pkg repository. XScreenSaver 5.43 (09-Jul-2019). XScreenSaver must bu rerun as demon on new login, because in other case it dont run as demon (in first start it was run). The hardware:

Is it necessary to bump target triple for lib32

2019-10-18 Thread Jeremy
While I was doing a buildworld for FreeBSD 12 stable (r353745) for amd64, I noticed the target triple was set at x86_64-unknown-freebsd12.0 while it was building the 32 bit libraries. I was wondering if it was necessary to bump it to 12.1 now that 12.1 is getting ready for release, or if it

XScreenSaver must bu rerun as demon on new login in Xfce 4.14

2019-10-18 Thread Dmitry Postolov
Hi to FreeBSD Community! Sorry for my very bad English... FreeBSD-12.1-RC2-amd64. Xfce 4.14 from the "latest" pkg repository. XScreenSaver 5.43 (09-Jul-2019). XScreenSaver must bu rerun as demon on new login, because in other case it dont run as demon (in first start it was run). The hardware:

Network anomalies after update from 11.2 STABLE to 12.1 STABLE

2019-10-18 Thread Paul
Our current version is: FreeBSD 11.2-STABLE #0 r340725 New version that we have problems with: FreeBSD 12.1-STABLE #5 r352893 After update to new version we have started to observe an incredible number of errors in HTTP requests in between various services in our system. This problem

FreeBSD 12.1-RC2 Now Available

2019-10-18 Thread Glen Barber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The second RC build of the 12.1-RELEASE release cycle is now available. Installation images are available for: o 12.1-RC2 amd64 GENERIC o 12.1-RC2 i386 GENERIC o 12.1-RC2 powerpc GENERIC o 12.1-RC2 powerpc64 GENERIC64 o 12.1-RC2 powerpcspe

Re: SSH error messages (bug id=234793) ) RELENG_12

2019-10-18 Thread Matt Garber
Does anyone know what the cause is of this fail message ? (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793) its triggered by a normal ssh key'd login, but sshd is running with VERBOSE logging. sshd[63290]: Failed unknown for testuser1 from

Re: SSH error messages (bug id=234793) ) RELENG_12

2019-10-18 Thread mike tancsa
On 10/18/2019 10:36 AM, Matt Garber wrote: >>> Does anyone know what the cause is of this fail message ? >>> >>> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793) >>> >>> its triggered by a normal ssh key'd login, but sshd is running with >>> VERBOSE logging. >>> >>> sshd[63290]: Failed

Re: SSH error messages (bug id=234793) ) RELENG_12

2019-10-18 Thread Matt Garber
> >> Does anyone know what the cause is of this fail message ? >> >> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793) >> >> its triggered by a normal ssh key'd login, but sshd is running with >> VERBOSE logging. >> >> sshd[63290]: Failed unknown for testuser1 from 192.168.xx.yyy

Re: SSH error messages (bug id=234793) ) RELENG_12

2019-10-18 Thread Matt Garber
> Does anyone know what the cause is of this fail message ? > > (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793) > > its triggered by a normal ssh key'd login, but sshd is running with > VERBOSE logging. > > sshd[63290]: Failed unknown for testuser1 from 192.168.xx.yyy port > 60643

SSH error messages (bug id=234793) ) RELENG_12

2019-10-18 Thread mike tancsa
Does anyone know what the cause is of this fail message ? (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793) its triggered by a normal ssh key'd login, but sshd is running with VERBOSE logging.   sshd[63290]: Failed unknown for testuser1 from 192.168.xx.yyy port 60643 ssh2 ? The user