In Visual Studio Code, terminal may set GEM_HOME and GEM_PATH environment variables to incompatible values for vagrant. In such case you may see the following error:
can't find gem vagrant (>= 0.a) with executable vagrant
Impressive error and hard to find when you use unnamed semaphores and you place them on a shared memory segment .
The most important issue you have to be aware of is the following:
All of the system calls that work with memory maps may malfunction if you give them offsets or sizes that aren’t a multiple of the system page size. (They’re supposed to round up for you, but historically there have been a lot of bugs in this area.) You get the system page size by calling sysconf(_SC_PAGESIZE), and you round up with a little helper function shown below.
So if you place unnamed semaphores to a shared memory segment and you calculate offsets manually you have to check that the semaphores are placed in multiples of the system page size.
An easy way is to place all semaphores in the beginning of the segment since the sizeof(sem_t) is a multiple of the page size.
Trackpoint is more evil than good. Maybe some people find it useful but i certainly am not.
On some computers if you apply pressure around the touchpad or on the touchpad buttons, it short-circuits making the pointer moving automatically to a direction (usually towards right). Usually it stops moving after a while but most people have no idea what is happening.
The simplest fix is to disable the trackpoint completely.
If you cannot connect to a MySQL server via SSH in MySQL Workbench, you should take into account that MySQL workbench cannot use OPEN SSH keys but only RSA keys. So a common cause is that the key you have is in OpenSSH format.
You can convert OpenSSH keys to RSA. The following command will do the conversion for you but keep in mind that it will overwrite the existing key so you should take a backup if you still needed.
You must be logged in to post a comment.