regis: What's wrong with it (aside from the brutally lengthy iterations?

ek, My relatively fast machine takes 20 seconds to solve some of the sites challenges. My slower older laptop takes a few MINUTES to solve the challenges. It's frustrating. The feel of things are not getting better. The feel of things is that things are getting worse.

rwp: Hrm... Seems to me those sites aren't handling their configs properly, maybe? It shouldn't take more than half a second to solve for most systems. Even slower ones. Especially if they're legit.

rwp: You're saying freshbsd.org takes minutes to solve?

Granted, they do have a very aggressive challenge. But, what about something like test.freshports.org ? Does that take the same lengthy time?

hm

is there any sort of special settings for zfs on usb drives?

like should ashift be 96 or some oddball thing?

so i labeled the zfs partitions but the labels aren't showing in /dev/gpt

is there something else i need to do to get them to pop up there?

rebooting didn't do the trick

hm

ah nm. i guess they're "there"

they just don't show

rwp: regis: if you don't complain it won't get fixed, ffs

I didn't set up Anubis for fun, I set it up because scrapers were eating about a quarter of my server in their ridiculous endless stream of expensive searches

Freaky: no worries; BTW: thanks for excellent service 1

s/1/!

mdoctl: reviews.freebsd.org/D50510

Freaky: I understand your standpoint but mine is: when I see something like this or instructions to click on hydrant pictures - I usually close the browser tab. But I'm not your usual user but a weirdo defaulting to NoScript.

ivy: What does this actually do?

ivy: As in what is MAC/do?

so the whole thing with my usb drives acting flakey was because o that default 4k setting for zroot install it seems (maybe?)

they seem to be doing a lot better now. i have a 3rd one that i might stick in the back usb port as a hot spare

just checking so with beadm when you create a be then that is where you will wind up if you hit 8 during boot and select that particular be?

so essentially a snapshot of where you are at a particular time?

Macer: Of the root dataset, yes

regis: I've turned it off for now since the bots are a bit less insane these days

Freaky: I hope that I described my weirdo approach properly, as in: not in a deamiining way.

regis: it's an understandable and justified position

regis: Freaky: those bots are leaching the bandwitdht, please keep them away from this excellent service

mzar: I'm not a bot and won't work towards proving that I'm not one.

regis: I'm the same way. NoScript always enabled. But, for sites I trust, I have no problem giving them a permanent exemption.

vkarlsen: thanks. cool.

Freaky, Everyone is already complaining!

(people are complaining, bots are a a statistic)

are nfs clients able to see dirs mounted with nullfs in a freebsd nfsv3 server ?

hernan604, Normally NFS mounts do not cross mount points on the server. I haven't tried with a nullfs mount but I think it would not since that would be a different mount point. It should be possible to export that additional mount point though and then nfs mount it too.

rwp: yea, im seeing that.. ok thanks

rwp: would be so much better to export just a root dir

NFS has always worked at the mount_point-directory level. Every mount point needs to be separately exported.

Over NFS if looking at a directory that is a mount point on the server it will just appear as an empty directory. (I actually think that the underly file system contents will be shown because that is on the mount point that was exported. Usually that's none. But if-and-only-if there is content there then on the server mounting another directory on top of it will shadow it and hide it on the server.)

It's a confusing description limited by the limitations of IRC message lines and my ability to organize the description concisely.

vkarlsen: see mac_do(4), but in short it's a way to let a user change their credentials (uid, gid, ...) without needing a setuid utility. it's somewhat like sudo or doas, but the implementation is very different

ivy: Oh, nice