Dan Langille
dvl@FreeBSD.org
I've been contributing to open source since 1998.
More on #FreshPorts vs restrictions on search, etc.
Last night, I received a CPU alert regarding the database server.
I logged in and restricted search to logged-in users.
[13:15 aws-1 dvl ~] % sudo grep 'joe' /var/log/auth.log.1
May 4 00:57:46 aws-1 sudo[37761]: dvl : TTY=pts/0 ; PWD=/usr/home/dvl ; USER=root ; COMMAND=/usr/local/bin/joe /jails/nginx01/usr/local/etc/freshports/constants.local.php
This change means anyone not logged into FreshPorts with their FreshPorts account will get a 401 for any search.
This morning, the graph for Nginx requests graph looks like this.
Search was enabled again at May 4 13:14:37
Two hosts came back with bad /etc/resolv.conf
I fixed it with 'resolvconf=NOin /etc/resolvconf.conf andmv /etc/resolvconf.conf.bak /etc/resolvconf.conf `
Search on FreshPorts is again restricted to registered users. Search traffic doubled from 40% to 77% just after 00:00 UTC on May 6.
Details here: https://gist.github.com/dlangille/f7244e592c663a16a8350816ac50a9a5
#pgbackrest is dead. What next?
https://mydbanotebook.org/posts/pgbackrest-is-dead.-now-what/