What if you set LOGFILE to something like /tmp/proc_stat.txt? What's /mnt/WORK anyway? It's some filesystem, but what? Maybe the postfixed dots are something that got added at the filesystem layer, the script certainly doesn't create any.
dice@chibacity:/tmp/forum_test % cat date.sh
#!/bin/sh...
Look at the raw value. Besides that, 10 is the threshold, the value is 99. That's almost an order of magnitude over the warning threshold. You've had a total of 2512 remapped sectors. And because pending and offline uncorrectable are both >0 it means your spare bit of space is full.
geli will...
I doubt they're being blocked because they came from someuser@somedomain.tld. That would block 99.9% of all valid email. Is there anything being returned? A reason? Or do they just disappear? They could be blocking based on somedomain.tld not having an MX record and they might consider that not...
Offline uncorrectable means your spare bit of space is already filled up.
That's the number of bad sectors it successfully remapped, not the amount you have left.
https://en.wikipedia.org/wiki/Self-Monitoring,_Analysis_and_Reporting_Technology
If they are pending then they failed to write to disk.
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 192
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 192
It simply means the disk ran out of spare space to map...
Updating the bootcode is pretty much mandatory if you upgrade the pool you are booting from. The system would fail to boot if the boot code doesn't understand the newer ZFS versions. But you're not booting from ZFS so this isn't an issue. Still a good idea to update the bootcode every once in a...
This sends a syslog message over the network.
syslogd never received it, so it will not send it either. The default syslogd_flags is -s which means it does NOT listen to network messages.
-ss turns off all network sockets.
-s Operate in secure mode. Do not log messages from remote
machines. If specified twice, no network socket will be opened
at all, which also disables logging to remote machines.
syslogd
Use freebsd-version instead, look at freebsd-version -urk for example. If I recall correctly p15 was a userland patch only, so the kernel wasn't updated, hence it still shows p14.
If you create a custom kernel configuration you should take T-Aoki 's advice. Simply include GENERIC (or MINIMAL) and work from there.
https://docs.freebsd.org/en/books/handbook/kernelconfig/#kernelconfig-config
If you don't know it's vt. It's been the default for a number of years and you have explicitly change it (thus you would know).
But you can also see it in your console output:
Configuring vt: keymap keyrate keybell2711;25B blanktime font8x160H7I7F0Gvidcontrol: iso2-8x16: can't load font file...
And to reiterate as I believe there's some confusion about it, your console settings (vt) have nothing to do with the terminal settings on your Bitvise ssh client.
Not on vt, older versions of FreeBSD used sc though, vt has been the standard console driver since 9.3. The old sc is still available. But if you use X on that system I don't recommend switching, one of the reasons sc was replaced was because it didn't support KMS.
One other change that may...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.