16%
01.08.2012
mpi/mpich2/1.5b1-open64-5.0 modulefile
#%Module1.0#####################################################################
##
## modules mpi/mpich2/1.5b1-open64-5.0
##
## modulefiles/mpi/mpich2/1.5b1
16%
05.08.2024
= [size][size]int {{0},{0},}
08
09 for i := 0; i < size; i++ {
10 for j := 0; j < size; j++ {
11 array[i][j]++
12 }
13 }
14
15
16%
17.06.2017
on your system:
# nmcli device status
DEVICE TYPE STATE CONNECTION
wls1 wifi connected --
enp0s25 ethernet connected --
lo loopback unmanaged --
To configure the Ethernet card with a static IPv4 address
16%
04.08.2020
->tv_nsec) * 1E-9;
24 }
25
26 int main(int argc, char* argv[argc+1]) {
27 if (argc < 2) {
28 fprintf(stderr, "Usage: %s NNN, NNN iterations\n",
29 argv[0]);
30 return EXIT_FAILURE;
31 }
32
16%
02.02.2021
FD TYPE DEVICE SIZE/OFF NODE NAME
docker-pr 13330 root 4u IPv4 91904 0t0 TCP *:2222 (LISTEN)
A simple test is to use the unerring, ultra-reliable netcat to see what is coming back
16%
10.12.2023
, availability, performance, and capacity. For example, RAID 0 stripes data across multiple storage devices to improve performance, whereas RAID 1 mirrors data across storage devices to improve data availability
16%
30.11.2025
see immediately that, if you have a small number of shoppers, the time required to pass through checkout (the residence time) is identical to the service time. If no other shoppers arrive (lambda = 0
16%
11.06.2014
architecture => 'i686'
10 kernel => 'Linux'
11 kernelrelease => '3.11.0-15-generic'
12 }
13 $hostname = 'sugar'
14 $operating_system = 'Ubuntu'
15 $operatingsystem = 'Ubuntu'
16 $operating
16%
11.04.2016
that bypasses the filesystem and accesses the underlying layer (e.g., device files such as /dev/sda or /dev/dm-0) directly.
In comparison, a filesystem benchmark addresses the filesystem but does not necessarily
16%
01.08.2019
, it is better to omit the -d so you can discover errors that could cause Unbound to stop directly.
Unbound should be working now. You can test the Unbound DNS resolver from another computer with dig:
dig @192.168.0
