podman设置开机启动
2024-05-02 02:38:23
查看httpd状态
[root@nextcloud ~]# systemctl status httpd
● httpd.service - The Apache HTTP ServerLoaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)Drop-In: /usr/lib/systemd/system/httpd.service.d└─php-fpm.confActive: failed (Result: timeout) since Tue 2022-07-26 09:02:08 CST; 3min 34s agoDocs: man:httpd.service(8)Process: 1424 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)Main PID: 1424 (code=exited, status=1/FAILURE)Status: "Reading configuration..."7月 26 09:00:25 nextcloud systemd[1]: Starting The Apache HTTP Server...
7月 26 09:01:55 nextcloud systemd[1]: httpd.service: start operation timed out. Terminating.
7月 26 09:02:08 nextcloud systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
7月 26 09:02:08 nextcloud systemd[1]: httpd.service: Failed with result 'timeout'.
7月 26 09:02:08 nextcloud systemd[1]: Failed to start The Apache HTTP Server.
启动httpd服务
[root@nextcloud ~]# setenforce 0
setenforce: SELinux is disabled
[root@nextcloud ~]# systemctl start httpd
Enter TLS private key passphrase for localhost:443 (RSA) : ******
[root@nextcloud ~]# cat /etc/selinux/config# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these three values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected.
# mls - Multi Level Security protection.
SELINUXTYPE=targeted//查看运行的容器
[root@nextcloud ~]# systemctl status podman
● podman.service - Podman API ServiceLoaded: loaded (/usr/lib/systemd/system/podman.service; disabled; vendor preset: disabled)Active: inactive (dead)Docs: man:podman-system-service(1)
[root@nextcloud ~]# systemctl start podman
[root@nextcloud ~]# podman ps //查看运行的容器
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
[root@nextcloud ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
010c0852efc0 docker.io/onlyoffice/documentserver:latest 15 hours ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp reverent_hugle
[root@nextcloud ~]# docker run -i -t -d -p 8080:80 -p 8443:443 --restart=always onlyoffice/documentserver
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
f0ec23f47a33719a899f39fe417ebe016ff15498220daa3bed045245710bf8c1
[root@nextcloud ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
010c0852efc0 docker.io/onlyoffice/documentserver:latest 15 hours ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp reverent_hugle
f0ec23f47a33 docker.io/onlyoffice/documentserver:latest 20 seconds ago Up 7 seconds ago 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp stoic_keldysh
[root@nextcloud ~]# podman run -i -t -d -p 8080:80 -p 8443:443 --restart=always onlyoffice/documentserver
Error: cannot listen on the TCP port: listen tcp4 :8080: bind: address already in use
[root@nextcloud ~]# dock exec -it 010c0852efc0 /bin/bash
bash: dock: 未找到命令...
[root@nextcloud ~]# podman exec -it 010c0852efc0 /bin/bash
Error: can only create exec sessions on running containers: container state improper
[root@nextcloud ~]# docker exec -it 010c0852efc0 /bin/bash
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: can only create exec sessions on running containers: container state improper
[root@nextcloud ~]# podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/library/ubuntu latest 27941809078c 7 weeks ago 80.3 MB
docker.io/onlyoffice/documentserver latest 5a50e3a2d2ed 8 weeks ago 2.99 GB
[root@nextcloud ~]# podman start 010c0852efc0
Error: unable to start container "010c0852efc09f87bfd95ec914db539c0b61b86531f614fe5e28dd7994289b49": failed to mount shm tmpfs "/var/lib/containers/storage/overlay-containers/010c0852efc09f87bfd95ec914db539c0b61b86531f614fe5e28dd7994289b49/userdata/shm": invalid argument
[root@nextcloud ~]# docker rm f0ec23f47a33
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: cannot remove container f0ec23f47a33719a899f39fe417ebe016ff15498220daa3bed045245710bf8c1 as it is running - running or paused containers cannot be removed without force: container state improper
[root@nextcloud ~]# docker stop f0ec23f47a33
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
f0ec23f47a33
[root@nextcloud ~]# docker rm f0ec23f47a33
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
f0ec23f47a33719a899f39fe417ebe016ff15498220daa3bed045245710bf8c1
[root@nextcloud ~]# podman start 010c0852efc0
Error: unable to start container "010c0852efc09f87bfd95ec914db539c0b61b86531f614fe5e28dd7994289b49": failed to mount shm tmpfs "/var/lib/containers/storage/overlay-containers/010c0852efc09f87bfd95ec914db539c0b61b86531f614fe5e28dd7994289b49/userdata/shm": invalid argument
[root@nextcloud ~]# docker ps -a
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
010c0852efc0 docker.io/onlyoffice/documentserver:latest 16 hours ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp reverent_hugle
5b9821eaef16 docker.io/onlyoffice/documentserver:latest 14 minutes ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp friendly_pike
[root@nextcloud ~]# podman rm 5b9821eaef16
5b9821eaef16481c99db67e8eac268284b8f9839592893aa2db076fc96d7c9ad
[root@nextcloud ~]# docker ps -a
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
010c0852efc0 docker.io/onlyoffice/documentserver:latest 16 hours ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp reverent_hugle
[root@nextcloud ~]# podman restart 010c0852efc0
Error: failed to mount shm tmpfs "/var/lib/containers/storage/overlay-containers/010c0852efc09f87bfd95ec914db539c0b61b86531f614fe5e28dd7994289b49/userdata/shm": invalid argument
[root@nextcloud ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
010c0852efc0 docker.io/onlyoffice/documentserver:latest 16 hours ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp reverent_hugle
[root@nextcloud ~]# docker images
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/library/ubuntu latest 27941809078c 7 weeks ago 80.3 MB
docker.io/onlyoffice/documentserver latest 5a50e3a2d2ed 8 weeks ago 2.99 GB
[root@nextcloud ~]# podman stats -l
Error: container state improper
[root@nextcloud ~]# podman run -i -t -d -p 8080:80 -p 8443:443 docker.io/onlyoffice/documentserver:latest
5928bc2b3a234ebbde9c7d239ef981381328e54e4b061a80b9b583ec0729e699
[root@nextcloud ~]# ^C
[root@nextcloud ~]# ^C
[root@nextcloud ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
010c0852efc0 docker.io/onlyoffice/documentserver:latest 16 hours ago Created 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp reverent_hugle
5928bc2b3a23 docker.io/onlyoffice/documentserver:latest 4 minutes ago Up 4 minutes ago 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp sleepy_edison
[root@nextcloud ~]# podman rm
Error: you must provide at least one name or id
[root@nextcloud ~]# podman rm 010c0852efc0
010c0852efc09f87bfd95ec914db539c0b61b86531f614fe5e28dd7994289b49
[root@nextcloud ~]# reboot
login as: root
root@192.168.182.129's password:
Activate the web console with: systemctl enable --now cockpit.socketLast login: Tue Jul 26 12:36:07 2022
[root@nextcloud ~]# systemctl status httpd
● httpd.service - The Apache HTTP ServerLoaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)Drop-In: /usr/lib/systemd/system/httpd.service.d└─php-fpm.confActive: failed (Result: timeout) since Tue 2022-07-26 12:35:02 CST; 3min 41s agoDocs: man:httpd.service(8)Process: 1427 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)Main PID: 1427 (code=exited, status=1/FAILURE)Status: "Reading configuration..."7月 26 12:33:21 nextcloud systemd[1]: Starting The Apache HTTP Server...
7月 26 12:34:51 nextcloud systemd[1]: httpd.service: start operation timed out. Terminating.
7月 26 12:35:02 nextcloud systemd[1]: httpd.service: Main process exited, code=exited, status=1/FAILURE
7月 26 12:35:02 nextcloud systemd[1]: httpd.service: Failed with result 'timeout'.
7月 26 12:35:02 nextcloud systemd[1]: Failed to start The Apache HTTP Server.查看SELinux
[root@nextcloud ~]# setenforce
usage: setenforce [ Enforcing | Permissive | 1 | 0 ]
[root@nextcloud ~]# getenforce
Disabled
[root@nextcloud ~]# setenforce 0
setenforce: SELinux is disabled
[root@nextcloud ~]# systemctl restart httpd
Enter TLS private key passphrase for localhost:443 (RSA) : ******
[root@nextcloud ~]# systemctl status podman
● podman.service - Podman API ServiceLoaded: loaded (/usr/lib/systemd/system/podman.service; disabled; vendor preset: disabled)Active: inactive (dead)Docs: man:podman-system-service(1)
[root@nextcloud ~]# systemctl status podman ps -a^Cdman
[root@nextcloud ~]# ^C
查看运行的容器
[root@nextcloud ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5928bc2b3a23 docker.io/onlyoffice/documentserver:latest 3 hours ago Exited (143) 3 hours ago 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp sleepy_edison
[root@nextcloud ~]# podman generate systemd --new --files --name sleepy_edison
/root/container-sleepy_edison.service
[root@nextcloud ~]# cd /root
[root@nextcloud ~]# ls
公共 模板 视频 图片 文档 下载 音乐 桌面 anaconda-ks.cfg container-sleepy_edison.service initial-setup-ks.cfg
[root@nextcloud ~]# systemctl daemon-reload //启动服务
[root@nextcloud ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5928bc2b3a23 docker.io/onlyoffice/documentserver:latest 3 hours ago Exited (143) 3 hours ago 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp sleepy_edison
[root@nextcloud ~]# systemctl status console-getty.service //查看状态
● console-getty.service - Console GettyLoaded: loaded (/usr/lib/systemd/system/console-getty.service; disabled; vendor preset: disabled)Active: inactive (dead)Docs: man:agetty(8)man:systemd-getty-generator(8)
设置为开机自启
[root@nextcloud ~]# podman ps -a //查看运行的容器
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5928bc2b3a23 docker.io/onlyoffice/documentserver:latest 3 hours ago Exited (143) 3 hours ago 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp sleepy_edison
[root@nextcloud ~]# podman generate systemd --new --files --name sleepy_edison
/root/container-sleepy_edison.service
[root@nextcloud ~]# cd /root/
[root@nextcloud ~]# ls //查看文件
公共 模板 视频 图片 文档 下载 音乐 桌面 anaconda-ks.cfg container-sleepy_edison.service initial-setup-ks.cfg
[root@nextcloud ~]# cp container-sleepy_edison.service /usr/lib/systemd/system/ //复制文件
[root@nextcloud ~]# vi /etc/selinux/config
[root@nextcloud ~]# vi /etc/selinux/config //关闭SELINUX
[root@nextcloud ~]# cat /etc/selinux/config //关闭SELINUX# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disable
# SELINUXTYPE= can take one of these three values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected.
# mls - Multi Level Security protection.
SELINUXTYPE=targeted[root@nextcloud ~]# systemctl status container-sleepy_edison.service
● container-sleepy_edison.service - Podman container-sleepy_edison.serviceLoaded: loaded (/usr/lib/systemd/system/container-sleepy_edison.service; disabled; vendor preset: disabled)Active: inactive (dead)Docs: man:podman-generate-systemd(1)
[root@nextcloud ~]# systemctl enable --now container-sleepy_edison.service //设置为开机自启
Created symlink /etc/systemd/system/multi-user.target.wants/container-sleepy_edison.service → /usr/lib/systemd/system/container-sleepy_edison.service.
Created symlink /etc/systemd/system/default.target.wants/container-sleepy_edison.service → /usr/lib/systemd/system/container-sleepy_edison.service.
[root@nextcloud ~]# systemctl status container-sleepy_edison.service //查看服务信息
● container-sleepy_edison.service - Podman container-sleepy_edison.serviceLoaded: loaded (/usr/lib/systemd/system/container-sleepy_edison.service; enabled; vendor preset: disabled)Active: active (running) since Tue 2022-07-26 13:16:37 CST; 13s agoDocs: man:podman-generate-systemd(1)Process: 2826 ExecStartPre=/bin/rm -f /run/container-sleepy_edison.service.ctr-id (code=exited, status=0/SUCCESS)Main PID: 3054 (conmon)Tasks: 2 (limit: 23384)Memory: 124.8MCGroup: /system.slice/container-sleepy_edison.service└─3054 /usr/bin/conmon --api-version 1 -c 62c8248bb8d4fe54bc2b286121aaeda80e50777877438f6aac5e104a837106ad -u 62c8248bb8d4fe54bc2b286121aaeda80e50777877438f6>7月 26 13:16:26 nextcloud systemd[1]: Starting Podman container-sleepy_edison.service...
7月 26 13:16:26 nextcloud podman[2829]: time="2022-07-26T13:16:26+08:00" level=warning msg="The input device is not a TTY. The --tty and --interactive flags might not w>
7月 26 13:16:37 nextcloud systemd[1]: Started Podman container-sleepy_edison.service.
7月 26 13:16:37 nextcloud podman[2829]: 62c8248bb8d4fe54bc2b286121aaeda80e50777877438f6aac5e104a837106ad[root@nextcloud ~]# podman ps //查看启动的容器
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
62c8248bb8d4 docker.io/onlyoffice/documentserver:latest 41 seconds ago Up 31 seconds ago 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp hardcore_borg
[root@nextcloud ~]#[root@nextcloud ~]# systemctl enable --now console-getty.service //设置为开机自启
Created symlink /etc/systemd/system/getty.target.wants/console-getty.service → /usr/lib/systemd/system/console-getty.service.
[root@nextcloud ~]# systemctl status --now console-getty.service //查看服务信息
● console-getty.service - Console GettyLoaded: loaded (/usr/lib/systemd/system/console-getty.service; enabled; vendor preset: disabled)Active: active (running) since Tue 2022-07-26 12:49:08 CST; 15s agoDocs: man:agetty(8)man:systemd-getty-generator(8)Main PID: 3780 (agetty)Tasks: 1 (limit: 23384)Memory: 324.0KCGroup: /system.slice/console-getty.service└─3780 /sbin/agetty -o -p -- \u --noclear --keep-baud console 115200,38400,9600 linux7月 26 12:49:08 nextcloud systemd[1]: Started Console Getty.
[root@nextcloud ~]# podman ps //查看启动的容器
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
[root@nextcloud ~]# podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5928bc2b3a23 docker.io/onlyoffice/documentserver:latest 3 hours ago Exited (143) 3 hours ago 0.0.0.0:8080->80/tcp, 0.0.0.0:8443->443/tcp sleepy_edison[root@nextcloud ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope hostvalid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000link/ether 00:0c:29:a2:11:c4 brd ff:ff:ff:ff:ff:ffinet 192.168.182.129/24 brd 192.168.182.255 scope global dynamic noprefixroute ens33valid_lft 1699sec preferred_lft 1699secinet6 fe80::20c:29ff:fea2:11c4/64 scope link noprefixroutevalid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000link/ether 52:54:00:18:b0:7a brd ff:ff:ff:ff:ff:ffinet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000link/ether 52:54:00:18:b0:7a brd ff:ff:ff:ff:ff:ff
[root@nextcloud ~]#[root@nextcloud ~]# ip a //再次查看。容器重新启动
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope hostvalid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000link/ether 00:0c:29:a2:11:c4 brd ff:ff:ff:ff:ff:ffinet 192.168.182.129/24 brd 192.168.182.255 scope global dynamic noprefixroute ens33valid_lft 948sec preferred_lft 948secinet6 fe80::20c:29ff:fea2:11c4/64 scope link noprefixroutevalid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000link/ether 52:54:00:18:b0:7a brd ff:ff:ff:ff:ff:ffinet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000link/ether 52:54:00:18:b0:7a brd ff:ff:ff:ff:ff:ff
5: cni-podman0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000link/ether 52:8a:92:16:a6:e1 brd ff:ff:ff:ff:ff:ffinet 10.88.0.1/16 brd 10.88.255.255 scope global cni-podman0valid_lft forever preferred_lft foreverinet6 fe80::508a:92ff:fe16:a6e1/64 scope linkvalid_lft forever preferred_lft forever
6: veth4ad74f4e@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master cni-podman0 state UP group defaultlink/ether ee:ba:c1:d5:d6:73 brd ff:ff:ff:ff:ff:ff link-netns cni-afea15a4-c2d0-bab6-4609-7c3659566890inet6 fe80::ecba:c1ff:fed5:d673/64 scope linkvalid_lft forever preferred_lft foreverpodman设置开机启动相关推荐
- ubuntu 设置开机执行脚本_ubuntu-18.04 设置开机启动脚本
ubuntu-18.04 设置开机启动脚本 参阅下列链接 ubuntu-18.04不能像ubuntu14一样通过编辑rc.local来设置开机启动脚本,通过下列简单设置后,可以使rc.local重新发 ...
- Linux设置开机启动
Linux设置开机启动有几种方式,今天就来讨论以下几种方式. 方法一:编辑rc.loacl脚本 直接在/etc/rc.local中添加启动脚本. $ vim /etc/rc.local 方法二:Lin ...
- linux init.d添加启动脚本 ln,linux编写可运行的shell脚本并在其他目录创建ln连接与设置开机启动...
ln :创建连接文件 - 默认创建的是硬连接,好比复制 ,但是两个文件会同步 命令:ln ./java/android/aa.txt aaa - s :创建的是软连接变为指向(类似于windows的 ...
- Centos设置开机启动Apache和Mysql[总结]
1.前言 最近学习搭建wordpress,需要用到apahce和mysql.我是下载源代码进行安装的,安装在/url/local目录下,每次开机都需要手动启动,有点麻烦.如是想设置开机启动,从网上查了 ...
- Windows 技术篇-win7利用系统自带工具关闭开机启用程序，不使用杀毒软件设置开机启动项
通过运行 msconfig 可以进入系统配置管理器,里面有开机启动程序列表,可以自由的进行设置. 如果想设置开机启动的话,就把要启动程序的快捷方式放入下面地址里即可,也可以通过开始菜单来进入. C:\ ...
- ubuntu 设置开机启动与关闭开机启动（适用于部分linux系统）
ubuntu 设置开机启动与关闭开机启动 首先,以apache开机启动的关闭为例, 参见:http://blog.csdn.net/lyhdream/article/details/8897618 然 ...
- linux设置脚本开机启动centos7,centos7设置开机启动
centos7有多种设置开机启动程序的方法,本文介绍通过自定义服务文件,添加到系统服务的方法.这里以redis为例: 1.vim redis.conf #改为yes后台运行,如果其它程序没有提供后台运 ...
- FastDFS设置开机启动
开机启动 fdfs_tracker 设置开机启动 cp FastDFS/init.d/fdfs_trackerd /etc/init.d/ chkconfig –add fdfs_trackerd c ...
- win10怎么设置开机启动项目_开机启动项怎么设置呢？禁用自启动程序
大家好,今天分享一篇来源小白一键重装网(xiaobaixitong.com)关于解答:开机启动项怎么设置呢? 每日壁纸 · 长按保存 开机启动项怎么设置呢?电脑开机速度变慢了很可能是开机启动项太多导致 ...
最新文章
- 面试官问你B树和B 树，就把这篇文章丢给他
- 我以为信用卡多就是好事，谁知道……
- 解码Java.Lang.OutOfMemoryError：PermGen空间
- 百度 合肥地区 软件研发工程师 笔试题
- SonarQube 8.4 发布，分析时间最多可减少 80%
- Java 实现发送Http请求
- 【MySQL】二，常用的SQL标准有哪些
- 3 二十五项反措--防止电气误操作及机组上电事故
- LeetCode-Python-1386. 安排电影院座位（数组）
- Python中关于with open file as 的用法
- 学生图书馆系统mysql数据库设计
- 命令行视频下载工具-dl
- uniapp swiper内嵌video组件的坑
- 复习整合Mysql指令操作
- java 压缩图片时候加水印
- YouTube儿童版的四种选择（其中不包含令人毛骨悚然的假视频）
- 中级职称计算机excel 公式,中级职称计算机试Excel应用模拟题库.doc
- STM32配置DAC输出固定电压和方波
- sed 注释行的 方法
- python crash coures python编程从入门到实践 笔记1 python常见函数