V2EX = way to explore
V2EX 是一个关于分享和探索的地方
现在注册
已注册用户请  登录
V2EX  ›  lumen  ›  全部回复第 1 页 / 共 2 页
回复总数  40
1  2  
2022-01-13 19:15:11 +08:00
回复了 N032138 创建的主题 MacBook Pro 鼠须管的输入法不能横排显示
当前的版本有两个配置来控制排版:

1.「候选词列表」的样式,横排和竖排
candidate_list_layout: stacked | linear

2.「候选词」的样式,横排和竖排
text_orientation: horizontal | vertical
2021-11-10 17:49:27 +08:00
回复了 movq 创建的主题 Apple 双十一想给黑苹果换块更大的 SSD,该怎么克隆系统到新硬盘上面
Time Machine
2019-11-29 20:02:13 +08:00
回复了 CitizenR 创建的主题 Linux CentOS 8/Podman 的坑
和你遇到的问题一样
2018-03-19 22:58:29 +08:00
回复了 hagezhou 创建的主题 GitLab Gerrit 新建项目无法同步进 gitlab
@hagezhou 找到解决办法了:
1. 在客户端编辑 ~/.known_hosts,将里面涉及 服务端 的条目删除
2. 执行 ssh-keyscan -p <server port> <server-host> 2>/dev/null | grep ssh-rsa >> ~/.known_hosts
2018-03-19 22:18:21 +08:00
回复了 hagezhou 创建的主题 GitLab Gerrit 新建项目无法同步进 gitlab
客户端的:
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 58: Applying options for *
debug2: resolving "gerrit.example.com" port 29418
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to gerrit.example.com [12.34.56.78] port 29418.
debug1: Connection established.
debug1: identity file /data/username/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /data/username/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /data/username/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /data/username/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /data/username/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /data/username/.ssh/id_ecdsa-cert type -1
debug1: identity file /data/username/.ssh/id_ed25519 type 4
debug1: key_load_public: No such file or directory
debug1: identity file /data/username/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4
debug1: Remote protocol version 2.0, remote software version GerritCodeReview_2.14.6 (SSHD-CORE-1.4.0)
debug1: no match: GerritCodeReview_2.14.6 (SSHD-CORE-1.4.0)
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to gerrit.example.com:29418 as 'lumen'
debug3: put_host_port: [gerrit.example.com]:29418
debug3: hostkeys_foreach: reading file "/data/username/.ssh/known_hosts"
debug3: record_hostkey: found key type ED25519 in file /data/username/.ssh/known_hosts:2
debug3: record_hostkey: found key type RSA in file /data/username/.ssh/known_hosts:4
debug3: load_hostkeys: loaded 2 keys from [gerrit.example.com]:29418
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,ext-info-c
debug2: host key algorithms: [email protected],[email protected],ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa,[email protected],[email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-dss
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,[email protected],zlib
debug2: compression stoc: none,[email protected],zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: host key algorithms: ssh-rsa,ssh-dss,ssh-ed25519
debug2: ciphers ctos: aes128-ctr,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc
debug2: ciphers stoc: aes128-ctr,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc
debug2: MACs ctos: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha2-512,hmac-sha1-96,hmac-md5-96
debug2: MACs stoc: hmac-md5,hmac-sha1,hmac-sha2-256,hmac-sha2-512,hmac-sha1-96,hmac-md5-96
debug2: compression ctos: none
debug2: compression stoc: none
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: ecdh-sha2-nistp256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: ecdh-sha2-nistp256 need=32 dh_need=32
debug1: kex: ecdh-sha2-nistp256 need=32 dh_need=32
debug3: send packet: type 30
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ssh-ed25519 SHA256:b6iuw5+xnO0ZiC+zYtXc1NGhLcQz5NbPRoMJxskH3tI
debug3: put_host_port: [12.34.56.78]:29418
debug3: put_host_port: [gerrit.example.com]:29418
debug3: hostkeys_foreach: reading file "/data/username/.ssh/known_hosts"
debug3: record_hostkey: found key type ED25519 in file /data/username/.ssh/known_hosts:2
debug3: record_hostkey: found key type RSA in file /data/username/.ssh/known_hosts:4
debug3: load_hostkeys: loaded 2 keys from [gerrit.example.com]:29418
debug3: hostkeys_foreach: reading file "/data/username/.ssh/known_hosts"
debug3: record_hostkey: found key type ED25519 in file /data/username/.ssh/known_hosts:2
debug3: record_hostkey: found key type RSA in file /data/username/.ssh/known_hosts:4
debug3: load_hostkeys: loaded 2 keys from [12.34.56.78]:29418
debug1: Host '[gerrit.example.com]:29418' is known and matches the ED25519 host key.
debug1: Found key in /data/username/.ssh/known_hosts:2
debug2: ssh_ed25519_verify: crypto_sign_ed25519_open failed: -1
ssh_dispatch_run_fatal: Connection to 12.34.56.78 port 29418: incorrect signature
2018-03-19 22:16:28 +08:00
回复了 hagezhou 创建的主题 GitLab Gerrit 新建项目无法同步进 gitlab
同遇到。
gerrit 的 error_log:
[2018-03-19 22:11:12,195] [sshd-SshServer[1b949de4]-nio2-thread-4] WARN org.apache.sshd.common.keyprovider.FileKeyPairProvider : Failed (StreamCorruptedException) to load key resource=/data/gerrit/review_site/etc/ssh_host_ecdsa_384_key: Invalid DER: object is not an OID: SEQUENCE
[2018-03-19 22:11:12,195] [sshd-SshServer[1b949de4]-nio2-thread-4] WARN org.apache.sshd.common.keyprovider.FileKeyPairProvider : Failed (StreamCorruptedException) to load key resource=/data/gerrit/review_site/etc/ssh_host_ecdsa_521_key: Invalid DER: object is not an OID: SEQUENCE

客户端的:
2018-02-03 14:17:14 +08:00
回复了 ttgo 创建的主题 职场话题 隔壁组的小兵集体情愿 要炒了 team leader
开启看戏模式
2018-01-04 10:15:51 +08:00
回复了 daishankeke 创建的主题 程序员 各位 V 友,想换个笔记本了~有木有推荐的
必须 MacBook Pro,外观不说了,Retina 也不说了,就是系统的 Terminal 装上 Homebrew 就能随手打造自己的工具链了。
2017-02-06 17:15:47 +08:00
回复了 BeliefanX 创建的主题 macOS 设置 aria2 开机启动时出现的 iTerm2 这个提示怎么关掉
用 iTerm2 打开会话之后又立即关闭就会出现这种提示
OS X 下正确的自动启动姿势可以参考: launchd — 你应该了解的 OS X 工具
https://www.ulumen.com/launchd-tool-of-os-x-you-should-know-about/
2016-08-18 14:25:15 +08:00
回复了 mystryl 创建的主题 问与答 Alfred 中用/bin/bash/运行脚本 command not found
大概是 PATH 变量里的路径没有包含命令所在路径
2016-05-31 21:19:07 +08:00
回复了 lslqtz 创建的主题 程序员 开站点时,各位喜欢用 www 前缀还是不用前缀?
@varrily 强行硬广
2016-05-31 17:49:30 +08:00
回复了 zyqf 创建的主题 Python 如何优雅简单的备份远程数据库到本机?
通过 ssh 远程执行 mysqldump 命令,在远程用 bzip2 压缩
重定向到本地的 .bz2 文件:
ssh USER@HOST "mysqldump --all-databases --single-transaction | bzip2 " > /path/to/local/file.HOST.sql.bz2

这样一个命令就搞定了远程、加密、压缩、存储
写成脚本,通过配置文件来添加机器及数据库就好
^foo^bar
将上一命令的第一个 foo 改为 bar

安利个小工具: nc 或者 netcat
2016-05-29 20:41:15 +08:00
回复了 Livid 创建的主题 Linux Gravitational Teleport 集中化的 SSH 登录方案
好像很不错,调研一下先~
@xqin 这个方法可靠, SSH 可以做端口隧道
2016-05-24 21:33:09 +08:00
回复了 jerry017cn 创建的主题 Linux SHELL 编程之执行过程
温故而知新
2016-05-24 19:33:08 +08:00
回复了 jerry017cn 创建的主题 Linux SHELL 编程之语法基础
很赞!用了很久,但是很多细节不一定能说的清楚。
MOUNT_NTFS(8) BSD System Manager's Manual MOUNT_NTFS(8)

NAME
mount_ntfs -- mount an NTFS file system

SYNOPSIS
mount_ntfs [-s] [-o options] special node

DESCRIPTION
The mount_ntfs command attaches the NTFS file system residing on the device special to the global
file system namespace at the location indicated by node. This command is normally executed by
mount(8) at boot time, but can be used by any user to mount an NTFS file system on any directory that
they own (provided, of course, that they have appropriate access to the device that contains the file
system).
2016-05-24 16:24:37 +08:00
回复了 lavdemo 创建的主题 问与答 618 电商搞促销,作为运维应该做什么?
看了之前的答案,基本上都做好了背锅的准备。
背锅的原因很简单,因为少做了一步工作,导致无限责任。
这里有个有限责任方案可供参考:

一、资源评估(重中之重,实力摔锅的重要依据)
   1.运维侧评估好当前资源,包括但不限于: IP 、带宽、存储、 DB 、服务器、网络设备
   2.运营及业务侧评估活动的人数、流量、包量峰值以及峰值出现的时间点(有可能是多个时间点)
   3.如果资源不足就要向公司要资源,如果公司也不能提供足够的资源,就反馈出来只能有损服务及具体的影响(意思是出了性能问题了这锅我们运维不背!)

二、部署扩容并测试
   1.不管资源够不够,该部署就部署,该扩容就扩容
   2.联合业务侧一起测试,功能测试、压力测试,输出结果(用于实力摔锅!)
   3.注意避免和别的业务混合部署,以免压力过大影响了别的功能

三、加强监控巡检
   1.Review 当前的监控,看是否有疏漏
   2.根据活动设置相应的监控,覆盖活动的所有关键路径

四、准备故障处理预案
   1.针对可能出现的故障场景做好处理方案

五、活动当天
   1.定时(比如每隔 30 分钟)查看监控视图
   2.团队成员轮流查看警报信息

以上,只要不是人为原因,运维都不用背锅。
至于其它什么随机 refues ,维护页面,道歉文案,那是业务和运营的事情了。
1  2  
关于   ·   帮助文档   ·   博客   ·   API   ·   FAQ   ·   我们的愿景   ·   实用小工具   ·   3593 人在线   最高记录 6543   ·     Select Language
创意工作者们的社区
World is powered by solitude
VERSION: 3.9.8.5 · 35ms · UTC 10:29 · PVG 18:29 · LAX 03:29 · JFK 06:29
Developed with CodeLauncher
♥ Do have faith in what you're doing.