Mute Screamer uses PHPIDS to detect attacks on your WordPress site and react in a way that you choose.
If you have too many intrusions in you Mute Screamer log (v 1.0.7 at time of writing) removing them via Admin (web) interface could be time consuming.
Faster is to do that directly on the database.
Just execute this SQL command (MySQL in this example) on your WorPress database:
TRUNCATE TABLE 'PREFIX_mscr_intrusions'
NOTE: “mscr_intrusions” is default table name and PREFIX is your WordPress prefix you set on installation, please replace with correct value. if you do not have that table you can look for the name at line 53 in mute-screamer.php.
I will be glad to see clean all button in one of next versions.
Since version 2.0 of VLC a lot of changes were made in the code of this popular media player.
Something annoying was the increase of CPU usage when playing audio files. From almost 0% to 10-20%.
On powerful system this increase is almost unnoticeable, but on Intel Atom or AMD C60 you can notice the difference.
The fix is really easy.
Shutdown VLC and just erase/rename following 2 files from VLC folder (in my case C:\Program Files (x86)\VideoLAN\VLC\plugins\codec):
And this is all. CPU usage is back to normal.
I did not notice any problems for now.
Finally I can use again VLC on all my systems.
Recently I got Error ID: 30702 on my Blackberry.
Initially I suspected problem on BB side, but after researching on the web it is common problem.
Following instructions on this post I’ve tried to login to payment options, but I’ve received same error Error ID: 30702.
Following further posts I logged in in blackberry app world.
Unlike other reports my login was successful.
Then something else was wrong.
Looking at my account I’ve noticed that my e-mail address was unconfirmed. I followed instructions and confirmed my E-mail.
This allowed me to login to my app world gain.
So solution to Error ID: 30702 for me was to confirm my e-mail address.
Lesson learned 😉
To upgrade you Debian installation usually you use:
This should upgrade all installed packages. But sometimes there is a message that some packages are kept back. This means that dependencies have changed on one of the packages you have installed so that a newer package must be installed to upgrade.
To fix this you must execute:
This will do the trick.
If you just got your new CentOS server.
After a while you notice that timestamps in your logfiles are shifted with few hours. So what could be wrong?
Actually is really simple – most probably your timezone is not correct. To check run “date” from command line, this will show what is the time for your server.
Then you find that the timezone is not correct?!
How do you set the correct one?
Unfortunately, this is not an easy thing to figure out. Official documentation states that you can use system-config-date, but it has a bunch of dependencies (when I ran yum install system-config-date on one of my servers it asked to install 84 packages).
So is there an alternative way to do it?
All timezone files are located in /usr/share/zoneinfo. To select the appropriate named timezone for your location. For my location, Montreal, Canada, I actually have to select: America/Montreal. For you it could be different so make note of the appropriate folder and file for your timezone.
The active timezone used on your system is in the /etc/localtime file.
The default will vary depending on your server host and it depends on the value that was provided during installation.
We simply need to replace this file with the file we selected in the previous step.
Even I say replace, actually is recommended to create a link to the pertinent file rather than actually replacing the file.
Here are the steps to follow:
First, backup the existing localtime file (it is always good practice to make backups of original config files).
mv /etc/localtime /etc/localtime.bak
Next, create the link:
ln -s /usr/share/zoneinfo/ /etc/localtime
Test your change.
Run “date” from the command line, and ensure that the appropriate time, date, and timezone are reported.
It happens that sometimes when connecting to misconfigured Windows Terminal server (TS) client receives following error message:
“Your temporary license about to expire in… days”
This is usually dye to misconfiguration on the server side, but here is the trick to get additional 90 days temporary license:
WARNING: This requires editing of Windows registry. Use it on your own risk.
- Launch regedit – Start -> Run… -> regedit
- Go to HKLM\Software\Microsoft\MSLicensing\
- Delete hardwareID entry.
- Enjoy another 90 days, but not forget to plan for fixing the issue 🙄
Recently I had to check DNS records on specific server from Debian.
Excellent tool for this job is dig – it allows you to see all DNS records like: A, MX, TXT…
Unfortunately the tool was not installed.
The proper way of installing it is:
apt-get update && apt-get install dnsutils
In case you did update recently you can skip the first command.
I love screen – it allows you to detach you console and still have the program running.
For more info:
Recently I experienced following error:
$ screen -r
Cannot open your terminal '/dev/pts/0' - please check.
After searching for solution I found several instructing to change permissions etc.
But different solution, almost “hack” is the one I like.
Before starting screen type:
And after that you can type:
Only drawback is that you need to type one additional exit for script to terminate.
Credits for this to Harry Jackson. Unfortunately the resource was not available so i did to put a link to the site.
As addition to Fix Hibernate in Windows XP here is additional shortcut I discovered.
To activate hibernate option I had to press <shift> every time I go to shutdown menu, but once I did not and it worked…
So here is the full shortcut:
<WinKey> -> <U> -> <H>
What that means?
– Start menu
Usually in Windows XP when you click Start -> Turn off Computer you have following options:
- Stand by
- Turn off
But there is another option called Hibernate. As name suggests when you choose that option your computer goes in deep sleep. This is different from Stand by mode and Shutdown and actually is in between.
In that mode Windows XP does the same as Stand by, but in addition writes memory dump on the hard drive and turns off the PC.
After you power up the PC the memory dump is loaded in the memory and computer resumes operation as after stand by.
It takes a bit more time for that operation, but is much less hat initial power up.
How to enable Hibernate?
- Make sure that you are logged in with administrator account. You can do that by going in Start -> Control Panel -> User account
- Go to Power Options and choose Hibernate tab
- Check Enable hibernation
- Now you are able to hibernate your computer
- I do not have hibernate icon
If on turn off menu you do not have hibernate icon it means that you have newer computer BIOS that supports Stand by by lower power option.
If you want to hibernate you need to press Shift button until hibernate icon appears.