29%
08.10.2015
:/etc/smtpd_remote.db
04 listen on 192.0.2.15 inet4 port 25 hostname post.example.org tls pki post
05 listen on 192.0.2.15 inet4 port 587 hostname mail.example.org tls-require pki mail auth tag remote
06 listen
29%
27.08.2014
was the sequential write test using 1MB record sizes:
./iozone -i 0 -c -e -w -r 1024k -s 32g -t 2 -+n > iozone_write_1.out
To gather the block statistics, I ran ioprof in a different terminal window before I ran
29%
08.05.2019
(i=0; i < n; i++)
{
...
}
for (j=0; j < m; j++)
{
...
}
for (k=0; k < n*m; k++)
{
...
}
Listing 2: Parallelized Sets of Loops
Fortran
C
!$omp parallel do
do i=1,n
29%
04.12.2024
MOUNTPOINTS
sda 8:0 0 25G 0 disk
|-sda1 8:1 0 1M 0 part
|-sda2 8:2 0 25G 0 part /var/snap/firefox/common/host-hunspell
In my case, I also want to configure my client
29%
17.02.2015
not to log the SYSTEM_BOOT event type. Using
ausearch -m 2>&1 | tr ' ' '\n' | grep '[A-Z]$' | sort
will show a list of all available event types.
Viewing Log Files
The ausearch command can also be used
29%
07.09.2025
Hub, S3, Samba v2 and v3, Dropbox, and possibly others.
One aspect of ratarmount
that I don’t like is that it mounts the archive as read-only and then keeps any changes or new files in a separate
29%
30.11.2025
to configure them. And, all this easily can be handled with a matching structure and a sophisticated Kickstart profile on the Spacewalk server [2]. An article on this topic was published not so long ago in Admin
29%
22.10.2012
rack straw 2 root straw 0
The --num_osds 6
parameter specifies that the cluster has six individual storage devices at its disposal. The --build
option introduces a statement with three three ... RADOS and Ceph: Part 2 ... The RADOS object store and Ceph filesystem: Part 2
29%
31.10.2025
straw 2 tells RADOS that two servers exist per rack. root straw 0 refers to the number of racks and determines that the replicas should be distributed equally on all available racks.
Subsequently, if you ... RADOS and Ceph : Part 2 ... The RADOS object store and Ceph filesystem: Part 2
29%
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
