安科网

k8s安装dashboard(未解决)

CurrentJ

CurrentJ

2020-01-07

关注 关注

第一种，用helm安装

helm repo update
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
[root@k8s-master templates]# helm repo list
NAME    URL
stable  https://kubernetes-charts.storage.googleapis.com
local   http://127.0.0.1:8879/charts
[root@k8s-master templates]# helm fetch stable/kubernetes-dashboard
[ templates]# ls
deployment.yaml  kubernetes-dashboard-1.10.1.tgz  service.yaml
[root@k8s-master templates]# tar -zvxf kubernetes-dashboard-1.10.1.tgz
kubernetes-dashboard/Chart.yaml
tar: kubernetes-dashboard/Chart.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/values.yaml
tar: kubernetes-dashboard/values.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/NOTES.txt
tar: kubernetes-dashboard/templates/NOTES.txt：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/_helpers.tpl
tar: kubernetes-dashboard/templates/_helpers.tpl：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/clusterrole-readonly.yaml
tar: kubernetes-dashboard/templates/clusterrole-readonly.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/deployment.yaml
tar: kubernetes-dashboard/templates/deployment.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/ingress.yaml
tar: kubernetes-dashboard/templates/ingress.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/networkpolicy.yaml
tar: kubernetes-dashboard/templates/networkpolicy.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/pdb.yaml
tar: kubernetes-dashboard/templates/pdb.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/role.yaml
tar: kubernetes-dashboard/templates/role.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/rolebinding.yaml
tar: kubernetes-dashboard/templates/rolebinding.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/secret.yaml
tar: kubernetes-dashboard/templates/secret.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/serviceaccount.yaml
tar: kubernetes-dashboard/templates/serviceaccount.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/templates/svc.yaml
tar: kubernetes-dashboard/templates/svc.yaml：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/.helmignore
tar: kubernetes-dashboard/.helmignore：不可信的旧时间戳 1970-01-01 08:00:00
kubernetes-dashboard/README.md
tar: kubernetes-dashboard/README.md：不可信的旧时间戳 1970-01-01 08:00:00
[root@k8s-master templates]# cd kubernetes-dashboard/
[ kubernetes-dashboard]# ll
总用量 28
-rwxr-xr-x 1 root root   468 1月   1 1970 Chart.yaml
-rwxr-xr-x 1 root root 12858 1月   1 1970 README.md
drwxr-xr-x 2 root root   264 1月   6 21:50 templates
-rwxr-xr-x 1 root root  5470 1月   1 1970 values.yaml
[root@k8s-master kubernetes-dashboard]# vim kubernetes-dashboard.yaml
[ kubernetes-dashboard]# ll
总用量 32
-rwxr-xr-x 1 root root   468 1月   1 1970 Chart.yaml
-rw-r--r-- 1 root root   376 1月   6 21:58 kubernetes-dashboard.yaml
-rwxr-xr-x 1 root root 12858 1月   1 1970 README.md
drwxr-xr-x 2 root root   264 1月   6 21:50 templates
-rwxr-xr-x 1 root root  5470 1月   1 1970 values.yaml
[ kubernetes-dashboard]# helm install . \
> -n kubernetes-dashboard > --namespace kube-system > -f kubernetes-dashboard.yaml
NAME:   kubernetes-dashboard
LAST DEPLOYED: Mon Jan  6 22:03:50 2020
NAMESPACE: kube-system
STATUS: DEPLOYED

RESOURCES:
==> v1/Deployment
NAME                  READY  UP-TO-DATE  AVAILABLE  AGE
kubernetes-dashboard  0/1    1           0          0s

==> v1/Pod(related)
NAME                                  READY  STATUS             RESTARTS  AGE
kubernetes-dashboard-bfdf5fc85-vrgqg  0/1    ContainerCreating  0         0s

==> v1/Role
NAME                  AGE
kubernetes-dashboard  0s

==> v1/RoleBinding
NAME                  AGE
kubernetes-dashboard  0s

==> v1/Secret
NAME                  TYPE    DATA  AGE
kubernetes-dashboard  Opaque  0     0s

==> v1/Service
NAME                  TYPE       CLUSTER-IP    EXTERNAL-IP  PORT(S)  AGE
kubernetes-dashboard  ClusterIP  10.107.6.189  <none>       443/TCP  0s

==> v1/ServiceAccount
NAME                  SECRETS  AGE
kubernetes-dashboard  1        0s

