Search This Blog

Loading...

Saturday, July 25, 2015

Solution : Google Authenticator continuously crashes



This happened to me when i moved from one phone to other. on investigation i understood that google only allows one authentication device. as on the old phone this setup was already done, The only easy option is to move the authentication to a different phone.

Following is the few step process that worked for me.

  1. Open Authenticator but do NOT press the “Begin setup” button.
  2. Instead, select “setup account” from the option menu.
  3. Then from another device/computer, go to https://accounts.google.com/b/0/SmsAuthSettings, select “Move to a different phone” and scan the QR code.

Friday, July 17, 2015

Linux server filesystem go read-only


First check how the system believes / is supposed to be mounted:

 

        mount|grep -i " / "


Should look something like this:


        /dev/mapper/VolGroup000-LogVol00 on / type ext3 (rw)

 

Might also be worth running a "cat /etc/fstab" and take a look to make sure there isn't a read-only option set in field four of the / entry.

 

If it is supposed to be (rw), then this should work:

 

        mount -o remount /

 

If it is being intentionally mounted (ro), then try this:

 

        mount -o remount,rw /

 


If that appears to work, make sure it survives a reboot (after checking fstab again).

 

 

Failing that, reboot in single user mode and run fsck on the disk in question to check and repair the Linux file system.  Invoke fsck without parameters and it should check everything listed in /etc/fstab.


 

        fsck

 

 

 

Thursday, February 26, 2015

cmake configure_file not replacing variables

most probably you may have

configure_file( in
                        out                       
                       @only )

here @only tells the cmake to only replace the variable defined like @variable@ and not to replace ${variable}