PS1 prod test example with color

By OK -
PS1='\[\e[1;31m\][test]\[\e[1;32m\][\u@\h \W]\$\[\e[0m\] '
PS1='\[\e[1;35m\][test]\[\e[1;32m\][\u@\h \[\e[1;34m\]\W]\$\[\e[0m\] '

Comments

Post a Comment

Popular posts from this blog

15 managing disk - understanding /etc/fstab xfs_admin mount -o rw,remount /

By OK -
the classical way to mount filelsystems automatically is to use fstab there is another method which is based on systemd [root@svn ~]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Wed Apr 26 17:25:59 2017 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/cl-root     /                       xfs     defaults        0 0 UUID=6e3708b2-09ea-43f3-b0f0-9b43a157b3b1 /boot                   xfs     defaults        0 0 /dev/mapper/cl-swap     swap                    swap    defaults        0 0 [root@svn ~]#  #description /boot - where you want to mount filesystem xfs - filesystem defaults ...
Read more

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log ...
Read more

write safe shell scripts set -euf set -o pipefail

By OK -
et -euf -o pipefail In dash,  set -o  doesn't exist, so use only  set -euf . What do those do? set -e If a command fails,  set -e  will make the whole script exit, instead of just resuming on the next line. If you have commands that can fail without it being an issue, you can append  || true  or  || :  to suppress this behavior — for example  set -e  followed by  false || :  will not cause your script to terminate. set -u Treat unset variables as an error, and immediately exit. set -f Disable filename expansion (globbing) upon seeing  * ,  ? , etc.. If your script depends on globbing, you obviously shouldn't set this. Instead, you may find  shopt -s failglob  useful, which causes globs that don't get expanded to cause errors, rather than getting passed to the command with the  *  intact. set -o pipefail set -o pipefail  causes a pipeline (for example,  curl -s ...
Read more