Will's questions

我的一台服务器上有一个大型数据文件夹，由于一些原因，我无法详细阐述，我想将其移动到专用 NAS（Openmediavault），然后再共享回现有服务器。

其中包括 www-data（nextcloud 数据文件夹）、will（我）、media（plex 数据文件夹）和 cctv（摄像机记录存储器）等文件。

有没有一种简单的方法可以在共享存储中维护这样的所有权结构，或者我最好将每个文件夹分解为单独的共享并单独安装它们？

理想情况下，我只想保留文件夹和文件的现有所有者。我已经克隆了驱动器映像进行测试，但尽管选择了听起来正确的“继承权限”设置

The permissions on new files and directories are normally governed by create mask and directory mask but the inherit permissions parameter overrides this. This can be particularly useful on systems with many users to allow a single share to be used flexibly by each user.

但是通过 fstab 条目将驱动器安装到服务器上（克隆用于测试）

//10.10.10.65/willzpool /willzpool cifs credentials=/root/smbcredentials 0 0

共享中的所有内容都归 root 所有。即使作为 root，我也无法更改共享中的所有内容。

我是否缺少了什么或者我的目标是否无法实现？

我一直致力于在运行 Ubuntu Server 16.04 的家庭服务器上设置 bind9 服务器，以允许我通过名称而不是 IP 地址访问我的服务。

绑定服务器本身（大部分）已设置好并且工作正常。我可以从我的网络设备的 ip 地址和主机名中解析主机名，但是服务器本身无法从它自己的 bind9 记录中解析任何内容，这让我有点难过。

唯一的名称服务器/etc/resolv.conf是我的路由器192.168.1.1和8.8.8.8.

这些是在我的/etc/network/interfaces. 我假设我的问题127.0.0.1不在那里，所以服务器本身会立即寻找我的路由器来解析地址，然后再到，8.8.8.8但是当我添加时127.0.0.1，/etc/network/interfaces没有其他任何东西被添加，/etc/resolv.conf所以我只剩下一个名字的服务器127.0.0.1

我确实在 中设置了转发器/etc/bind/named.conf.local，并且它们确实在我仍然可以访问互联网的情况下工作，但是从我读过的每个指南中，bind9 应该添加127.0.0.1到/etc/resolv.conf自身，这意味着它仍然由我的文件中的服务器填充，/etc/network/interfaces以便我的即使绑定服务器由于某种原因失败，服务器仍然“在线”。

我已经检查过/etc/default/bind9并且RESOLVCONF=yes在那里

# run resolvconf?
RESOLVCONF=yes

# startup options for the server
OPTIONS="-u bind"

这是我/etc/network/interfaces的，以防万一那里有问题

/etc/network/interfaces                                                                      

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo wlan0
iface lo inet loopback

# The primary network interface

#auto eth0
#       iface eth0 inet static

iface wlan0 inet static
        address 192.168.1.62
        netmask 255.255.255.0
        broadcast 192.168.1.255
        network 192.168.1.0
        wpa-ssid #############
        wpa-psk ****************
        dns-nameservers 192.168.1.1 8.8.8.8
        gateway 192.168.1.1
#       mtu 1500

这是我的/etc/bind/named.conf

acl mynetwork {
        192.168.1.0/24;
        };
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
key rndc-key {
        algorithm hmac-md5;
        secret "*****************";
        };
controls {
        inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { rndc-key; };
        };

和我的/etc/bind/named.conf.options

options {
        directory "/var/cache/bind";

        // If there is a firewall between you and nameservers you want
        // to talk to, you may need to fix the firewall to allow multiple
        // ports to talk.  See http://www.kb.cert.org/vuls/id/800113

        // If your ISP provided one or more IP addresses for stable
        // nameservers, you probably want to use them as forwarders.
        // Uncomment the following block, and insert the addresses replacing
        // the all-0's placeholder.

        forwarders {
                192.168.1.1;
                208.67.222.222;
                208.67.220.220;
                8.8.8.8;
                8.8.4.4;
                };

        //========================================================================
        // If BIND logs error messages about the root key being expired,
        // you will need to update your keys.  See https://www.isc.org/bind-keys
        //========================================================================
        dnssec-validation auto;

        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { any; };
        forward first;
};

如果您需要查看任何区域文件，请询问，但我认为它们不是问题，因为名称解析可以在其他设备上正常工作，而不是从服务器本身；除非我更改我的/etc/network/interfaces文件并将其127.0.0.1作为我唯一的 dns 服务器，否则我想这是我询问如何添加到我的 dns 列表而不是将其作为唯一条目/etc/resolv.conf 的冗长方式 127.0.0.1/etc/resolv.conf

