Feeds:
Posts
Comments

Posts Tagged ‘solution’

I have configured a custom location for photostream on my windows machine, since I don’t want to fill up my C drive. All this while, this seemed to work without any issues. However, recently after updating to iOS 7 and iCloud 3.0.3 my photostream stopped syncing on my windows machine. It was weird because while all my shared photo streams continued to sync, my “My Photostream” didn’t sync at all. I tried various things like re-installing iCloud Control Panel, resetting my phone etc., but nothing seem to work.

I noticed that in the new iCloud Control Panel 3.0.x, the default location for photostream is changed from “[User Documents]\Pictures\Photo Stream” to “[User Documents]\Pictures\iCloud Photos”. I suspected that developers in Cupertino must have overlooked some bugs in iCloud Control Pamel 3.0.x (as they did in iOS 7) which would have crept in because of the change in default location. I therefore tried the following experiment, and voila, my photostream started to sync again.

Basically, I created a junction link between “[User Documents]\Pictures\iCloud Photos” and the custom location where i wanted my photos to sync. Junction link is similar to a hard link in unix/linux machines. To create a junction link you should first sign out of any running instance of iCloud control panel and quit it. Then run the following commands at command prompt, and launch iCloud control panel again.


prompt>mkdir "[custom path]"
prompt>mklink /j "[User Documents]\Pictures\iCloud Photos" "[custom path]"

Problem solved! 🙂

Advertisements

Read Full Post »

Atheros 9k series based wireless cards are among the most commonly found wireless networking cards on laptops. While Linux Kernel 2.6 and later provide support for these cards through ath9k module/driver, madwifi is also an option for some.

Despite the card’s popularity and integrated module availability, the driver is not bug-free. Users of all flavors of Linux (to name a few: RHEL 5,6; Centos 5,6; Ubuntu 11.x,12.x; FC 12,13) seem to have had issues with this driver. The two most commonly reported issues are slow wireless connectivity and wireless network disconnecting intermittently – either due to inactivity or after coming out of suspend/hibernate. The latter issue also sometimes manifests itself as the network card refusing to “come up”.

Here is an easy fix that fixes both issues. It has been tried and tested to fix the issues on at least the above mentioned Linux distros and should also work on other distros that use ath9k module.

Run the following commands as root (or prefix sudo)
Add the option nohwcrypt for ath9k: this removes the hardware based encryption and moves it to software

echo "options ath9k nohwcrypt=1" > /etc/modprobe.d/ath9k.conf

Turn off the automatic power management for your wireless card

iwconfig wlan0 power off

Now Reboot.

Alternatively, instead of rebooting you can perform the steps below
Unload the driver and reload it again

modprobe -rv ath9k
modprobe ath9k

Restart the network manager service

service NetworkManager restart

Now you are all set. Have fun!

Read Full Post »

Often RDS users trying to import data face this error when they try to create triggers:

ERROR 1419 (HY000) at line 49: You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)

The reason for this is that the default DB parameter group doesn’t have the privileges set to create and insert triggers into the database. To get rid of this error, do the following:

  1. Obtain RDS CLI tools from AWS website here, and follow the installation steps.
  2. On your terminal (or command line) create a new parameter group (since we can’t directly modify the default parameter group)
    rds-create-db-parameter-group allow-triggers --db-parameter-group-family mysql5.5 --description "parameter group to allow triggers"
  3. Now modify the parameter group created just now
    rds-modify-db-parameter-group allow-triggers --parameters "name=log_bin_trust_function_creators, value=true, method=immediate"
  4. Apply the new group to the database
    rds-modify-db-instance --db-instance-identifier instance-name --db-parameter-group-name allow-triggers --apply-immediately
  5. Finally, you will need to restart your RDS instance.

After running the above you should be able to import your schema/data and create triggers without problem. In case you receive the following error while using mysqldump

ERROR 1227 (42000) at line 2492: Access denied; you need (at least one of) the SUPER privilege(s) for this operation.

then, the problem is with the definer statement in your trigger. Change it from

DEFINER=user_a@localhost

to something like

DEFINER=correctuser@ip

Read Full Post »