Why are there suddenly ad’s on this site?
So, recently I enrolled this site into Google’s AdSense network. It’s something that I really didn’t want to do, and am still a little torn about it.
I don’t like ad’s on web pages for a number of reasons:
- I think pages with ad’s feel less credible. So I’m going to try to limit the number of ad’s on each page to one or two. ( I know there are some with more than that right now… I’m still experimenting with how it works.)
- They can be annoying.
- The advertisement revenue model rewards click bait that generally has crap content.
So why did put ad’s on my pages? I have a few reasons for doing so that I hope the two or three people who read my blog regularly this can empathize with.
- The cost of keeping this site up and running is not insignificant. Hosting charges add up and I’m hoping to generate enough revenue to break even.
- It’s the easiest way to fund this account at the moment. I’ve kicked around the idea of using Patreon and I still might, but for now I’m going to stick with the advertising and see how it goes.
If you notice an ad that is offensive or if you find them too distracting let me know in the comments and I’ll try to either refine the placement of the ad’s or in the case that something is offensive I will do my best to remove it.
In this post I want to cover one of the most commonly used features of lvm, extending a logical volume. If you were following along with the last post, “Working with logical volumes part 1”, then you should already have a volume group with a couple of live volumes attached.
With lvm you can quickly and easily extend a Linux file system on the fly without interrupting any services.
Not too long ago I ran into a problem where a server with systemd would not shutdown or reboot through normal means.
sudo shutdown -r now I would get a weird message back as output:
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.
I’m still not entirely certain what caused the problem and the suggestion of running
systemctl status reboot.target to troubleshoot simply resulted in the same message being displayed.
However, if you run into this problem and you just need to get your services back up and running you can force a reboot like this:
Try this first:
systemctl --force reboot
If that doesn’t work, which it didn’t for me, add another –force but know that this will unceremoniously kill all running process.
systemctl --force --force reboot
This of course assumes that you can still gain access to the terminal via ssh. This operation is essentially the same as holding down the power button on a physical machine or hitting the reset button on a VM.
According to the man page this can dangerous if you have a process running that is trying to save data so be certain that you want to forcibly kill off every process on your server before running this command. Try it with only a single –force first.