几年前我设置服务器时，我做了一些研究并决定为我将用于存储的 3 个磁盘使用 zfs 文件系统。

总的来说，我对此非常满意。一开始，我只使用了旧笔记本电脑的 3 500gb 硬盘驱动器，当我决定升级它们时，更换过程非常简单，我在几个小时内就更换了所有 3 个磁盘。

但我想做一些改变。我希望能够快速查看系统的总容量以及已经使用了多少，但是当我设置它时，我创建了一些单独的挂载点。

本质上，我将整个池安装为 /willzpool，但在其中我有 5 个单独的文件夹 - /willzpool/will（我的存储）/willzpool/MrsWill（我妻子的存储）/willzpool/media（我们都可以访问的公共文件夹并且还用作我的 plex 库和下载的发行版/种子等的存储）

所有 3 也由 samba 共享，以实现 Windows 兼容性。

无论出于何种原因，我都为这 3 个文件夹提供了它们自己的挂载点：/willzpool/will、/willzpool/MrsWill、/willzpool/media。这意味着当我使用“zfs list”时，我并没有真正得到整个池使用量的确切数字，它被分成 4 个单独的文件系统。

我在 /willzpool/backups 的主 /willzpool 中也有 2 个文件夹（用于我的整个 / 系统的 rsync 备份减去一些文件夹，因此如果我破坏某些东西，我可以轻松恢复）和 /willzpool/nextcloud（用于我的 nextcloud 数据文件夹）当我运行“zfs list”时，这两个文件夹计入 /willzpool 的存储空间，并且我也有 samba 共享的备份文件夹，所以我可以验证它是否按我想要的方式工作（仅在上周设置）到目前为止正如我所见，will/MrsWill/media 的单独安装实际上毫无意义。

如果我使用 zfs destroy 销毁挂载，它会删除文件夹的内容还是只销毁挂载点，留下我的顶级 /willzpool zfs 条目，然后“zfs list”将为我提供总计？

我一直在尝试设置 conky 来监控我的家庭服务器的一些基本统计数据（处理器/内存使用情况、硬盘使用情况等）。

今天经历了很多混乱之后，我设法通过通过登录来使该过程正常工作

screen ssh -X 

然后运行

conky -c /path/to/config

然后，conky 进程在我的笔记本电脑上启动，即使我关闭了 ssh 会话，它也会持续存在。

但是我试图让这个从我笔记本电脑上的脚本开始，这样我就可以在启动时自动运行它。

我已经设置了一个通过没有密码的密钥登录的用户，以尝试使其全部正常工作（最终我的目标是尝试让它在我登录并开始过程时简单地询问密码）但我只是无法让它工作。

我正在使用的脚本是

#/bin/bash
screen ssh -X myconkyuser@myserverip "conky -c /path/to/config"

但它只是拒绝显示 conky。

甚至手动输入

screen ssh -X myconkyuser@myserverip "conky -c /path/to/config" 

从终端不会这样做。

如果我做

screen ssh -X -vv myconkyuser@myserverip "conky -c /path/to/config" 

我可以看到 ssh 连接正在发生并且 conky 正在启动，它只是没有正确地传递到我的笔记本电脑的 x 服务器。

我还尝试将其conky -c /path/to/config 作为自己的脚本放在服务器上并使用

screen ssh -X myconkyuser@myserverip "sh /path/to/conkystartupscript" 

但结果是一样的。

我将附加输出-vv以查看它是否可以阐明任何问题，我猜问题可能是会话在 conky 进程实际输出到显示器之前关闭，但我尝试pause 10在 conky 线下方添加无济于事。

任何人都可以帮忙吗？

