When i transfer my private key file to my new Mac OS X, i got an error message below:-
If you are getting this error then you probably reset the permissions on your hidden .ssh directory in your user folder.
So, the solution for this is, make that file(id_rsa) readable or writable only for the owner with private key. Below is the command
sudo chmod 600 ~/.ssh/id_rsa
After change the permission, my problem is solved.
If you recently update your BIND server to version 9.9.X, you will noticed that you unable to read slave zone file.
Below is the example of zone file
As per checking on BIND official release notes from ISC, BIND version 9.9.x store Slave Zones file in raw/binary format.
In order to view the content of Slave Zone file, you need to convert “raw” format zone files to “text” format using the named-compilezone utility that comes with BIND. Continue reading
Error Message “Existing lock /var/run/yum.pid: another copy is running as pid xxxx.” is a very common error which you might come across in Red Hat Linux distro while trying to run yum command.
As you see the error from above screenshot, it mentioned that yum command is locked by another application. Meaning that someone already run the yum command and the process is running.
To find out which process and user holding the yum lock, just enter following command:-
From the above screenshot, PID 11290 is currently run by root user and holding the yum lock.
It is very easy to solve this issue, first wait the process finished. Second is kill the process ID. Below is the command to kill the PID
kill -9 11290
Now you should able to use yum command.