Search results

Our situation is odd. We found the problem on one host which was upgraded from 13.1-RELEASE-p2 to 13.3-RELEASE today. With perl v5.36.3 # perl -e 'use POSIX; use IO::Pty; new IO::Pty && print "OK\n";' Cannot open a pty at -e line 1. We cannot test with perl 5.38 yet on that host. But on...

Alter this line, append jail: [11:37 zuul dan ~] % grep REQUIRE /usr/local/etc/rc.d/fail2ban # REQUIRE: DAEMON Confirm the order via: rcorder /etc/rc.d/* /usr/local/etc/rc.d/* Ensure jail appears before fail2ban - the amendment will require repeating after each reinstall of fail2ban.

I feel that such advice should always include background / elaboration / reasons so that other understand without blindly following....

FWIW, at home, I once followed -STABLE. However, once freebsd-update became a thing, I've followed -RELEASE.

Historically, I do not know. We're run -RELEASE for more than 10 years. We patch via freebsd-update fetch install. If I had to guess, it'd be because patching the OS is rather straight forward. We have about 650 servers and they are all different. There might be a cluster where they all do...

I tried building with the indicated options. [dvl@ava-pkg-02prd:~] $ pkg info msktutil | grep GSS GSSAPI_BASE : off GSSAPI_HEIMDAL : off GSSAPI_MIT : on FWIW, msktutil dies sooner (right after SASL/GSS-SPNEGO authentication started) as opposed to much later...

The author of that issue is a clever chap. I'm trying that now. Thanks.

-STABLE is not an option for us. We use -RELEASE.

For now, we're going back to FreeBSD 13.3 (due to be released soon) and abandoning 14.0 for use with Active Directory for now. It seems like some utilities need to be patched up to work with the newer OpenSSL.

Use pkg-static to bootstrap your host with a new pkg, or at least: sudo pkg-static install -f pkg

Does pkg-static help

Above, we thought kstart was broken. It goes deeper I think. Here, msktutil also dump: This is on another host: bsdpackage01p# lldb --core msktutil.core /usr/local/sbin/msktutil (lldb) target create "/usr/local/sbin/msktutil" --core "msktutil.core" Core file '/tmp/msktutil.core' (x86_64) was...

Backups seem fine. All running as expected.

I'll try that zpool configuration change: [15:36 r730-03 dvl ~] % zfs get -r aclinherit data01/timemachine NAME PROPERTY VALUE SOURCE data01/timemachine aclinherit restricted default data01/timemachine/dvl-air01 aclinherit restricted...

We match on that list night, apart from ordering: vfs objects = acl_xattr catia fruit streams_xattr

Not necessarily, but I understand.

I'm sure that's the ZFS_FILESYSTEM` not ZPOOL

Is this what you mean? [20:44 tm dvl /usr/local/timemachine] % ls -l total 74 drwxr-xr-x 3 dvl-air01 dvl-air01 4 2024.01.14 18:08 dvl-air01/ drwxr-xr-x 3 dvl-pro02 dvl-pro02 4 2024.01.14 18:19 dvl-pro02/ drwxr-xr-x 3 dvl-pro03 dvl-pro03 4 2024.01.14 18:56 dvl-pro03/ [20:44 tm dvl...

Here's my most recent blog post for Time Machine: https://dan.langille.org/2024/01/06/creating-a-time-capsule-instance-using-samba-freebsd-and-zfs-2/

My instances started not working some time ago (40+days) and I don't know why. I kept encountering "The backup image could not be created". This configuration let me get past that error and get this created: [16:32 tm dvl /usr/local/timemachine] % du -ch dvl-air01 3.0K...