Task
To refresh Shotwell thumbnails cache.
Description
Shotwell create thumbnail for every picture it display so when you scroll through gallery it will rebuild it. Problem is when storage is slow (SMB over WiFi) it takes some time.
Idea
Force Shotwell to scroll all gallery
Solution
Find id of Shotwell window:
As you can see sometimes there are two of them (I don't know why)
Switch to that window an send Page_Down / Next key check.
Repeat many many (1000) times but give some time (22s) to refresh all visible pictures. I've prepared bash script:
After confirmation which identifier is good (2099432) you can run:
and do something more interesting than just typing Page_Down key for more than 6h.
Once, after server crash, I've noticed I've BackupPC shows no backups for some clients. Fortunately /BackupPC/pc/*/ still contains those backups.
To fix a corrupted backups file you should:
- Stop BackupPC
- Run BackupPC_fixupBackupSummary script as backuppc user
- Start BackupPC
Now I can see all backups on Host Summary page.
How to detect if there someone is home or if the house is empty.
Prerequisite
- OpenWRT router
- MQTT server
- Something to interpret and display data (Node-RED, Home Assistant, Domoticz, OpenHAB, etc.)
On your OpenWRT router:
Install mosquitto-client. If you don't use encrypted communication use -nossl version.
Download presence_sensor script:
make it executable:
Now you can check if it works. Run command:
Change 192.168.1.8 to address of your MQTT server. Turn WiFi on one of your devices (my was e6:6a:ca:c8:38:e6).
as you can see there my device "left" (del) and connect (new) to Wi-Fi.
Press Ctrl-C to stop test.
To start this every time router boots I've added this line:
to /etc/rc.local file. Of course before "exit 0".
Using data
You can subscribe to "owrtwifi/status/#" topics to receive messages in topic like this:
and payload del or new.
They are also messages in topic
and name of your device in payload.
I'm using Node-RED and check every device like this:
Maybe it's not the best way, but it works for me.
The most important value is devicescount - the house is empty if equal to zero.
Of course this method cannot distinguish if you are in home or you just forgot your phone. It's obvious, but I want to be sure you know this too ;-)
When you will try to use VirtualBox on Windows 11 you can notice that VM performance is very low.
One of the reason can be Windows Hypervisor-enforced Code Integrity (HVCI).
The easiest way to check if it active is via Settings > Update & Security > Windows Security > Device security > Core isolation details > Memory integrity.
To turn it off run cmd as privileged user:
and restart the system.
Be aware, that HVCI is turned on to improve system security - so turn if off only when you really need it.
Download current binary from site memtest.org. Now current version is 5.31b.
Extract file (in my case memtest86+-5.31b.bin).
Rename it and place somewhere in TFTP server:
as in previous posts my TFTP root is /data/tftpboot and I place all files in networkboot directory.
Add menu entry in pxelinux.cfg/default or as in my examples in pxelinux.cfg/4c4c4544-0042-4410-8053-b2c04f43334a (these magic numbers are my test PC UUID):
On fresh install ESXi 7.0 U2 you just need two commands:
First line configures address of remote syslog server - of course you have to change 192.168.1.28 to yours server IP.
Second one opens required ports on firewall.
My router configuration was:
I would like to change WPAD address (option 252) to wpad.lan so I've to remove (del_list) old entry and add (add_list) new one:
check, if everything is correct:
now, You can commit changes (write to /etc/config/dhcp file) and restart dnsmasq daemon:
On client you can check again using nmap command:
My last resolution about power button works only when monitor is connected.
If you have headless server you can use systemd-logind service. By default (in CentOS 8) it do nothing. I've only found:
in /var/log/messages.
To change this behaviour you can modify
I've uncommented line
After thins restart service:
Now power key works on headless Linux server.
Booting to PXE (or iPXE) using dnsmasq is rather well documented also by Me ;-).
If You would like to use MikroTik it's not so easy (at least v6.43.2). I couldn't manage to boot iPXE using chainloading because of the infinite loop with the DHCP server.
Booting from PXE is also not so obvious. You cannot set option 66 (next-server/Server-Name) nor 67 (boot-file/Bootfile-Name) in "ip dhcp-server option". Instead set "Next Server" and "Boot File Name" in "ip dhcp-server network", so it should look like this:
Add comment