Debian10.2 Samba4.9.5 Windows Server 2019 Datacenter Active Directory Domainのメンバー に参加してみた

 

root@debian:~# kinit administrator
Password for administrator@TEST.JP:
root@debian:~# net ads join -U administrator
Enter administrator’s password:
Using short domain name — TEST
Joined ‘DEBIAN’ to dns domain ‘test.jp’
No DNS domain configured for debian. Unable to perform DNS Update.
DNS update failed: NT_STATUS_INVALID_PARAMETER
root@debian:~# systemctl restart winbind
root@debian:~# wbinfo -u
TEST\administrator
TEST\guest
TEST\krbtgt
TEST\chibi
root@debian:~# wbinfo -n chibi
S-1-5-21-3288142828-1890802880-3761831349-1103 SID_USER (1)
root@debian:~# net ads info
LDAP server: 192.168.1.7
LDAP server name: dc.test.jp
Realm: TEST.JP
Bind Path: dc=TEST,dc=JP
LDAP port: 389
Server time: 水, 29 1月 2020 16:13:27 JST
KDC server: 192.168.1.7
Server time offset: -5
Last machine account password change: 水, 29 1月 2020 16:12:39 JST
root@debian:~# host -4 dc
dc.test.jp has address 192.168.1.10
dc.test.jp has address 192.168.1.7
dc.test.jp has IPv6 address 2400:4052:46e0:b700:4f:d564:2171:d644
dc.test.jp has IPv6 address 2400:4052:46e0:b700:b965:55ce:a6fa:cbe
root@debian:~# host -4 dc1
dc1.test.jp has address 192.168.1.11
dc1.test.jp has IPv6 address 2400:4052:46e0:b700:85f5:d25e:c529:278a
root@debian:~# host -4 dc2
dc2.test.jp has address 192.168.1.12
dc2.test.jp has IPv6 address 2400:4052:46e0:b700:309e:ebe1:748c:e149
root@debian:~# host -t SRV _ldap._tcp.test.jp
_ldap._tcp.test.jp has SRV record 0 100 389 dc2.test.jp.
_ldap._tcp.test.jp has SRV record 0 100 389 dc1.test.jp.
_ldap._tcp.test.jp has SRV record 0 100 389 dc.test.jp.
root@debian:~# host -t SRV _kerberos._udp.test.jp
_kerberos._udp.test.jp has SRV record 0 100 88 dc1.test.jp.
_kerberos._udp.test.jp has SRV record 0 100 88 dc2.test.jp.
_kerberos._udp.test.jp has SRV record 0 100 88 dc.test.jp.
root@debian:~# host -t A test.jp
test.jp has address 192.168.1.10
test.jp has address 192.168.1.7
test.jp has address 192.168.1.12
test.jp has address 192.168.1.11
root@debian:~# smbclient -L localhost -U%

Sharename Type Comment
——— —- ——-
netlogon Disk
sysvol Disk
print$ Disk Printer Drivers
IPC$ IPC IPC Service (Samba 4.9.5-Debian)
Reconnecting with SMB1 for workgroup listing.

Server Comment
——— ——-

Workgroup Master
——— ——-
TEST DC
WORKGROUP DEBIAN
root@debian:~# smbclient -L localhost -U%

Debian10.2 Samba4.9.5 Windows Server 2019 Datacenter Active Directory Domainのメンバー に参加してみた

カテゴリー: debian, samba4, windows | コメントする

Arch Linux Kernel5.4.15-arch1-1 Update

Arch Linux Kernelが5.4.15-arch1-1にUpdateされました。

[root@arch ~]# uname -r
5.4.15-arch1-1
[root@arch ~]# php -v
PHP 7.4.2 (cli) (built: Jan 21 2020 18:16:58) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
[root@arch ~]# curl -V
curl 7.68.0 (x86_64-pc-linux-gnu) libcurl/7.68.0 OpenSSL/1.1.1d zlib/1.2.11 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh2/1.9.0 nghttp2/1.39.2
Release-Date: 2020-01-08
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets
[root@arch ~]# samba -V
Version 4.10.10
[root@arch ~]# cat /etc/os-release
NAME=”Arch Linux”
PRETTY_NAME=”Arch Linux”
ID=arch
BUILD_ID=rolling
ANSI_COLOR=”0;36″
HOME_URL=“https://www.archlinux.org/”
DOCUMENTATION_URL=“https://wiki.archlinux.org/”
SUPPORT_URL=“https://bbs.archlinux.org/”
BUG_REPORT_URL=“https://bugs.archlinux.org/”
LOGO=archlinux
[root@arch ~]#

