I’ve recently upgraded my Windows 7 installation to Windows 8. Unfortunately Tweetdeck wouldn’t connect to my account anymore and showed the not so useful error “Unable to connect”.
After a lot of searching I’ve found a simple and unlogical solution:
- Start Internet Explorer
- Navigate to https://api.tweetdeck.com
- Navigate to https://twitter.com
- Close Internet Explorer
- Start Tweetdeck
- Log in to your account
Now Tweetdeck works like it should, and profile images should appear again.
When installing a package via Yum, the process stalled at “Running Transaction Test”.
After a lot of digging, I found that the problem was a stale NFS mount.
After unmounting this mount with the command below, Yum worked flawlessly again.
umount -l /mnt/sharename
For Moodle development I occasionally clone a production environment to a temporary test location. This way I know for certain that my custom code works in the environment it should work in.
The downside of this approach is that notifications are still mailed to users. So after a bit of searching in the Moodle docs I have found no solution. So I went digging in the code, and found a configuration option that prevents the Moodle installation to send emails completely. All you have to do is put the following setting in your config.php.
$CFG->noemailever = true;
Tip: A lot of settings are also described in the config-dist.php file in the root folder of your Moodle installation.
If you own a shared hosting server, you probably want to keep the /var/log/messages file as clean as possible, to make searching for errors as easy as possible.
One of our web servers had a messages file filled with Drupal errors and warnings. It al seemed to come from one site.
After a bit of searching, it seemed the syslog module in Drupal was enabled. There are two solutions to this annoyance. You can disable the syslog module in the database used by this site, or make syslog log all Drupal errors to a separate file.
The most easy method to check and disable the syslog module is disabling this module in the database as follows:
Checking if the module is enabled:
SELECT * FROM system WHERE name='syslog';
If the status column is 0, the module is disabled, in case of a 1 the module is enabled.
To disable the module:
UPDATE system SET status='0' WHERE name='syslog';
And to check if the module is really disabled:
SELECT * FROM system WHERE name='syslog';
The status column should now say 0.
Separate log solution
Create the file /etc/rsyslog.d/90-drupal.conf with the following content:
# drupal logging
if $programname == 'drupal' and $syslogseverity <= '6' then /var/log/drupal.log
if $programname == 'drupal' and $syslogseverity <= '6' then ~
That's it. There should be no more Drupal messages in the /var/log/messages file.
I wanted to flash a custom firmware on an HTC Desire S because I didn’t like the Sense interface HTC installed on the device. It felt sluggish and I think it was ugly.
I have unlocked the bootloader on htcdev.com, rooted the device, and installed ClockworkMod (cwm). I chose a rom that seemed usefull (in this case CyanogenMod), and copied the cwm image (.zip file) to my sd-card, and booted into recovery. Here I made a backup of the current rom, did a full wipe, and flashed the image. After this I rebooted the device, expecting to see my new rom boot.
Instead of booting, all I saw was a white screen with the letters HTC in green on an white background. This state is named bootloop.
After flashing back the original rom, the device booted without problems.
I have tried several roms, all with exacly the same problem. After a lot of online research i have finally a booting custom rom. The solution was to flash the correct boot.img file for your rom to the device with the fastboot utility. The file boot.img is in the .zip file of the rom you chose. Flashing the boot.img can be done this way:
- Boot the HTC in fastboot mode by powering on the device while holding the Volume – button, and choosing fastboot
- Connect the phone to your computer with an micro-USB cable
- Flash the boot.img you extracted from the custom firmware:
fastboot flash boot <path to boot.img>
- Reboot the phone
After these steps your HTC Desire S should boot the custom rom as expected!