==> v1beta1/Ingress
NAME                  HOSTS            ADDRESS  PORTS  AGE
kubernetes-dashboard  k8s.frognew.com  80, 443  0s


NOTES:
*********************************************************************************
*** PLEASE BE PATIENT: kubernetes-dashboard may take a few minutes to install ***
*********************************************************************************
From outside the cluster, the server URL(s) are:
     https://k8s.frognew.com
[ kubernetes-dashboard]# kubectl get svc -n kube-system
NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE
kube-dns               ClusterIP   10.96.0.10       <none>        53/UDP,53/TCP,9153/TCP   17d
kubernetes-dashboard   ClusterIP   10.107.6.189     <none>        443/TCP                  110s
tiller-deploy          ClusterIP   10.102.114.107   <none>        44134/TCP                23h
[root@k8s-master kubernetes-dashboard]# kubectl edit kubernetes-dashboard -n kube-system
error: the server doesn‘t have a resource type "kubernetes-dashboard"
[root@k8s-master kubernetes-dashboard]# kubectl edit svc kubernetes-dashboard -n kube-system
service/kubernetes-dashboard edited
[root@k8s-master kubernetes-dashboard]# kubectl get svc -n kube-system
NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE
kube-dns               ClusterIP   10.96.0.10       <none>        53/UDP,53/TCP,9153/TCP   17d
kubernetes-dashboard   NodePort    10.107.6.189     <none>        443:31961/TCP            3m39s
tiller-deploy          ClusterIP   10.102.114.107   <none>        44134/TCP                23h
[root@k8s-master kubernetes-dashboard]# kubectl -n kube-system get secret | grep kubernetes-dashboard-token
kubernetes-dashboard-token-qxxpr                 kubernetes.io/service-account-token   3      4m56s
[root@k8s-master kubernetes-dashboard]# kubectl -n kube-system get secret | grep kubernetes-dashboard
kubernetes-dashboard                             Opaque                                0      5m5s
kubernetes-dashboard-key-holder                  Opaque                                2      4m59s
kubernetes-dashboard-token-qxxpr                 kubernetes.io/service-account-token   3      5m5s
[root@k8s-master kubernetes-dashboard]# kubectl -n kube-system get secret | grep kubernetes-dashboard-token-qxxpr
kubernetes-dashboard-token-qxxpr                 kubernetes.io/service-account-token   3      5m13s
[root@k8s-master kubernetes-dashboard]# kubectl describe secret kubernetes-dashboard-token-qxxpr -n kube-system
Name:         kubernetes-dashboard-token-qxxpr
Namespace:    kube-system
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: kubernetes-dashboard
              kubernetes.io/service-account.uid: 844c78bd-979b-478a-9c84-b5997706f8a4

Type:  kubernetes.io/service-account-token

Data
====
ca.crt:     1025 bytes
namespace:  11 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6IktTaWpWSDJoem5WTzNZdExreU9sV2dqLVpTa1NzVHdZeE56clZuZ2JxQncifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZC10b2tlbi1xeHhwciIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6Ijg0NGM3OGJkLTk3OWItNDc4YS05Yzg0LWI1OTk3NzA2ZjhhNCIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlLXN5c3RlbTprdWJlcm5ldGVzLWRhc2hib2FyZCJ9.HZviLVDSTdZ-n4Q08tYR_z5EGE1tAbTJ4vm7MEQ1haCD4HtnEGwgvvZmAsISNz38VHWh5ASIJW6CVHbU6a3Q7YYAp4jTVB9GMGNXaKKMIIgzNoMz_r_Sts0CCBcziotaVKMFiH5zudPm6TdJViAaCwrmCUZEL-mRel5QEOfT0MPq9KNI-0smmC3L2wKPlgfTT6MLx1pv3F5hQ5quZqXa2XUSLlUNpg1p8Vzan0KMCoXmgnax-u7BniA5HCIBqv7MZ1Yobo6v8dp2nE9o23f8yebyWT_dxSvZ59kenCpYlpLFxKKAcnko2w6Cg2PcV-qJydU-Y2xcNYOpke15HgITig
[ kubernetes-dashboard]# ll
总用量 32
-rwxr-xr-x 1 root root   468 1月   1 1970 Chart.yaml
-rw-r--r-- 1 root root   376 1月   6 21:58 kubernetes-dashboard.yaml
-rwxr-xr-x 1 root root 12858 1月   1 1970 README.md
drwxr-xr-x 2 root root   264 1月   6 21:50 templates
-rwxr-xr-x 1 root root  5470 1月   1 1970 values.yaml
[root@k8s-master kubernetes-dashboard]# cat kubernetes-dashboard.yaml
image:
  repository: k8s.gcr.io/kubernetes-dashboard-amd64
  tag: v1.10.1