カテゴリー: archlinux | コメントする

Ubuntu16.04.5 TESLA V100-SXM2 16GB x4 CUDA 9.0 Samples simpleP2P p2pBandwidthLatencyTest 他を動作させてみた

user0018@10-111-146-12:~/cuda-samples-9.0/samples/0_Simple/simpleP2P$ ./simpleP2P
[./simpleP2P] – Starting…
Checking for multiple GPUs…
CUDA-capable device count: 4
> GPU0 = “Tesla V100-SXM2-16GB” IS capable of Peer-to-Peer (P2P)
> GPU1 = “Tesla V100-SXM2-16GB” IS capable of Peer-to-Peer (P2P)
> GPU2 = “Tesla V100-SXM2-16GB” IS capable of Peer-to-Peer (P2P)
> GPU3 = “Tesla V100-SXM2-16GB” IS capable of Peer-to-Peer (P2P)

Checking GPU(s) for support of peer to peer memory access…
> Peer access from Tesla V100-SXM2-16GB (GPU0) -> Tesla V100-SXM2-16GB (GPU1) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU0) -> Tesla V100-SXM2-16GB (GPU2) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU0) -> Tesla V100-SXM2-16GB (GPU3) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU1) -> Tesla V100-SXM2-16GB (GPU0) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU1) -> Tesla V100-SXM2-16GB (GPU2) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU1) -> Tesla V100-SXM2-16GB (GPU3) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU2) -> Tesla V100-SXM2-16GB (GPU0) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU2) -> Tesla V100-SXM2-16GB (GPU1) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU2) -> Tesla V100-SXM2-16GB (GPU3) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU3) -> Tesla V100-SXM2-16GB (GPU0) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU3) -> Tesla V100-SXM2-16GB (GPU1) : Yes
> Peer access from Tesla V100-SXM2-16GB (GPU3) -> Tesla V100-SXM2-16GB (GPU2) : Yes
Enabling peer access between GPU0 and GPU1…
Checking GPU0 and GPU1 for UVA capabilities…
> Tesla V100-SXM2-16GB (GPU0) supports UVA: Yes
> Tesla V100-SXM2-16GB (GPU1) supports UVA: Yes
Both GPUs can support UVA, enabling…
Allocating buffers (64MB on GPU0, GPU1 and CPU Host)…
Creating event handles…
cudaMemcpyPeer / cudaMemcpy between GPU0 and GPU1: 44.84GB/s
Preparing host buffer and memcpy to GPU0…
Run kernel on GPU1, taking source data from GPU0 and writing to GPU1…
Run kernel on GPU0, taking source data from GPU1 and writing to GPU0…
Copy data back to host from GPU0 and verify results…
Disabling peer access…
Shutting down…
Test passed
user0018@10-111-146-12:~/cuda-samples-9.0/samples/0_Simple/simpleP2P$ cd ~/cuda-samples-9.0/samples/1_Utilities
user0018@10-111-146-12:~/cuda-samples-9.0/samples/1_Utilities$ ls
bandwidthTest deviceQueryDrv topologyQuery
deviceQuery p2pBandwidthLatencyTest
user0018@10-111-146-12:~/cuda-samples-9.0/samples/1_Utilities$ cd p2pBandwidthLatencyTest
user0018@10-111-146-12:~/cuda-samples-9.0/samples/1_Utilities/p2pBandwidthLatencyTest$ ./p2pBandwidthLatencyTest
[P2P (Peer-to-Peer) GPU Bandwidth Latency Test]
Device: 0, Tesla V100-SXM2-16GB, pciBusID: 61, pciDeviceID: 0, pciDomainID:0
Device: 1, Tesla V100-SXM2-16GB, pciBusID: 62, pciDeviceID: 0, pciDomainID:0
Device: 2, Tesla V100-SXM2-16GB, pciBusID: 89, pciDeviceID: 0, pciDomainID:0
Device: 3, Tesla V100-SXM2-16GB, pciBusID: 8a, pciDeviceID: 0, pciDomainID:0
Device=0 CAN Access Peer Device=1
Device=0 CAN Access Peer Device=2
Device=0 CAN Access Peer Device=3
Device=1 CAN Access Peer Device=0
Device=1 CAN Access Peer Device=2
Device=1 CAN Access Peer Device=3
Device=2 CAN Access Peer Device=0
Device=2 CAN Access Peer Device=1
Device=2 CAN Access Peer Device=3
Device=3 CAN Access Peer Device=0
Device=3 CAN Access Peer Device=1
Device=3 CAN Access Peer Device=2

