Linux commands

read -s LDAP_USER
read -s LDAP_PASSWORD
read -s LDAP_SERVER

echo "LDAP_USER: $LDAP_USER"
echo "LDAP_PASSWORD: $LDAP_PASSWORD"
echo "LDAP_SERVER: $LDAP_SERVER"

# Retrieve entries from administrative databases such as passwd and group
getent
# list members of a group
getent group group_name
# check if user belongs to ldap group
getent group yg-nas-quant-z | grep "s4X9Xf"
# Display the current user ID and group ID, and all associated groups
id username
# Display all groups a user belongs to
groups username
# check if multiple users belong to a server
getent netgroup LSP7077A | grep -E "S2XXF|S30XX|s7XXc|s8XXf"
# check if user belongs to a server
getent netgroup servername | grep username

# Show last logged in users
last
# display bad login attempts of specified user
lastb username
# shows logged-in users and their activities
w

cat /etc/sudoers

# Edit the sudoers configuration file safely
visudo

chown
chmod

# my tip is use setgid on parent directory, that is inherited and then
# use setfacl on the group, that would give them the access needed.
# attempt with Pitkänen, Arto, but it still does not work

setfacl -Rm g:quant:rwX -m d:g:quant:rwX -m m:rwx /[directory of choice]

# display kernel ring buffer messages
dmesgn
# server uptime
uptime
# check server ram
free -g -h -t
# detailed ram info
cat /proc/meminfo
# same like above just summarized and in GB
cat /proc/meminfo | grep -E 'MemTotal|MemFree|MemAvailable|Buffers|Cached' | awk '{print $1 ": " $2/1024/1024 " GB"}'
# check server cores
lscpu
# to see which pkg:s that was updated during the last patch round. I think that
# is the best way. good after tsw's
rpm -qa -last | more

# look for a word "mas" in ALL files(their content)
grep -r "mas" .
# search for files on the whole server by supressing error messages
find / -type f -name "viya-services-status.yml" 2>/dev/null

# creates a symbolic link(symlink) named "html" in the current directory that points to the "/opt/app/html" directory.
ln -s /opt/app/html html
# find out how big are the folders
du -sh /opt/app/*
# show disk usage statistics
df -h
# estimate file space usage
du
# size of the folder/file
du -sh filename/foldername
# see when file was created, modified last time and etc
stat filename.txt
# cd into dir, shows how much each item in it takes space
du -skh *
# shows files
sudo lsof +L1
# ask for confirmation deleting each folder/file
rm -rri /opt/app/R/*
# list ALL the folders of the current folder
find retail_modelling -type d > test_output.txt
# count how many things in the dir
ls -la | wc -l
# Check when file was created and stuff
stat /opt/app/retail_modelling/users/s5743b/fi_kort_rc_ttc.tsv
# check top 10 biggest files in home dir
du -h /home | sort -rh | head -n 10

fuser -c /opt/app/

ps -ef | grep 2666631

ps -ef | grep rstudio

ps aux | grep -i rstudio

ps aux | grep -i jupyter

kill -9 <processname form the previous command>

ps                              # show running processes

ps aux | grep SXXXB | grep rstudio

pkill -u sxxxxxf              # - NEVEIKIA
killall -u sxxxxxf rsession   # - NEVEIKIA
pkill -9 -u sxxxxxf rsession  # - SUVEIKE

kill all rstudio sessions
sudo killall -9 rserver

pgrep rserver                   # Check if any services remaining

systemctl list-units --type=service | grep sas-viya # check all services by name
ps aux | grep sas-viya

sudo systemctl stop sas-viya-*  # kill all services by name

# show the IP routing table
route
# find all aliases/DNS of a Linux server that are assigned or being used
nslookup <IP address or hostname>
# same as above
dig -x <IP address>
# show you a list of all active network connections and their associated ports
netstat -tlnp

# find if port 80 is being used
netstat -tuln | grep :80
# check what ports are running on the servers
nmap -T4 -Pn -p 1-65535 lxxx123a
# telnet
telnet servername 8301
telnet serername.ad1.net 1433

journalctl -u jupyterhub -f

journalctl -u rstudio-server.service -f

ansible-playbook viya-ark-master/playbooks/viya-mmsu/viya-services-status.yml -vvv 2>&1 | tee -a viya_services_status_logs_20230727.txt
ansible-playbook viya-ark-master/playbooks/viya-mmsu/viya-services-stop.yml -e "enable_stray_cleanup=true" -vvv 2>&1 | tee -a viya_services_stop_logs_20230727.txt
ansible-playbook viya-ark-master/playbooks/viya-mmsu/viya-services-start.yml -vvv 2>&1 | tee -a viya_services_start_logs_20230727.txt

# sas installation logs to file

ansible-playbook site.yml -vvv 2>&1 | tee -a install_20230809_1500.txt

# Use yum whatprovides to see what package provides a file.
yum whatprovides */ldapsearch
# Can see that ldapsearch is part of =openldap-clients=
# before installing we can check the content:
repoquery -lq openldap-clients
# all is good? install
yum install openldap-clients

yum history
yum list installed | grep devel
yum remove <reponame>
yum erase <reponame>
yum repolist all
yum repolist enabled
yum search 'udunit*' --enablerepo=hello_Extra_Packages_for_Enterprise_Linux_epel8
yum search 'R-*' --disablerepo='*' --enablerepo=hello_Extra_Packages_for_Enterprise_Linux_epel8
yum info 'R-devel' --disablerepo='*' --enablerepo=hello_Extra_Packages_for_Enterprise_Linux_epel8
sudo yum install 'udunits2-devel' --enablerepo=hello_Extra_Packages_for_Enterprise_Linux_epel8 --enablerepo=codeready-builder-for-rhel-8-x86_64-rpms
# list all available red hat repos
yum repolist all
# search for package in all repos + EPEL8 repo
yum search 'R-*' --disablerepo='*' --enablerepo=hello_Extra_Packages_for_Enterprise_Linux_epel8
# search EPEL8 repo
yum info 'R-devel' --disablerepo='*' --enablerepo=hello_Extra_Packages_for_Enterprise_Linux_epel8
# install from EPEL8 repo
sudo yum install 'R-devel' --enablerepo=hello_Extra_Packages_for_Enterprise_Linux_epel8 --enablerepo=codeready-builder-for-rhel-8-x86_64-rpms

crontab -l                    # view your own user's crontab
crontab -e                      # edit your own user's crontab
crontab -r                      # remove your own user's crontab:

tar -cvf archive_name.tar files_or_directories_to_archive
tar -cvf labas.tar .

# list all drives?
cat /etc/fstab
# get mount name
mount -l |grep sas-store

nc -vz dbname 1433
ping dbname


# You can list the data sources on your system with the following command:
odbcinst -q -s

# NOTE. You can determine the location of the configuration files on your
# system by entering the following command into a terminal:
odbcinst -j

# Check what ODBC drivers are installed for required DB in "/etc/odbcinst.ini"
odbcinst -q -d


tsql -S dbname -U username
select name from sysdatabases
quit

:set paste
:set nopaste

:set nonu
:set nu

# no highlighting:

:noh

ansible-galaxy collection list

# install default version
ansible-galaxy collection install community.general

# install specific version:
ansible-galaxy collection install geerlingguy.apache,v1.0.0

7.0.1