ingress:
  enabled: true
  hosts:
    - k8s.frognew.com
  annotations:
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
  tls:
    - secretName: frognew-com-tls-secret
      hosts:
      - k8s.frognew.com
  rbac:
    clusterAdminRole: true

但是登陆的时候会报错，权限不足，暂时还没有办法解决

k8s安装dashboard(未解决)

 第二种，直接下载yaml文件

[ kubernetes-dashboard]# wget https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta8/aio/deploy/recommended.yaml
--2020-01-06 22:57:43--  https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0-beta8/aio/deploy/recommended.yaml
正在解析主机 raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.108.133
正在连接 raw.githubusercontent.com (raw.githubusercontent.com)|151.101.108.133|:443... 已连接。
已发出 HTTP 请求，正在等待回应... 200 OK
长度：7568 (7.4K) [text/plain]
正在保存至: “recommended.yaml”

100%[=====================================================================================================================>] 7,568       1.32KB/s 用时 5.6s

2020-01-06 22:57:51 (1.32 KB/s) - 已保存 “recommended.yaml” [7568/7568])
[ kubernetes-dashboard]# kubectl apply -f recommended.yaml
namespace/kubernetes-dashboard created
serviceaccount/kubernetes-dashboard created
service/kubernetes-dashboard created
secret/kubernetes-dashboard-certs created
secret/kubernetes-dashboard-csrf created
secret/kubernetes-dashboard-key-holder created
configmap/kubernetes-dashboard-settings created
role.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrole.rbac.authorization.k8s.io/kubernetes-dashboard created
rolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
clusterrolebinding.rbac.authorization.k8s.io/kubernetes-dashboard created
deployment.apps/kubernetes-dashboard created
service/dashboard-metrics-scraper created
deployment.apps/dashboard-metrics-scraper created
[root@k8s-master kubernetes-dashboard]# kubectl describe secret -n kubernetes-dashboard $(kubectl get secret -n kubernetes-dashboard | grep dashboard-admin | awk ‘{print $1}‘)
Name:         default-token-cthh2
Namespace:    kubernetes-dashboard
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: default
              kubernetes.io/service-account.uid: 48ff2cdb-321b-4775-8c87-28c3b6bafea8

Type:  kubernetes.io/service-account-token

Data
====
ca.crt:     1025 bytes
namespace:  20 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6IktTaWpWSDJoem5WTzNZdExreU9sV2dqLVpTa1NzVHdZeE56clZuZ2JxQncifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJkZWZhdWx0LXRva2VuLWN0aGgyIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6ImRlZmF1bHQiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiI0OGZmMmNkYi0zMjFiLTQ3NzUtOGM4Ny0yOGMzYjZiYWZlYTgiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6a3ViZXJuZXRlcy1kYXNoYm9hcmQ6ZGVmYXVsdCJ9.dYWLwxww6uepIfdUPfI443pquM9pGm4XzVKwO-tGMz27YdrNvxM1KsKsOjKwRkOVu6Gs1MmJO8LzcKh___uGf-gJvSw14MO9ITVR2g61bK0bNUH8pEiDaQQIsWwEbKgdiiqAu3syUA-9sv4FRH3PAmTqDOgURVF9vHqg_-93UnKnq5dqqowt2-LttDWwFplp59Gq95HCsoPGsF22JajRT84Wp_lk8jKmC6PFSTh4Lt28jbOqnJchDobMr48_B_St31S0y8RAZGfMYe6HrRpy-EDMSbzXYQYmyBw-srIbNPiiH4sbv3qdc-90aiu6NTV1NCVOhyN-Po3B_u-ym8BBAg


Name:         kubernetes-dashboard-certs
Namespace:    kubernetes-dashboard
Labels:       k8s-app=kubernetes-dashboard
Annotations:
Type:         Opaque

Data
====


Name:         kubernetes-dashboard-csrf
Namespace:    kubernetes-dashboard
Labels:       k8s-app=kubernetes-dashboard
Annotations:
Type:         Opaque

Data
====
csrf:  0 bytes