will@will-Inspiron-7520 ~ 19:46:44 $ ssh -X -vv myconkyuser@myserverip "conky -c /path/to/myconky/config "
OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /my/ssh/folder/config
debug1: /my/ssh/folder/config line 1: Applying options for myserverip
debug1: /my/ssh/folder/config line 8: Applying options for myserverip
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "myserverip" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to myserverip [myserverip] port 22.
debug1: Connection established.
debug1: identity file /my/ssh/folder/id_ed25519 type 4
debug1: key_load_public: No such file or directory
debug1: identity file /my/ssh/folder/id_ed25519-cert type -1
debug1: identity file /my/ssh/folder/myconkyuserid_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /my/ssh/folder/myconkyuserid_rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.1 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to myserverip:22 as 'myconkyuser'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: [email protected],ssh-ed25519,[email protected],[email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-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: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
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]
debug2: compression stoc: none,[email protected]
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: [email protected]
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-ed25519 SHA256:yXsLEfcX1vuLtfzDI/flPwX4OYATC0Usa9EKmZFojWE
debug1: Host 'myserverip' is known and matches the ED25519 host key.
debug1: Found key in /my/ssh/folder/known_hosts:5
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug2: key: /my/ssh/folder/myconkyuserid_rsa (0x5560479c2e00), explicit, agent
debug2: key: will@will-Inspiron-7520 (0x5560479c2ea0), agent
debug2: key: /my/ssh/folder/id_ed25519 (0x5560479b5060), explicit
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /my/ssh/folder/myconkyuserid_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
debug2: input_userauth_pk_ok: fp SHA256:PanRCck33pj+N8mNWoTLkaoaVudzUQlv5CTaF12SJ0Y
debug1: Authentication succeeded (publickey).
Authenticated to myserverip ([myserverip]:22).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Requesting [email protected]
debug1: Entering interactive session.
debug1: pledge: exec
debug1: client_input_global_request: rtype [email protected] want_reply 0
debug2: callback start
debug2: x11_get_proto: /usr/bin/xauth  list :0 2>/dev/null
debug1: Requesting X11 forwarding with authentication spoofing.
debug2: channel 0: request x11-req confirm 1
debug2: fd 3 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug1: Sending environment.
debug1: Sending env LC_PAPER = 
debug2: channel 0: request env confirm 0
debug1: Sending env LC_ADDRESS = 
debug2: channel 0: request env confirm 0
debug1: Sending env LC_MONETARY = 
debug2: channel 0: request env confirm 0
debug1: Sending env LC_NUMERIC = 
debug2: channel 0: request env confirm 0
debug1: Sending env LC_TELEPHONE = 
debug2: channel 0: request env confirm 0
debug1: Sending env LC_IDENTIFICATION = 
debug2: channel 0: request env confirm 0
debug1: Sending env LANG = en_GB.UTF-8
debug2: channel 0: request env confirm 0
debug1: Sending env LC_MEASUREMENT = 
debug2: channel 0: request env confirm 0
debug1: Sending env LC_TIME = en_GB.UTF-8
debug2: channel 0: request env confirm 0
debug1: Sending env LC_NAME = 
debug2: channel 0: request env confirm 0
debug1: Sending command: conky -c /path/to/myconky/config 
debug2: channel 0: request exec confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 99 id 0
debug2: X11 forwarding request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: exec request accepted on channel 0
debug2: channel 0: rcvd ext data 7
conky: debug2: channel 0: written 7 to efd 7
debug2: channel 0: rcvd ext data 108
debug2: channel 0: rcvd ext data 62
Syntax error (/path/to/myconky/config:2: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
debug2: channel 0: written 170 to efd 7
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 36372
debug2: fd 8 setting O_NONBLOCK
debug1: channel 1: new [x11]
debug1: confirm x11
debug2: channel 0: rcvd ext data 65
conky: desktop window (1a00022) is subwindow of root window (d5)
debug2: channel 0: written 65 to efd 7
debug2: channel 0: rcvd ext data 28
conky: window type - normal
debug2: channel 0: written 28 to efd 7
debug2: channel 0: rcvd ext data 45
conky: drawing to created window (0x5200001)
debug2: channel 0: written 45 to efd 7
debug2: channel 0: rcvd ext data 32
conky: drawing to double buffer
debug2: channel 0: written 32 to efd 7
debug2: channel 0: rcvd ext data 42
conky: forked to background, pid is 14055
debug2: channel 0: written 42 to efd 7
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype [email protected] reply 0
debug2: channel 0: rcvd eow
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug2: channel 1: rcvd eof
debug2: channel 1: output open -> drain
debug2: channel 1: obuf empty
debug2: channel 1: close_write
debug2: channel 1: output drain -> closed
debug1: channel 1: FORCE input drain
debug2: channel 1: ibuf empty
debug2: channel 1: send eof
debug2: channel 1: input drain -> closed
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug2: channel 0: rcvd close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 2
debug2: channel 1: send close
debug2: channel 1: rcvd close
debug2: channel 1: is dead
debug2: channel 1: garbage collecting
debug1: channel 1: free: x11, nchannels 1
Transferred: sent 16740, received 12920 bytes, in 3.8 seconds
Bytes per second: sent 4378.2, received 3379.1
debug1: Exit status 0

conky 文件中有一些语法错误（这是一个非常旧的文件，但它完成了我想要的工作）但我认为它们不会导致问题，就像我ssh -X进入服务器然后启动 conky 一切都按预期工作.

（注意上面的代码输出没有使用屏幕，因为使用屏幕清除终端。看起来它正在经历基本相同的过程）