debian datetime adjustment技术
debian 时间同步
Linux de 5.10.0-23-amd64 #1 SMP Debian 5.10.179-1 (2023-05-12) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Sep 1 20:48:42 2024 from 192.168.11.1
root@de:~# timedatectl status
Local time: Sun 2024-09-01 12:04:25 EDT
Universal time: Sun 2024-09-01 16:04:25 UTC
RTC time: Sun 2024-09-01 20:58:18
Time zone: US/Eastern (EDT, -0400)
System clock synchronized: no
NTP service: n/a
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time zone.
This mode cannot be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.
root@de:~# chronyd
-bash: chronyd: command not found
root@de:~# apt install chrony
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
dnsutils networkd-dispatcher
The following NEW packages will be installed:
chrony
0 upgraded, 1 newly installed, 0 to remove and 101 not upgraded.
Need to get 287 kB of archives.
After this operation, 644 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 chrony amd64 4.0-8+deb11u2 [287 kB]
Fetched 287 kB in 12s (24.5 kB/s)
Selecting previously unselected package chrony.
(Reading database ... 33668 files and directories currently installed.)
Preparing to unpack .../chrony_4.0-8+deb11u2_amd64.deb ...
Unpacking chrony (4.0-8+deb11u2) ...
Setting up chrony (4.0-8+deb11u2) ...
Creating config file /etc/chrony/chrony.conf with new version
Creating config file /etc/chrony/chrony.keys with new version
dpkg-statoverride: warning: --update given but /var/log/chrony does not exist
Created symlink /etc/systemd/system/chronyd.service → /lib/systemd/system/chrony.service.
Created symlink /etc/systemd/system/multi-user.target.wants/chrony.service → /lib/systemd/system/chrony.service.
root@de:~# timedatectl status
Local time: Sun 2024-09-01 21:07:59 EDT
Universal time: Mon 2024-09-02 01:07:59 UTC
RTC time: Sun 2024-09-01 21:01:56
Time zone: US/Eastern (EDT, -0400)
System clock synchronized: no
NTP service: active
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time zone.
This mode cannot be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.
root@de:~# chronyd
Another chronyd may already be running (pid=4080632), check /run/chrony/chronyd.pid
root@de:~# chronyd -Q
2024-09-02T01:09:10Z chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
2024-09-02T01:09:10Z Disabled control of system clock
2024-09-02T01:09:10Z Using right/UTC timezone to obtain leap second data
2024-09-02T01:09:15Z System clock wrong by 0.008633 seconds (ignored)
2024-09-02T01:09:15Z chronyd exiting
root@de:~# date
Mon 02 Sep 2024 09:09:18 AM CST
root@de:~# chronyd -q
2024-09-02T01:10:08Z chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
2024-09-02T01:10:08Z Fatal error : Another chronyd may already be running (pid=4080632), check /run/chrony/chronyd.pid
root@de:~# timedatectl status
Local time: Sun 2024-09-01 21:10:41 EDT
Universal time: Mon 2024-09-02 01:10:41 UTC
RTC time: Sun 2024-09-01 21:10:41
Time zone: US/Eastern (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time zone.
This mode cannot be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.
root@de:~# chronyd -q
2024-09-02T01:13:18Z chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
2024-09-02T01:13:18Z Fatal error : Another chronyd may already be running (pid=4080632), check /run/chrony/chronyd.pid
root@de:~# chronyd -Q
2024-09-02T01:13:22Z chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
2024-09-02T01:13:22Z Disabled control of system clock
2024-09-02T01:13:22Z Frequency 0.000 +/- 1000000.000 ppm read from /var/lib/chrony/chrony.drift
2024-09-02T01:13:22Z Using right/UTC timezone to obtain leap second data
2024-09-02T01:13:27Z System clock wrong by -0.002952 seconds (ignored)
2024-09-02T01:13:27Z chronyd exiting
root@de:~# ps aux | grep chrony
_chrony 4080632 0.0 0.0 19032 3684 ? S 09:07 0:00 /usr/sbin/chronyd -F 1
_chrony 4080633 0.0 0.0 10840 2740 ? S 09:07 0:00 /usr/sbin/chronyd -F 1
root 4082093 0.0 0.0 6240 708 pts/0 S+ 09:13 0:00 grep chrony
root@de:~# chronyd --help
Usage: chronyd [OPTION]... [DIRECTIVE]...
Options:
-4 Use IPv4 addresses only
-6 Use IPv6 addresses only
-f FILE Specify configuration file (/etc/chrony/chrony.conf)
-n Don't run as daemon
-d Don't run as daemon and log to stderr
-l FILE Log to file
-L LEVEL Set logging threshold (0)
-p Print configuration and exit
-q Set clock and exit
-Q Log offset and exit
-r Reload dump files
-R Adapt configuration for restart
-s Set clock from RTC
-t SECONDS Exit after elapsed time
-u USER Specify user (_chrony)
-U Don't check for root
-F LEVEL Set system call filter level (0)
-P PRIORITY Set process priority (0)
-m Lock memory
-x Don't control clock
-v, --version Print version and exit
-h, --help Print usage and exit
root@de:~#
root@de:~# systemctl status datetime
Unit datetime.service could not be found.
root@de:~# systemctl status chronyy
Unit chronyy.service could not be found.
root@de:~# systemctl status chrony
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2024-09-02 00:07:56 CST; 9h ago
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Process: 4080630 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
Main PID: 4080632 (chronyd)
Tasks: 2 (limit: 18883)
Memory: 1.4M
CPU: 33ms
CGroup: /system.slice/chrony.service
├─4080632 /usr/sbin/chronyd -F 1
└─4080633 /usr/sbin/chronyd -F 1
Sep 02 00:07:56 de systemd[1]: Starting chrony, an NTP client/server...
Sep 02 00:07:56 de chronyd[4080632]: chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
Sep 02 00:07:56 de chronyd[4080632]: Using right/UTC timezone to obtain leap second data
Sep 02 00:07:56 de chronyd[4080632]: Loaded seccomp filter
Sep 02 00:07:56 de systemd[1]: Started chrony, an NTP client/server.
Sep 02 00:08:02 de chronyd[4080632]: Selected source 110.42.98.138 (2.debian.pool.ntp.org)
Sep 02 00:08:02 de chronyd[4080632]: System clock wrong by 32397.260653 seconds
Sep 02 09:07:59 de chronyd[4080632]: System clock was stepped by 32397.260653 seconds
Sep 02 09:07:59 de chronyd[4080632]: System clock TAI offset set to 37 seconds
Sep 02 09:08:01 de chronyd[4080632]: Selected source 202.112.29.82 (2.debian.pool.ntp.org)
root@de:~# timedatectl status
Local time: Sun 2024-09-01 21:18:01 EDT
Universal time: Mon 2024-09-02 01:18:01 UTC
RTC time: Sun 2024-09-01 21:18:01
Time zone: US/Eastern (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: yes
Warning: The system is configured to read the RTC time in the local time zone.
This mode cannot be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
'timedatectl set-local-rtc 0'.
root@de:~# timedatectl set-local-rtc 0
root@de:~# timedatectl
Local time: Sun 2024-09-01 21:41:41 EDT
Universal time: Mon 2024-09-02 01:41:41 UTC
RTC time: Mon 2024-09-02 01:41:41
Time zone: US/Eastern (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
root@de:~# date
Mon 02 Sep 2024 09:41:48 AM CST
root@de:~# hwclock
2024-09-02 05:43:22.743599+08:00
root@de:~# date
Mon 02 Sep 2024 09:43:26 AM CST
root@de:~# hwclock --show
2024-09-02 05:44:09.791545+08:00
root@de:~# hwclock --systohc
root@de:~# hwclock --show
2024-09-02 09:45:16.177046+08:00
root@de:~# hwclock
2024-09-02 09:45:21.937260+08:00
root@de:~# date
Mon 02 Sep 2024 09:45:23 AM CST
小米路由 MIWIFI 自动重新拨号技术
其实小米路由器没有隐私可言，每次操作都上报数据，恐怖至极！
有能力的小伙伴，还是应该折腾换掉它，毕竟人生短暂啊，没有时间就算了。
小米路由如何远程重新拨号呢？其实是可以实现的。
远程拨号有个最大的危险，就是会中断，导致完全失联。这样必须找一个本地终端，设置好自动脚本，这样才能做到！
上代码：
miwifi 的网页版含有 JQuery 对象，可以直接使用，VUE 太臃肿，太费终端资源，终究不是最好的选择。
$('#pppoeStop').trigger('click');
setTimeout(function(){
$('#pppoeStart').trigger('click');
},11e3);
以上代码，必须远程桌面使用本地终端在 console 执行可以做到。看视频号直播带货技术
视频号直播带货就是一个骗子平台，招募一堆骗子个人IP，打造骗子家庭人设，进行无货源行骗。
当互联网的最后一点点信用耗尽了之后，互联网的意义何在？
奇葩的是那些买了主播带货的商品的用户评论，我只看差评，看到一个产品的 800 多个差评，结果很多用户的评论都是因为某某的直播，和信任某某才买的这个商品，可见带同一款货的主播有很多。为什么用户会这么傻呢？明明卖货的主播和商品的视频号不是同一个，明明是无货源假IP主播模式，为什么就相信呢，看来绝大多数用户对于软件的认知是一点都不懂的。
cf proxy 301 too many times技术
这次配置，只配置了一个二级，结果测试不行，我还以为必须根 proxy 才可以，后来全部 proxy，出现了一直重定向的问题。
本来是轻车熟路，结果熟悉后反而容易出错，记录之。
除了缓存，代理，等等的问题，后来才发现，我忘记设置了 SSL/TLS 了，默认 Flexible，改为 Full (strict)。基本上就都好了，剩下一个是代理缓存的问题，重启了浏览器就都好了。
SSL/TLS Overview Choose how Cloudflare encrypts traffic between your visitors and Cloudflare, and between Cloudflare and your origin server, to prevent data theft and other tampering. SSL/TLS documentation Advanced Certificate Manager Unlock more control and flexibility for your Certificates and SSL/TLS settings Activate Your SSL/TLS encryption mode is Full (strict) This setting was last changed 17 minutes ago Browser Origin Server Cloudflare Off (not secure) No encryption applied. Turning off SSL disables HTTPS and causes browsers to show a warning that your website is not secure. Flexible Enable encryption only between your visitors and Cloudflare. This avoids browser security warnings, but all connections between Cloudflare and your origin are made through HTTP. Full Enable encryption end-to-end. Use this mode when your origin server supports SSL certification but does not use a valid, publicly trusted certificate. Full (strict) (Recommended mode) Enable encryption end-to-end and enforce validation on origin certificates. Use Cloudflare’s Origin CA to generate certificates for your origin.
黑名单软件 TamperMonkey 别再用了技术
TamperMonkey 油猴子作为一个软件，向用户收费，是没有问题的，但是，要求用户打赏，用户不打赏就罢工，这就太流氓了！
说实话，开发一个 Chrome 插件门槛并不高，它特别像现在的小程序。我在很多年以前（10年前）就开发过，参考这篇文章 Chrome插件在高版本浏览器中安装报错解决。
无意中弹出来打赏，点击了不打赏，就直接罢工了，导致找了一段时间，才发现是这个流氓在作祟。
软件还是需要一个好听的名字的，油猴子，🐒，一听就不是好东西！