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%
03.02.2022
eMMC (not populated)
Network
1x Topaz networking switch
2x GbE LAN
1x Ethernet WAN
1x MiniPCIe slot
USB
1x USB 3.0
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%
29.06.2012
| | | | | | |/ _` | |
| | |_| | | | (_| | | Version 0.0.0+86921303.rc6cb
_/ |\__'_|_|_|\__'_| | Commit c6cbcd11c8 (2012-05-25 00:27:29)
|__/ |
julia>
If you don't want to see the title on subsequent start ups use julia -q
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%
20.06.2012
is to find out whether it runs on the master node when it is booted by using the chkconfig
command:
[root@test1 etc]# chkconfig --list
...
nfs 0:off 1:off 2:off 3:off 4:off 5:off 6
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%
25.09.2023
is used per the netcat report:
localhost [127.0.0.1] 80 (http): Connection refused
The result in the hosttext variable is then checked for warnings and errors, which are reported if detected
