rm -rf . | wildcards | m5sum loop

By OK -
rf -rf .  - will remove everything from the current directory downward
rf "-rf ." - will remove file named -rf .

ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$ ll
total 8
drwxrwxr-x 2 ubuntu2 ubuntu2 4096 Jul 20 11:06 ./
drwxrwxr-x 3 ubuntu2 ubuntu2 4096 Jul 20 11:00 ../
-rw-rw-r-- 1 ubuntu2 ubuntu2    0 Jul 20 11:05 file-1
-rw-rw-r-- 1 ubuntu2 ubuntu2    0 Jul 20 11:06 file-2
-rw-rw-r-- 1 ubuntu2 ubuntu2    0 Jul 20 11:06 file-3
ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$

ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$ ll *[-12]
-rw-rw-r-- 1 ubuntu2 ubuntu2 0 Jul 20 11:05 file-1
-rw-rw-r-- 1 ubuntu2 ubuntu2 0 Jul 20 11:06 file-2
ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$

to find - or [ put it into []
------------
touch *f*.dot
rm \*f\*.dot
------------
rm -rf *
ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$ ll
total 8
drwxrwxr-x 2 ubuntu2 ubuntu2 4096 Jul 20 11:50 ./
drwxrwxr-x 3 ubuntu2 ubuntu2 4096 Jul 20 11:00 ../
-rw-rw-r-- 1 ubuntu2 ubuntu2    0 Jul 20 11:49 .test
------------

 ll
total 8
drwxrwxr-x 2 ubuntu2 ubuntu2 4096 Jul 20 11:51 ./
drwxrwxr-x 3 ubuntu2 ubuntu2 4096 Jul 20 11:00 ../
-rw-rw-r-- 1 ubuntu2 ubuntu2    0 Jul 20 11:51 file1
-rw-rw-r-- 1 ubuntu2 ubuntu2    0 Jul 20 11:51 file2
-rw-rw-r-- 1 ubuntu2 ubuntu2    0 Jul 20 11:51 file3
-rw-rw-r-- 1 ubuntu2 ubuntu2    0 Jul 20 11:49 .test
ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$ set -o noglob
ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$ rm *
rm: cannot remove ‘*’: No such file or directory
ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$ ll
set +o noglob
ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$ rm *
ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$ ll
total 8
drwxrwxr-x 2 ubuntu2 ubuntu2 4096 Jul 20 11:52 ./
drwxrwxr-x 3 ubuntu2 ubuntu2 4096 Jul 20 11:00 ../
-rw-rw-r-- 1 ubuntu2 ubuntu2    0 Jul 20 11:49 .test
ubuntu2@ubuntu2:~/temp/newdir1/dir2/dir3$
------------

for filename in a* b*; do md5sum $filename; done
a45888e194263277c3609efd9ce69707  a1
7813db75db95e759afd971d5c92d5b7e  a2
ba4944388cdb14df5ff14b0e27303cb2  a3
5c8ed45495853061ab86e961bdbb0e48  a4
---------------------

Comments

Post a Comment

Popular posts from this blog

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 global mode http option httplog option dontlognull         contimeout 5000    
Read more

tomcat catalina coyote jasper cluster

By OK -
Tomcat Component are Catalina Coyote Jasper Cluster Catalina :  Catalina is the name of the servlet container of Apache Tomcat since version 4.x. Tomcat implements Sun Microsystems' specifications for servlet and JavaServer Pages (JSP), which are important Java-based Web technologies. Tomcat's servlet container was redesigned as Catalina in Tomcat version 4.x. other components of the Tomcat engine are: Tomcat Jasper which converts the code portions within JavaServer Pages into servlets and pass them to Catalina to process. Tomcat Coyote which is an HTTP connector based on HTTP/1.1 specifications that receives and transmits web requests to the Tomcat engine by listening to a TCP/IP port and returns requests back to the requesting client. Coyote :  The Coyote JK Connector element represents a Connector component that communicates with a web connector via the JK protocol (also known as the AJP protocol). This is used for cases where you wish to invisibly integr
Read more

NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

By OK -
Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availability ssh   ports:   protocols:   masquera
Read more