On 15/12/2021 19:55, FreeBSD User wrote:
It is spooky, if not to say "buggy", if ZFS is capable of freezing the whole
box even if
the essential operating system stuff is isolated on a dedicated UFS filesystem.
I do not think that this is the case.
Commands that do not access anything on ZFS or
On 15/12/2021 17:55, FreeBSD User wrote:
… SSD, partioned into two halfes, one for ZIL, the other for
L2ARC. When showing "zpool status", the RAIDZ's HDDs (Hitachi/Seagate
4 TB NAS HDD) where "online", ZIL was "online" and
L2ARC device/vdev showd - nothing. …
The 'nothing' aspect reminds me of
Back when I upgraded the ThreadRipper 1950X amd64 system to (line split for
readability):
# uname -apKU
FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #25
main-n251456-22c4ab6cb015-dirty:
Tue Dec 7 19:38:53 PST 2021
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-
From: FreeBSD User wrote on
Date: Wed, 15 Dec 2021 18:55:09 +0100 :
> . . .
>
> It is spooky, if not to say "buggy", if ZFS is capable of freezing the whole
> box even if
> the essential operating system stuff is isolated on a dedicated UFS
> filesystem.
I would guess that, for ZFS being in u
On Wed, 15 Dec 2021 at 11:56, Emmanuel Vadot wrote:
>
>
> Hello, it's me again,
>
> I've posted some review some time ago but didn't follow up with some
> mail so users might see it.
> I'd like to remove publickey(5) related programs, those are the only
> DES users iirc and likely unused.
>
>
On Wed, Dec 15, 2021 at 05:52:02PM +0100, Emmanuel Vadot wrote:
E> > > I've noticed this /sbin/sconfig binary and after looking it's for
E> > > configuring Cronyx E1 PCI (PCI as in PCI, not PCIe).
E> > > The products pages ([1], [2]) seems to say that FreeBSD >=7 isn't
E> > > supported.
E> > > W
On Mon, 13 Dec 2021 09:30:50 +0200
Andriy Gapon wrote:
> On 12/12/2021 18:45, Alan Somers wrote:
> > You need to look at what's causing those errors. What kind of disks
> > are you using, with what HBA? It's not surprising that any access to
> > ZFS hangs; that's what it's designed to do when a
On Fri, 10 Dec 2021 19:41:07 +1030
Daniel O'Connor via freebsd-current wrote:
> > On 25 Nov 2021, at 18:50, FreeBSD User wrote:
> >
> > Running CURRENT (FreeBSD 14.0-CURRENT #7 main-n250911-a11983366ea7: Mon Nov
> > 22
> > 18:17:54 CET 2021 amd64) troubles me with our DNS server/service.
> > A
On Wed, Dec 15, 2021 at 9:52 AM Emmanuel Vadot
wrote:
> On Wed, 15 Dec 2021 10:42:36 -0500
> Ed Maste wrote:
>
> > On Wed, 15 Dec 2021 at 10:27, Emmanuel Vadot
> wrote:
> > >
> > >
> > > Hello all,
> > >
> > > I've noticed this /sbin/sconfig binary and after looking it's for
> > > configuring
Hello, it's me again,
I've posted some review some time ago but didn't follow up with some
mail so users might see it.
I'd like to remove publickey(5) related programs, those are the only
DES users iirc and likely unused.
https://reviews.freebsd.org/D30682
https://reviews.freebsd.org/D3068
On Wed, 15 Dec 2021 10:42:36 -0500
Ed Maste wrote:
> On Wed, 15 Dec 2021 at 10:27, Emmanuel Vadot wrote:
> >
> >
> > Hello all,
> >
> > I've noticed this /sbin/sconfig binary and after looking it's for
> > configuring Cronyx E1 PCI (PCI as in PCI, not PCIe).
> > The products pages ([1], [2])
On 2021-12-15 02:55, Piper H wrote:
But I write this program to listen on port who sends a random str to
the socket every 0.25 second. And there is no client connecting to the
port. The server just runs there without problem. :( So I am not sure
enough...
use strict;
package MyPackage;
use
On Wed, 15 Dec 2021 at 10:27, Emmanuel Vadot wrote:
>
>
> Hello all,
>
> I've noticed this /sbin/sconfig binary and after looking it's for
> configuring Cronyx E1 PCI (PCI as in PCI, not PCIe).
> The products pages ([1], [2]) seems to say that FreeBSD >=7 isn't
> supported.
> We currently only
Hello all,
I've noticed this /sbin/sconfig binary and after looking it's for
configuring Cronyx E1 PCI (PCI as in PCI, not PCIe).
The products pages ([1], [2]) seems to say that FreeBSD >=7 isn't
supported.
We currently only build the drivers for i386 (and they contain native
compiled code).
Thanks @Ronald Klop
I changed it to this and it does work:
print "$str\015\012" or return;
Regards
On Wed, Dec 15, 2021 at 7:47 PM Ronald Klop wrote:
> Hi,
>
> Your program first waits for the first client to connect. So nothing is
> written anywhere.
> You can check by running "nc -
Hi,
Your program first waits for the first client to connect. So nothing is written
anywhere.
You can check by running "nc -v localhost " in another terminal.
After the first client disconnects it keeps looping in the while and the print
will return 0 which means failure.
Something like th
But I write this program to listen on port who sends a random str to
the socket every 0.25 second. And there is no client connecting to the
port. The server just runs there without problem. :( So I am not sure
enough...
use strict;
package MyPackage;
use base qw(Net::Server);
my @fruit=qw(
Hi,
Just try it!
I think you will get an error that you are writing to a not-connected socket.
From "man 2 write":
" [EPIPE]An attempt is made to write to a socket of type SOCK_STREAM
that is not connected to a peer socket."
See also "man 2 send" and "man 2 socket" for a lot
18 matches
Mail list logo
