12%
05.09.2011
can see how the arp cache poisoning works:
$ sudo nemesis arp -v -r -d eth0 -S 192.168.1.2 \
-D 192.168.1.133 -h 00:22:6E:71:04:BB -m 00:0C:29:B2:78:9E \
-H 00:22:6E:71:04:BB -M 00:0C:29:B2:78:9E
12%
21.08.2012
6 ### 8/5/2012
7
8 ### Set the job name
9 #PBS -N mpi_pi_fortran90
10
11 ### Run in the queue named “batch”
12 #PBS -q batch
13
14 ### Specify the number of cpus for your job. This example
12%
25.09.2023
guest
82a84,88
>
> tee /etc/.htpasswd <<'EOF'
> guest:$apr1$gz4n7s6o$P.O/V1k9rZuV9nN/5lh3l0
> admin:$apr1$esczj7wu$ffu/6j8vETMAMJaVTKn7a1
> EOF
Monit is configured to load service
12%
30.01.2024
Dell Precision Workstation T7910
Power
1,300W
CPU
2x Intel Xeon Gold E5-2699 V4, 22 cores, 2.4GHz, 55MB of cache, LGA 2011-3
GPU, NPU
n/a*
Memory
12%
17.01.2023
is working, boot the compute node and run timedatectl
:
$ ssh n0001
[laytonjb@n0001 ~]$ timedatectl
Local time: Sat 2022-12-17 11:31:26 EST
Universal time: Sat 2022-12
12%
04.04.2023
timedatectl
$ ssh n0001
[laytonjb@n0001 ~]$ timedatectl
Local time: Sat 2022-12-17 11:31:26 EST
Universal time: Sat 2022-12-17 16:31:26 UTC
RTC time: Sat 2022-12
12%
02.08.2021
SGEMM
for N = [2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192]
A = single( rand(N,N) );
B = single( rand(N,N) );
start = clock();
C = A*B;
elapsedTime = etime(clock(), start
12%
25.03.2021
unused devices:
Listing 5
View RAID Details
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Sat Jan 9 15:22:29 2021
Raid Level
12%
02.08.2021
nvmet-rd0 -a 10.0.0.185 -s 4420
and verify that the NVMe subsystem sees the NVMe target (Listing 9).
Listing 9
Verify the NVMe Target Is Seen
$ sudo nvme list
Node SN
11%
12.05.2020
68e152db7e5bb36b1cca638",
"sha256:37b9a4b2218692d028f9f26aa9cb85bf1f56d9abe612ba31304643bdb448484f",
"sha256:b16af11cbf2977eb52ba4d6cee5b713721cc19812b8c90ea1f22e7e