***NOTE: In case a device doesn’t have P2P access to other one, it falls back to normal memcopy procedure.
So you can see lesser Bandwidth (GB/s) in those cases.

P2P Connectivity Matrix
D\D 0 1 2 3
0 1 1 1 1
1 1 1 1 1
2 1 1 1 1
3 1 1 1 1
Unidirectional P2P=Disabled Bandwidth Matrix (GB/s)
D\D 0 1 2 3
0 748.32 9.92 11.02 11.03
1 9.96 742.63 11.02 11.07
2 11.05 11.03 744.05 9.94
3 11.04 11.01 9.92 745.47
Unidirectional P2P=Enabled Bandwidth Matrix (GB/s)
D\D 0 1 2 3
0 744.05 47.91 47.95 47.89
1 47.90 745.47 47.96 47.96
2 47.91 47.97 746.89 48.00
3 47.97 47.90 47.97 745.47
Bidirectional P2P=Disabled Bandwidth Matrix (GB/s)
D\D 0 1 2 3
0 764.43 10.38 18.92 17.99
1 10.42 765.93 18.08 17.56
2 18.79 18.23 763.69 10.41
3 17.86 17.49 10.43 762.94
Bidirectional P2P=Enabled Bandwidth Matrix (GB/s)
D\D 0 1 2 3
0 762.20 95.58 95.67 95.58
1 95.37 765.93 95.67 95.65
2 95.37 95.39 765.93 95.44
3 95.48 95.46 95.51 769.70
P2P=Disabled Latency Matrix (us)
D\D 0 1 2 3
0 4.21 20.29 19.84 19.75
1 20.36 4.27 20.36 20.39
2 20.30 20.31 3.92 18.73
3 19.48 19.49 18.69 3.26
P2P=Enabled Latency Matrix (us)
D\D 0 1 2 3
0 4.14 7.38 7.32 7.02
1 8.32 4.37 7.45 7.52
2 6.80 6.84 4.04 6.79
3 6.81 6.75 6.88 3.39

NOTE: The CUDA Samples are not meant for performance measurements. Results may vary when GPU Boost is enabled.
user0018@10-111-146-12:~/cuda-samples-9.0/samples/1_Utilities/p2pBandwidthLatencyTest$

Ubuntu16.04.5 TESLA V100-SXM2 16GB x4 CUDA 9.0 Samples simpleP2P p2pBandwidthLatencyTest 他

カテゴリー: nvidia, ubuntu | コメントする

Samba 4.11.6 Available for Download

Samba 4.11.6が公開されました。ReleaseNoteはこちらです。

カテゴリー: samba4 | コメントする

FreeBSD 13.0-CURRENT PHP 7.4.2 Update

FreeBSD 13.0-CURRENT PHPが7.4.2にUpdateされました。

root@freebsd:~ # uname -a
FreeBSD freebsd 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r357002: Thu Jan 23 04:35:00 UTC 2020 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
root@freebsd:~ # php -v
PHP 7.4.2 (cli) (built: Jan 25 2020 01:34:48) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
root@freebsd:~ # curl -V
curl 7.68.0 (amd64-portbld-freebsd13.0) libcurl/7.68.0 OpenSSL/1.1.1d zlib/1.2.11 nghttp2/1.40.0
Release-Date: 2020-01-08
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: alt-svc AsynchDNS GSS-API HTTP2 HTTPS-proxy IPv6 Kerberos Largefile libz NTLM NTLM_WB SPNEGO SSL TLS-SRP UnixSockets
root@freebsd:~ # samba -V
Version 4.10.11
root@freebsd:~ #

カテゴリー: freebsd | コメントする