45%
25.10.2011
1
05 set remote-gw 192.168.1.31
06 set psksecret
ENC kB+sdP4e109vAROdm9TRn9YIzA47T3JHPK4xVOzYu/8nc3wmqBknMZBzfHU7VRuWBF2gncDuHY1ubeCk9DU3zasHi61Izu0m6cg1cdERjgNmKKcO
07 set keepalive
45%
20.05.2014
LAN_IF=eth0
DMZ_IF=eth2
LAN_NET=2001:db8:1::/64
DMZ_NET=2001:db8:2::/64
Next, completely reset the firewall rules to delete any previously existing rules. You can use the -F option for this. You also
45%
30.01.2020
its execution in the real world (real), as well as how much CPU time was allocated in user and kernel (sys) modes:
$ time sleep 1
real 0m1.004s
user 0m0.002s
sys 0m0.001s
What not everyone knows
45%
18.12.2013
(One-by-One)
1 #include
2
3 /* Our structure */
4 struct rec
5 {
6 int x,y,z;
7 float value;
8 };
9
10 int main()
11 {
12 int counter;
13 struct rec my_record;
14 int counter_limit;
15
45%
07.01.2014
[laytonjb@home4 TEST]$ rsync -a --delete /home/laytonjb/TEST/SOURCE/ backup.0
[laytonjb@home4 TEST]$ ls -s
total 8
4 backup.0/ 4 SOURCE/
[laytonjb@home4 TEST]$ du -sh
16M .
[laytonjb@home4 TEST]$ du -sh
45%
30.11.2025
/0K /s] [4137 /0 iops] [eta 00m:06s]
In the example, the first job is performing a sequential read, marked as r in square brackets, while Fio hasn't initialized the second job, marked as P
44%
15.02.2012
/lsdyna/benchmark-file/tmp/./mes0007
1
/etc/localtime
209
/dev/shm/Intel_MPI_4m1pPG
209
/dev/shm/Intel_MPI_QV00CT
209
/dev/shm/Intel_MPI_QV00CT
44%
26.01.2012
/lsdyna/benchmark-file/tmp/./mes0007
1
/etc/localtime
209
/dev/shm/Intel_MPI_4m1pPG
209
/dev/shm/Intel_MPI_QV00CT
209
/dev/shm/Intel_MPI_QV00CT
44%
30.11.2025
04 errs: 0, errxfer: 0.0k, succxfer: 1667072.0k
05 +curr.rate: 5270kB/s, avg.rate: 5808kB/s, avg.load: 8.1%
The resulting image, sdb
44%
05.06.2013
, learning curve, ease of use, complexity, and, doggone it, just plain fun. But the focus is to keep the cost down while you are learning. The one aspect of clusters that I’m not really going to focus