Name:         kubernetes-dashboard-key-holder
Namespace:    kubernetes-dashboard
Labels:       k8s-app=kubernetes-dashboard
Annotations:
Type:         Opaque

Data
====


Name:         kubernetes-dashboard-token-2tsg8
Namespace:    kubernetes-dashboard
Labels:       <none>
Annotations:  kubernetes.io/service-account.name: kubernetes-dashboard
              kubernetes.io/service-account.uid: f0a47104-2a7f-4dc4-80e7-06cbc2ca2c77

Type:  kubernetes.io/service-account-token

Data
====
namespace:  20 bytes
token:      eyJhbGciOiJSUzI1NiIsImtpZCI6IktTaWpWSDJoem5WTzNZdExreU9sV2dqLVpTa1NzVHdZeE56clZuZ2JxQncifQ.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZC10b2tlbi0ydHNnOCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50Lm5hbWUiOiJrdWJlcm5ldGVzLWRhc2hib2FyZCIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VydmljZS1hY2NvdW50LnVpZCI6ImYwYTQ3MTA0LTJhN2YtNGRjNC04MGU3LTA2Y2JjMmNhMmM3NyIsInN1YiI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDprdWJlcm5ldGVzLWRhc2hib2FyZDprdWJlcm5ldGVzLWRhc2hib2FyZCJ9.rNDeHhXHzWk33wiE0MQlSZwxPb-CGyryFVhqTMzigs2znv59QZOab6Ztt1o6rU8TJyMfk1wnKJeKEJdyT2x4W6XdoAmSsIHkUKtSixQiazFeWp6rkWABPW_-Co2AKzciltUK5Xtgd6_L-KWodGFCc3t0B12GvdMet1On63-GgM6X8SUOVtE9_htEbTrEfyMV5AG1DfzsVpOJFv4V-qQUaxmSexlaCi59_nbzoBLz125_3K_1fHckXd4j9Jb9v5mQ4WRL4oddN7Sm7OQCLQjErKBSbfO5cnsJvuFEceoHPDS8mkT7fU4vFflillfuJfZarHs5vYQYgpqre3X-UmruVA
ca.crt:     1025 bytes
[root@k8s-master kubernetes-dashboard]#

k8s安装dashboard(未解决)

 发现还是有问题，看不了信息

tar k8s kubernetes dashboard

CurrentJ

CurrentJ

0 关注 0 粉丝 0 动态

关注 关注

相关推荐

linux解压压缩文件zip/tar/tar.gz命令汇总

tar -czf jpg.tar.gz *.jpg //将目录里所有jpg文件打包成jpg.tar后，并且将其用gzip压缩，生成一个gzip压缩过的包，命名为jpg.tar.gz

benico 2020-07-04

Linux压缩总结

Linux下最常用的打包程序就是tar了，使用tar程序打出来的包我们常称为tar包，tar -cf all.tar *.jpg将所有.jpg的文件打成一个名为all.tar的包。-c是表示产生新的包，-f指定包的文件名。tar -rf all.tar *

jackalwb 2020-06-21

Linux下常用压缩格式的压缩与解压方法详解

解压后请将rar_static拷贝到/usr/bin目录：

linuxwcj 2020-06-14

【转】Linux中常用的tar解压打包命令语法介绍

常用的tar解压打包命令语法介绍1．命令格式2．命令功能3．命令参数4．常见解压/压缩命令5．使用实例1．命令格式tar[必要参数][选择参数][文件]. .tar.gz 和 .tgz解压：tar zxvf FileName.tar.gz压缩：tar zc

wintelx 2020-06-11

在 Linux 上压缩文件的 5 种方法

在 Linux 上有不少用于压缩文件的命令。最新最有效的一个方法是 xz，但是所有的方法都有节省磁盘空间和维护备份文件供以后使用的优点。在这篇文章中，我们将比较这些压缩命令并指出显著的不同。当使用 z 选项为 tar 命令附加压缩过程时，tar 使用 g

大孩爱小孩 2020-05-07

linux 中如何解压文件（比如.tar.gz 用tar

tar -xzvf .tar.gztar [-cxtzjvfpPN] 文件与目录 ....参数：-c ：建立一个压缩文件的参数指令；-x ：解开一个压缩文件的参数指令！特别注意，在参数的下达中， c/x/t 仅能存在一个！因为不可能同时压缩与解压缩。亦即是

zfyaixue 2020-02-24

linux中压缩解压缩命令

