It’s not bad to get running, and the alerting is really flexible. You can add Nagios and syslog alerts easily too.
It’s not bad to get running, and the alerting is really flexible. You can add Nagios and syslog alerts easily too.
Using it here. Love the flexibility and features.
I’m running NUT on the host os - no container. If that’s an option for you it will probably be much more reliable.
Huh. Losing USB access?
It’s not very exciting, but: Network UPS Tools (NUT).
Keep everything in good shape in the event of a power outage.
Here’s my messy-cabled 9u rack.
It has:
Everything is set up for low energy consumption (~90w), remote admin, and recovery from power loss.
We are on Fidelity. But self-directed on all the big ones are no fee and free trades these days - Vanguard, Fidelity, Merrill and probably others. Just need to watch the fund/ETF fees to have a total cost.
That’s better for sure. Still too much for me. Our all-in investment cost is 0.05% now. That’s a lot of free compounded yield compared against guided investments which are themselves no better than the average market (on average).
That’s all fine, but just be sure you know how much you’re paying them for that service. Before we switched to self-managed a number of years ago our guys were taking 1.4% off the top of the whole account just to pick a bunch of index ETFs. Market goes up 5% and I only see 3.6% of it. Not good. Plus the ETFs they picked had higher expenses than just going with a whole market choice.
They offered to get us on a plan at 1%. Ha, no thanks.
That and the shrinking ability to grant access to device storage. If that becomes an option only on rooted phones (which seems like the directly Google is heading) it will make the audience for such an app much smaller.
Mildly what now?
No. 1970 is 0 in Unix time. The NTP RFC specifies 1900. I had to look it up!
Better to represent it as a 64-bit unsigned fixed-point number, in seconds relative to 0000 UT on 1 January 1900. It’s how he would have wanted it.
It can help to download your local map for offline use. The default basemap doesn’t have details like house numbers, but the downloaded maps should.
OsmAnd will do that. If you edit the destinations you can manually specify their order. Click sort there and choose door-to-door to get the most efficient routing.
The app takes some getting used to, but it works very well, and can act as a front-end for contributing to OpenStreetsMap.
See what’s using the space. This will list any dirs using >100MiB:
sudo du -h -d 5 -t 100M /var
I use LibreNMS, which is a fork of Observium. It is primarily SNMP polling, so if you haven’t worked with SNMP before there can be a bit of a learning curve to get it set up. Once you get the basics working it’s pretty easy to add service monitoring, syslog collection, alerting and more. And since it’s SNMP you can monitor network hardware pretty easily as well as servers.
The dashboards aren’t as beautiful as some other options but there is lot to work with.
Interesting. In NC here. Not sure if there’s a difference regionally. I was seeing that kind of RTT on ipv4, but ipv6 was slower. I’ll need to give it another try. The last time I did was at my last place where I had the BGW210. I have the BGW320 now and haven’t tried on that. Maybe that, or changes in their routing since then will make a difference.
Did I read right that it doesn’t use systemd?
If you want to keep using networkd, you might want to consider if multiple interfaces are causing the wait. NM doesn’t care, but networkd gives more granular options for dependencies. If you have wired and wireless and only one in use the systemd-networkd-wait-online.service waits for a timeout period. You can find lots of info on it related to boot delays with that service.
Try the --any switch on the systemd-networkd-wait-online.service launch configuration. This will tell the wait-online service that any single routable interface is enough, you don’t need them all.
Run:
sudo systemctl edit systemd-networkd-wait-online.service
That adds the override.conf for the service. Add these lines:
[Service] ExecStart= ExecStart=/usr/lib/systemd/systemd-networkd-wait-online --any
The other possibility is if you have virtual .netdev devices configured (VPN, bridging, etc) and some of them are not essential for the machine to be online, you can set RequiredForOnline=no on the ones that aren’t essential.