Hi. After a server restart I can't start NUT (14.0p6) Previously I had no problems and I didn't modify the server lately. Nut fails with "setuptcp: bound to localhost as 1c1c:da5:: but there seem to be further (ignored) addresses resolved for this name" Is it trying to bind to an IPV6 address?

What would be the downside of doing `sysrc fsck_y_enable="YES"`? There must be a reason this isn't enabled by default.

tuaris: fsck -y can unconditionally modify the filesystem in a way that might cause data loss

if you're confident in your backups (and/or you use journaling or softupdates) it's probably fine

A default modern install of FreeBSD should use already be using journaling, correct?

i haven't used the UFS installer for years so i don't know off hand. but the administrator may create new filesystems post-install and those may not be using journaling

fsck -y is generally considered a dangerous operation and not something that should be enabled by default

Assuming all important data is kept externally, either on NFS or ZFS, and configurations backups are done regularly, this should in theory be a better option that just letting the file system get remounted in a dirty state and not knowing about it (when there are 100's of VM's).

you could post to arch@ to suggest this be changed, if you have an argument for it

I'm not suggesting we change the default behavor

Was curious about the decision behind the current decision, but you explained it perfectly.

well, i think you make a reasonable point that with background fsck, the filesystem will be mounted anyway. i'm not really sure what the expected behaviour is here.

it used to be if fsck failed the system would drop to single user and you would run fsck -y by hand (if you wanted to)

I am worried that over time this would result in filesystem corruption and render the machine unusable in the long term

the documentation (man.freebsd.org/cgi/man.cgi?fsck) says:

Note that background fsck is limited to

checking for only the most commonly occurring file system ab-

normalities. Under certain circumstances, some errors can es-

cape background fsck. It is recommended that you perform fore-

ground fsck on your systems periodically and whenever you en-

counter file-system-related panics.

this seems like fairly undesirable behaviour to me, i have to say

hmm, yeah

i doubt anyone "perform[s] foreground fsck on [their] systems periodically"

hehe, yeah. It's always reactive. Usually when I notice anyone of my system's panicing for no reason, I do a manual fsck

It's really hard to do a periodic fsck when you have hundreds of FreeBSD systems all over the palce

Hi, trying to install a python-package (sentence-transformers) here. I create the virtual environment:

I activate the virtual environment, and I try to pip install sentence-transformes. It begans evaluating differen t releases and tries to install one but it fails. It points to dependencies on torch. I already installe py311-pytorch using pkg install, any ideas?

unixman_home: TYVM, your suggestion works :D

freebsd 14 broke after I tried setting up xfce and kde to be my chose of desktops .   I rebooted and now there was problem with zfs . I have ran the live cd on for freebsd scrubbing the zfs and yet  I still have the problem.  I can look at the files with Ubuntu and every thing seem to be there . I don't know how I might fix it.  I'm new to

freebsd so I don't know how to replace the bootloader  if that is even the problem

f451, you're welcome.

I was looking for an answer for tarel2, but that person left too soon. Oh well. :P