. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 9.4.15 Scheduling tasks on event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 9.4.16 Tecla . . . . . . . . . . 203 10.2.3.2 Mount event triggered backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 10.2.3.3 Timer event triggered backup . . . . . . . . . . . . ficheiros que correspondem a alguma condição, ex. que corres- pondem ao modelo glob ”*.ext”. • Método for-loop da shell (veja Secção 12.1.4): for x in *.ext; do if [ -f ”$x”]; then command ”$x” ; fi; done •

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 9.4.15 Scheduling tasks on event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 9.4.16 Die . . . . . . . . . . 209 10.2.3.2 Mount event triggered backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 10.2.3.3 Timer event triggered backup . . . . . . . . . . . . Näheres in systemd.timer(5) . 9.4.15 Scheduling tasks on event Systemd can schedule program not only on the timer event but also on the mount event. See Abschnitt 10.2.3.3 and Abschnitt 10.2.3.2 for examples

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 2.1.8 The event flow of the package management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 perl(1) example, ”-i” is for the in-place editing of each target file, and ”-p” is for the implicit loop over all given files. Debian Reference 35 / 238 Tip Use of argument ”-i.bak” instead of ”-i” keeps List of script snippets for piping commands Debian Reference 37 / 238 A one-line shell script can loop over many files using find(1) and xargs(1) to perform quite complicated tasks. See Sec- tion 10.1

network and where to download the server ISO from. 6. The RAM Disk downloads the ISO and mounts it as a loop device. 7. From this point on the install follows the same path as if the ISO was on a local block focal-live-server-pp 100% |....................| 922M 0:00:00 ETA • Next is to loop-back mount the ISO: / # mkdir iso / # mount -o loop focal-live-server-ppc64el.iso iso Or in case autodetect of type iso9660 explicitly specify the ‘iso9660’ type: / # mount -t iso9660 -o loop focal-live-server-ppc64el.iso iso • Now load kernel and initrd from the loop-back mount, specify any needed kernel parameters and get it

build, runtime dependencies, and upstream communities of the open source software form a closed loop, realizing a complete, transparent software supply chain management. Open and Transparent Management Compared to native NFS, eNFS boasts three key innovations. • It enables second-level failover in the event of software or hardware faults on I/O paths. It also ensures multiple links between the client and active-active path failover on a three-layer network. It enables cross-site active-active failover in the event of storage faults or host-side I/O timeouts, effectively resolving cross-engine failures and host

tracing write(2) calls - $ rbperf record \ --pid=124 event \ --tracepoint=syscalls:sys_enter_write - $ rbperf report [...] Architecture 2. Event (timer, syscall, etc) BPF code (bpf/rbperf.c) Read thread address) 3. Receives stacktrace 4. Serialisation and persistence BPF tail-calls Bounded loop Challenges - Implementing the stack walking for a dynamic language Challenges - Implementing the

hearts, we strive to provide be�er tooling for troubleshoo�ng. This includes tooling to provide: Event monitoring with metadata: When a packet is dropped, the tool doesn’t just report the source and des�na�on performed for kube-dns $ kubectl delete pods -n kube-system $(kubectl get pods -n kube-system -o pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" deleted pod "heapster-v1 produces into Ka�a topic authaudit a JSON-forma�ed message which contains the following informa�on: event: login or logout username client IP address �mestamp To observe the Ka�a messages sent by productpage

hearts, we strive to provide better tooling for troubleshooting. This includes tooling to provide: Event monitoring with metadata: When a packet is dropped, the tool doesn’t just report the source and destination may be seeing cilium install print something like this: ♻ Restarted unmanaged pod kube-system/event-exporter-gke-564fb97f9- rv8hg ♻ Restarted unmanaged pod kube-system/kube-dns-6465f78586-hlcrz ♻ --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" deleted pod "heapster-v1

hearts, we strive to provide better tooling for troubleshooting. This includes tooling to provide: Event monitoring with metadata: When a packet is dropped, the tool doesn’t just report the source and destination name,HOSTNETWORK:.spec.hostNetwork -- no-headers=true | grep '' | awk '{ print $1 }') pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" deleted pod "heapster-v1 produces into Kafka topic authaudit a JSON-formatted message which contains the following information: event: login or logout username client IP address timestamp To observe the Kafka messages sent by productpage

hearts, we strive to provide better tooling for troubleshooting. This includes tooling to provide: Event monitoring with metadata: When a packet is dropped, the tool doesn’t just report the source and destination may be seeing cilium install print something like this: ♻ Restarted unmanaged pod kube-system/event-exporter-gke-564fb97f9- rv8hg ♻ Restarted unmanaged pod kube-system/kube-dns-6465f78586-hlcrz ♻ --no-headers=true | grep '' | awk '{print "-n "$1" "$2}' | xargs -L 1 -r kubectl delete pod pod "event-exporter-v0.2.3-f9c896d75-cbvcz" deleted pod "fluentd-gcp-scaler-69d79984cb-nfwwk" deleted pod "heapster-v1