I have a Void linux VM which only gets turned on once in every month. Today, when I booted up and updated the packages on this VM, I noticed that there are many old kernels installed. As a seasonal Void user, I had no clue on how to remove older kernels. Fortunately, a quick Google search pointed me to a video: VOID Linux: Removing old kernels with vkpurge. Basically, Void comes with a pre-installed utility program called vkpurge....
If you’re familiar with Kerberos, one way to check if a ticket is valid is to run klist command. ❯ klist Ticket cache: FILE:/tmp/krb5cc_1001 Default principal: username@UNIVERSITY.EDU.AU Valid starting Expires Service principal 02/07/21 11:26:50 02/07/21 21:26:50 krbtgt/UNIVERSITY.EDU.AU@UNIVERSITY.EDU.AU renew until 03/07/21 11:26:50 02/07/21 12:24:07 02/07/21 21:26:50 cifs/server1.UNIVERSITY.edu.au@UNIVERSITY.EDU.AU 02/07/21 12:24:07 02/07/21 21:26:50 cifs/server1.UNIVERSITY.edu.au@UNIVERSITY.EDU.AU ❯ date Mon 05 Jul 2021 16:01:59 AEST From the above output, the principal ticket expired since 2 Jul. So how do we find out if the Kerberos (principal) ticket expires programmatically?...
Suppose you just connect a Raspberry Pi to your home network using ethernet interface, and the Pi is not connected to a display device. How would you find an IP of that Raspberry Pi? Well, you’re right…whatever you say. There are a few ways to do this - looking at DHCP log, router log, …etc. But here is an even easier way to achieve this - using a command line tool called nmap....
I just updated my Foreman server and reboot, then this happened when I accessed the web console: Service unavailable ERF64-6496 [Foreman::MaintenanceException]: There are migrations pending in the system. This was the first time I’ve seen this message, and possibly because I haven’t done the update frequently enough. Fortunately, according to this blog post, it should be relatively easy to fix. [root@foreman ~]# sudo foreman-rake db:migrate API controllers newer than Apipie cache!...
If you use LVM frequently enough, especially when re-using existing disks, you might come a cross a problem when you’re unable to create a physical volume from that disk. For example, here is what I encountered today when I tried to create a physical volume on a device called /dev/sdb. [root@db3 ~]# pvcreate /dev/sdb Device /dev/sdb excluded by a filter. I’m sure I haven’t had any filters in /etc/lvm/lvm.conf. To fix this, I needed to wipe the signature from this device with wipefs command....