When updating to FreeBSD 13.1, I started getting these messages from sysutils/logcheck: egrep: trailing backslash (\) This post will document how I tracked down the problem. It is occurring on several hosts. In this post: FreeBSD 13.1 logcheck-1.3.24 Other similar issues I suspect the issue arises because of the change from egrep 2.5.1 under FreeBSD […]
logcheck – egrep: trailing backslash (\) Read More »
In this post, I will talk about how I modified my pkg configuration so I don’t have to modify it after upgrading a host/jail from one version of FreeBSD to another. You might say that you don’t have to do that. Perhaps you have a different configuration and aren’t doing what I’m doing. HEADS UP:
Making my pkg.conf configuration version independent Read More »
Today I encountered this. [r720-01 dan ~] % sudo freebsd-update fetch install 14:39:01 Looking up update.FreeBSD.org mirrors… 2 mirrors found. Fetching metadata signature for 13.0-RELEASE from update1.freebsd.org… done. Fetching metadata index… done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. I confirmed it was just the
freebsd-update fetch install -> Cowardly refusing to proceed any further. Read More »
It was May 2021 when I tweeted about monitoring FreeBSD jails which had jail IP addresses only in the 127.0.0.0/8 range. Yesterday, nearly 6 months later, I did the first test of this. This came up because I’m getting a new FreshPorts node ready. I’ve created a file in the jail to be run from
Monitoring FreeBSD jails from the host Read More »
This started off as a Twitter thread earlier this morning. databases/mysql57-client has an optional dependency on security/cyrus-sasl2 which defaults to on. Let’s try turning that off and see if it also removes openldap-client from the dependency list. Why? I install net-mgmt/nagios-plugins in just above every jail and host. Even hosts which don’t use MySQL. I
Turning off SASLCLIENT for databases/mysql57-client Read More »
Last last night, after renaming some buildlists, which were actually setnames, for poudriere, I realized that files in /usr/local/etc/poudriere.d also needed to be renamed. In this post: poudriere 3.3.7 nginx 1.20.1_2,2 Both running on FreeBSD 13.0-RELEASE-p4 These are my renamed files: [dan@pkg01:/usr/local/etc/poudriere.d]: $ ls *primary* primary-make.conf primary-poudriere.conf primaryi386-make.conf primaryi386-poudriere.conf The output of svn status illustrates
poudriere: when renaming sets, also rename *-make.conf files etc Read More »
I like readability. I like it in variable names. I prefer something descriptive and easy to ready. In in this post: FreeBSD 13.0-RELEASE-p4 poudriere 3.3.7 I recently started getting messages like this from my daily poudiere build: I could just rename the sets, everything would be rebuilt, but then clients would be stuck pointing at
On one recent FreeBSD 13 host, I noticed a lack of motd. The MOTD (Message Of The Day) appears when you login. Typically, it looks like this: [dan@rose:~] $ r720 Last login: Mon Aug 2 00:30:13 2021 from air01.startpoint.vpn.unixathome.org FreeBSD 13.0-RELEASE-p3 (GENERIC) #0: Tue Jun 29 19:46:20 UTC 2021 Welcome to FreeBSD! Release Notes, Errata:
suppressing motd on FreeBSD 13.0+ Read More »
This post was originally a few tweets. It’s not really about upgrading vulnerabilities in poudriere jails either. Read this as if each paragraph was a tweet. When a FreeBSD security alert comes out, or a package is marked as vulnerable, I try to get that fixed as soon as I can. Even if not using
Fixing vulns in poudriere jails Read More »
When you install a package, you want to know it’s still around to reinstall. You’ve probably never given this much thought. Neither had I, until I read this post on Reddit. In my case, I run my own poudriere server which allows me to run my own package server. Why run your own package server?
Are all installed packages available for reinstall? Read More »