33%
17.06.2011
sprzblog mysql ↩
limesurvey -uroot -ppassword > ↩
backup.sql
will take 21 seconds to complete:
real 0m21.626s
user 0m0.000s
sys 0m0.000s
In the case of larger databases on non
33%
30.11.2025
sprzblog mysql limesurvey -uroot -ppassword > backup.sql
will take 21 seconds to complete:
real 0m21.626s
user 0m0.000s
sys 0m0.000s
In the case of larger databases on non-replicated servers
33%
31.10.2025
disk fails, the sum of all remaining bits reveals whether the missing disk would need to have a 0 or a 1 to meet the even or odd status stored on the parity disk.
The advantage of RAID 3 is that you
33%
05.12.2019
, 4, 5 }, // row 0 initialized to 1, 2, 3, 4, 5
{ 6, 7, 8, 9, 10 }, // row 1 initialized to 6, 7, 8, 9 ...
}; // rows 2 onwards initialized to zeros
**
int
33%
08.06.2021
ran the “plain” NumPy code with Legate:
$ legate test1.py
[0 - 7f080ae4e000] 0.000070 {4}{threads}: reservation ('Python-1 proc 1d00000000000006') cannot be satisfied
Elapsed time = 2
32%
02.02.2021
5221548db 58 seconds ago 5.67MB
80dc7d447a48 About a minute ago 167MB
alpine 3.9 78a2ce922f86 5 months ago 5.55MB
The command you really
32%
05.12.2019
Container
$ podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/nmap latest 53890e393585 34 seconds ago 425 MB
**
$ podman run --rm localhost
32%
25.05.2012
. Something along the lines of:
TID PRIO USER DISK READ DISK WRITE IO> COMMAND
18981 be/4 www-data 0.00 B/s 3.92 K/s apache2 -k start
Or, if you were trying to see which system user
32%
07.07.2020
command is:
$ time cp /mnt/data/Downloads/octave-5.1.0.tar.gz /tmp
real 0m46.298s
user 0m0.000s
sys 0m0.034s
Don’t worry about the performance of the transfer. After the transfer, take a look
32%
04.10.2018
of their internal 2.5-inch SATA devices, coming in at a mere 2.3x3x0.5 inches (5.8x7.6x1.3 cm) – smaller than a Post-it note (Figure 1). Available in sizes ranging from 256GB to 2TB, the specimen in our lab is the MU
