14%
28.11.2011
shown in Figure 4.
Figure 4: Header bytes 12-15.
Looking at byte 13, if SYN and ACK are set, then your binary value would be 00010010
, which
14%
26.01.2012
written = 216,707,618 (216.707618 MB)
Number of Write function calls = 35,369
Average (mean) bytes per call = 6,131.210016 (bytes) (0.006131 MB)
Standard Deviation bytes per call = 112
14%
15.02.2012
written = 216,707,618 (216.707618 MB)
Number of Write function calls = 35,369
Average (mean) bytes per call = 6,131.210016 (bytes) (0.006131 MB)
Standard Deviation bytes per call = 112
14%
30.04.2012
, use the winenum
script and the scraper
script. The winenum
script will dump tokens and hashes, providing you with lots of information (see Figure 6). The scraper
script will pull down the registry
14%
14.04.2021
will see a screen like that shown in Figure 6. Notice that a small window opens just above the process table listing CPU usage, memory usage, the user, and more about that process
14%
29.09.2020
the graphical interface or with text files in JSON format [6] stored in the /etc/cockpit/machines.d/ directory. A configuration file would resemble Listing 1: "address" can be either the IP address or the DNS
14%
14.03.2013
: 6
08 microcode : 0x60c
09 cpu MHz : 800.000
10 cache size : 6144 KB
11 physical id : 0
12 siblings : 2
13 core id : 0
14 cpu cores : 2
15 apicid
14%
01.08.2019
_path": "/var/log/osquery",
07 "disable_logging": "false",
08 "schedule_splay_percent": 10
09 },
10 "schedule": {
11 "osquery_profile": {
12 "query": "SELECT * FROM osquery_info;",
13
14%
01.08.2019
frameworks as DIY plugins. On the same principle, Karma plugins support continuous integration with Jenkins [5], Travis [6], or Semaphore [7].
After launching, Karma first loads all the plugins and parses its
14%
30.01.2024
and assigning tasks to the build nodes.
Another important component of the build system is Pulp [6], which provides artifact storage for newly-built packages and other products of the build process. According
