/usr/local/bin vs /usr/bin

https://unix.stackexchange.com/questions/8656/usr-bin-vs-usr-local-bin-on-linux

1. /bin (and /sbin) were intended for programs that needed to be on a small / partition before the larger /usr, etc. partitions were mounted. These days, it mostly serves as a standard location for key programs like /bin/sh, although the original intent may still be relevant for e.g. installations on small embedded devices.

2. /sbin, as distinct from /bin, is for system management programs (not normally used by ordinary users) needed before /usr is mounted.

3. /usr/bin is for distribution-managed normal user programs.

4. There is a /usr/sbin with the same relationship to /usr/bin as /sbin has to /bin.

5. /usr/local/bin is for normal user programs not managed by the distribution package manager, e.g. locally compiled packages. You should not install them into /usr/bin because future distribution upgrades may modify or delete them without warning.

6. /usr/local/sbin, as you can probably guess at this point, is to /usr/local/bin as /usr/sbin to /usr/bin.

In addition, there is also /opt which is for monolithic non-distribution packages, although before they were properly integrated various distributions put Gnome and KDE there. Generally you should reserve it for large, poorly behaved third party packages such as Oracle.

Mongodb /etc/mongod.conf

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

processManagement: fork: true net: bindIp: localhost port: 27017 storage: dbPath: /var/lib/mongo systemLog: destination: file path: "/var/log/mongodb/mongod.log" logAppend: true storage: journal: enabled: true

https://docs.mongodb.com/manual/reference/configuration-options/

https://docs.mongodb.com/manual/administration/configuration/#std-label-base-config

NACL vs Route Table vs SecurityGroup

 

How to mount AWS EFS Drive to Linux EC2 Instance

sudo su user1-

sudo yum install nfs-utils

mkdir -p /fileshare

chown user1:usergrp1 /fileshare

chmod ugo+rwx /fileshare

sudo vi /etc/fstab

--Get Info from Attach EFS from AWS [You need Network Access ]

fs-123456.efs.us-east-1.amazonaws.com:/ /fileshare nfs4 rw,intr,hard,_netdev,nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport

sudo mount -a

sudo reboot now

EFS is regional 

Lambdas

https://www.educative.io/blog/java-lambda-expression-tutorial

SAML vs OAUTH

 https://www.ubisecure.com/uncategorized/difference-between-saml-and-oauth/

Docker: Docker Commands : Exhaustive

docker image pull <image>
docker image ls

docker container run <image> 
docker container run <image> --name  <containerName>

docker container run <image> -d

docker container run <image> -p HostPort:ContainerPort
docker container run -it <image> command

docker container 

docker container start <container>
docker container start -at <container>

docker container exec -it  <container>  command

docker container top

Would the following two commands create a port conflict error with each other?
NO ? Why ?
Each of below lines creates own containers

docker container run -p 80:80 -d nginx
docker container run -p 8080:80 -d nginx