-rw-r--r--. 1 root root 655K Jun 7 2013 /etc/services. -rw-r--r-- 1 root root 133K Nov 29 17:45 /tmp/services.gz. Try `tar --h

神龙 2020-02-19

Linux基础命令（tar gzip）

tar cvf a.tar 1.txt 2.txt 把1.txt 2.txt文件打包至a.txt f必须放到最后，f后面的第一个参数代表要生成的文件名，后面所有的参数是要打包的文件。tar与gzip命令结合使用实现文件打包，压缩。

zmjzhangmj 2020-02-11

tar压缩文件 .tar.gz

tar xzf ansible.tar.gz tar xf ansible.tar.gz -C /tmp/

onepiecedn 2020-01-30

linux解压缩命令

解压缩后的文件只能放在当前的目录。.tar .tgz .tar.gz .tar.Z .tar.bz .tar.bz2 .zip .cpio .rpm .deb .slp .arj .rar .ace .lha .lzh .lzx .lzs .arc .sd

hickwu 2020-01-29

LINUX 常用命令集合

su su命令是最基本的命令之一，常用于不同用户间切换。完成之后就可以用exit命令返回到user1。su命令的常见用法是变成根用户或超级用户。如果登录为根用户，则可以用su命令成为系统上任何用户而不需要口令。cd cd命令不仅显示当前状态，还改变当前状态

qonsnow 2013-03-27

Linux tar 命令

因为不可能同时压缩与解压缩。另外，如果您进入 /usr/local/src/etc# 则会发现，该目录下的文件属性与 /etc/ 可能会有所不同喔！etc.tar.gz 内的根目录 / 是被拿掉了！[root@linux ~]# tar -zcvpf /t

xue0zhiqiang 2013-05-31

Linux文件压缩

*.Z compress 程序压缩的文件；*.tar tar 程序打包的数据，并没有压缩过；Linux 上常见的压缩指令就是 gzip, bzip2 以及最新的 xz ，至于 compress 已经不流行了。不过，单纯的 tar 功能仅是打包而已，亦即是将

sunln00 2019-12-15

Linux压缩&amp;解压缩

　　解压1：gunzip FileName.gz. 压缩多个文件：tar zcvf FileName.tar.gz DirName1 DirName2 DirName3 ...

安得情怀似旧时 2019-12-10

其他命令

查找文件find 命令功能非常强大，通常用来在 特定的目录下 搜索 符合条件的文件如果省略路径，表示在当前文件夹下查找之前学习的通配符，在使用 find 命令时同时可用有关 find 的高级使用，在就业班会讲。tar -jcvf 打

xiaohouye 2019-12-02

Linux gzip: stdin: not in gzip format

可能是文件不支持 gzip格式，所以去掉z就可以了

LUOPING0 2019-12-01

Linux/Ubuntu 解压 zip, tar,7z,gz,bz2,rar

To install p7zip on Ubuntu , launch the terminal and issue this command:. After installing this command line utility, you can ex

FruitDrop 2013-08-22

linux批量解压缩

为什么tar不支持这种通配符语法呢？为了防止 *.tar被shell解释为a.tar b.tar c.tar...＜tarfile.tar> 是选项f所要求的，只能是一个文件，比如myfiles.tar。<archived_file> 是

fickyou 2013-08-20

linux命令tar

[root@test flume]# tar --helpUsage: tar [OPTION...] [FILE]...GNU `tar' saves many files together into a single tape or disk arch

HeronLinuxampARM 2013-08-17

【linux 红帽子版 入门】安装tomcat (tar命令使用、查看进程、端口操作)

先说明一下 tar 命令压缩、解压缩命令。tar -zcvf /tmp/etc.tar.gz /etc <==打包后，以 gzip 压缩。tar -jcvf /tmp/etc.tar.bz2 /etc <==打包后，以 bzip2 压缩。此处默

codedecode 2013-09-11
CurrentJ

CurrentJ

W3CSchool教程
HTML 教程
CSS 教程
Bootstrap 教程
Javascript 教程
jQuery 教程
后端教程
C 教程
Java 教程
PHP 教程
Python 教程
Go 教程
移动开发
Android 教程
Swift 教程
Kotlin 教程
jQuery Mobile 教程
ionic 教程
关于我们
新闻动态
联系方式
招聘英才
安科实验室
帮助与反馈

安科网(Ancii)，中国第一极客网

Copyright © 2013 - 2019 Ancii.com

京ICP备18063983号 京公网安备11010802014868号