Hello Koichiro,
Is there any update to this? I've since upgraded both systems to
FBSD 12.0-RELEASE-p3 and there have also been (I think) two (2) xrdp
port/pkg updates as well but the problem still remains the same.
Connections to chansrv work 100% of the time on one system and 0% of the
time
On 5/8/19 2:46 PM, Hans Petter Selasky wrote:
On 2019-05-08 13:44, Jan Beich wrote:
Andrea Venturoli writes:
Try to install GDB from ports and use that. It often helps.
Right!!! Thanks!!!
I always install installing it when I develop, but forgot to think about
it in this sysadmin-side
On 2019-05-08 13:44, Jan Beich wrote:
Andrea Venturoli writes:
Try to install GDB from ports and use that. It often helps.
--HPS
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe,
Andrea Venturoli writes:
> While this sheds some light (seems the whole thing has to do with
> trust password change), it shows a stack overflow, not an assert.
"stack overflow detected" messages are part of -fstack-protector*.
Recently, ports/ default changed to -strong in order to follow
On 5/8/19 12:25 PM, Konstantin Belousov wrote:
Signal 6 is SIGABRT, which means most likely that some assert was triggered.
You should look into your logs.
samba.log shows nothing at level 1 (default); at level 3 gives gobs of
information and I don't look what to look for.
In all.log,
On Wed, May 08, 2019 at 12:03:34PM +0200, Andrea Venturoli wrote:
> Hello.
>
> I've got a few servers where I run Samba 4.8 in a jail as an AD DC.
>
> Lately, on a couple of them, it started dumping core: on one server,
> apparently everything works fine after that; on another one I have
>
Hello.
I've got a few servers where I run Samba 4.8 in a jail as an AD DC.
Lately, on a couple of them, it started dumping core: on one server,
apparently everything works fine after that; on another one I have
intermittent DNS issues, but I'm not sure they are related to this core.
I tried
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,
