Blog

It is quite annoying that our Google Analytics traffic statistics are adversely affected by our own visits or those of any member of our team (internal traffic). Even more in early stages of websites, while still receives little traffic and our activity is a greater percentage compared to the total activity. Not only modifies appreciably the number of visits per se, but also the number of page views per visit, bounce rate and average time spent per user among many other parameters. This makes sense, as it is when we spend more time reviewing each and every one of our web pages or performing unfinished development tasks.

Those who use the tool KeePassX (KeePass clone for Linux and Mac OS X) to safely save passwords and login details at one single place will have seen many times on the need for rapid access to their repository of passwords with a single click. However, by default when accessing KeePassX none repository is open, or one is open that does not correspond to the one we want to check, so often it’s necessary to browse the file system to locate and select the corresponding file. If in addition to a master password we use a key file to improve security, we have to repeat the same process over and over again to locate and select the key file.

The simplest and shortest method to measure the number of processors present on a Linux box, which is also widely extended as it’s part of coreutils is:

Another way to get the same result which also allows us to obtain additional information from our processor are the lscpu command:

Or we can examine the cpuinfo file from /proc filesystem:

There are many additional details about these processors in /proc/cpuinfo file, including the CPU model and number of cores: