Find out the configuration with which the nfs client is connected to the nfs server.
Bouncing my head to my keyboard while trying to find out where is the bottleneck on an nfs client-server relationship, I found out how to see the configuration with which the nfs client is connect to the server:
And the output is:
/nfsshare from nexenta.nfs-servers.example.com:/volumes/datastore/dataset/
Knowing exactly how the client is connected to the server, you can find more easily where the problem is.
Using the nfsstat -m command, you get the information about all nfs mounts. The -m switch is present on centOS, but abscent on FreeBSD, in which I do also performance tests.
You can also find all this information and also all the information about all mounts ( not only nfs mounts) if you execute:
I am trying to get this info on FreeBSD, if everyone knows everything about this, please post a comment. I also asked a question at http://unix.stackexchange.com/questions/91594/nfs-mount-properties-options-in-freebsd to help me find the solution.
Mercurial is a free, distributed source control management tool. It efficiently handles projects of any size and offers an easy and intuitive interface. You can setup mercurial on a server just to keep your teams repository. It’s pretty easy to install it to your CentOS machine , or vm. You can just run the command:
yum install mercurial
and that’s all. I think that it’s easy to install it to other Linux distributions too. Now all you have to do is to add a group for the developers and a user for each of them to have access to the repositories.
If your team of developers use windows as their primary operating system Mercurial is the right choice for a scm. Mercurial just works on Windows. The definitive Mercurial book (written by Bryan O’Sullivan – a fellow Irishman) is concise, and exhaustive. Better yet, if you want that warm fuzzy feeling a GUI gives you, then look no further than TortoiseHg – a top quality tool. It’s good to learn Mercurial mainly on the command line. I wanted to understand how Mercurial worked, and how it is different from SVN.
To install openssh on a CentOS:
yum install openssh
And if you want to install the client (ssh command) you have to run:
yum install openssh-clients
If you want to use on of the linux commands:
dig, host or nslookup on a CentOS machine and you get the error message:
-bash: nslookup: command not found
you have to install the bind-utils package.
Just run the command:
yum install bind-utils
If you want to determine the version of the CentOS or Redhat Operating System installed you have to execute a simple command: