Jakob Bohm

Using 0.14.2 installed from ZIP file over the version from Debian Bookworm, and having configured TEXT MODE in refind.conf, the optional delay for detecting additional removable drivers is displayed in the BIOS-es graphic mode instead of the configured text mode, looks like rEFInd forgets to load the text mode from the config file before executing the startup delay from the same config file. This was observed on Dell hardware with the AMI UEFI skin (Aptio) from 2013 .

Steps done: * * 1. System is UEFI x86_64, Veracrypt is 1.24 update 2 2. Create and test a working VeraCrypt rescue disk 3. Continue using the system 4. Use a Linux dd disk imaging tool to copy the encrypted partition to an identical partition on a new disk Also copy all supporting partitions (such as EFI, Windows recovery and Microsoft reserved). 5. Try booting from new disk, password consistently reject during preboot. 6. Use Veracrypt rescue disk to boot from rescue boot loader, password is seemingly...

Steps done: * * 1. System is UEFI x86_64, Veracrypt is 1.24 update 2 2. Create an test a working VeraCrypt rescue disk 3. Continue using the system 4. Use a Linux dd disk imaging tool to copy the encrypted partition to an identical partition on a new disk Also copy all supporting partitions (such as EFI, Windows recovery and Microsof reserved). 5. Try booting from new disk, password consistently reject during preboot. 6. Use Veracrypt rescue disk to boot from rescue boot loader, password is seemingly...

Stepps done: * * 1. System is UEFI x86_64, Veracrypt is 1.24 update 2 2. Create an test a working VeraCrypt rescue disk 3. Continue using the system 4. Use a Linux dd disk imaging tool to copy the encrypted partition to an identical partition on a new disk Also copy all supporting partitions (such as EFI, Windows recovery and Microsof reserved). 5. Try booting from new disk, password consistently reject during preboot. 6. Use Veracrypt rescue disk to boot from rescue boot loader, password is seemingly...

On the errors404 AwStats output subpage, the "source" of 404 errors should be in the "Referrers" column unless blocked by the affected user's browser privacy settings.

I am not sure where those 72 hours come from, except that if someone does breach the server storing your logs or awstats data, you need to report it as a breach withing 72 hours of the time when you did or should know you had been breached (even if the data was only kept for 1 second or less before being stolen). But if you want to keep the data encrypted, I would suggest to use full disk encryption on the server storing this data and restrict access to viewing the output. Also, use encrypted methods...

If you upgraded awstats itself in the process, it may have discarded a different fraction of traffic as "search engine bots, worms etc.". Look at the "not viewed traffic" at the top of the statistics pages. If it increased by the same amount the regular traffic decreased that's the issue, otherwise I don't know either.

While our systems are not yet that busy, we do approach it. I have found that the following techniques keep the speed bearable, though still somewhat slow: Process the logfiles in chunks that are less than half of free memory, such as hourly or daily. For example an idle 4GB VM should be able to process 1.5GB of logs at a time. Keep the merged log and its intermediary forms (such as temporary MySQL database in your case) on a tmpfs ramdisk (/tmp is such on most servers). This was found to give a...