SoftwareEngineering

chgrp -R Users ~/.ssh

-rw-------

Here’s how you can fix the root cause:

chmod 600 ~/.ssh/id_rsa

cat /etc/group | egrep '^Users:' | cut -f3 -d':'

value was 545

cat /etc/passwd | egrep '^Vineet:' | cut -f4 -d':'

value was 513 (which was the value for the ‘None’ group in /etc/group)

Class Loading in AS7

mysqld --init-file=C:\\mysql-init.txt

For INSERT statements where the number of rows to be inserted is known at the beginning of processing the statement, InnoDB quickly allocates the required number of auto-increment values without taking any lock, but only if there is no concurrent session already holding the table-level AUTO-INC lock (because that other statement will be allocating auto-increment values one-by-one as it proceeds)

innodb_autoinc_lock_mode = 0 (“traditional” lock mode)

special table-level AUTO-INC lock is obtained and held to the end of the statement

lock mode is provided for:

innodb_autoinc_lock_mode = 1 (“consecutive” lock mode)

important impact of this lock mode is significantly better scalability

This mode is safe for use with

innodb_autoinc_lock_mode = 2 (“interleaved” lock mode)

This is the fastest and most scalable lock mode

but it is

Using auto-increment with replication

set innodb_autoinc_lock_mode to 0 or 1 and use the same value on the master and its slaves

If you are using

all of the auto-increment lock modes are safe

init_connect

init_connect

executed by the server for each client that connects

one or more SQL statements, separated by semicolon characters