We changed our privacy policy. Read more.

New answers tagged

1

Here's another answer purely about Committed_AS being lower than "expected": The interesting lines from your /proc/meminfo are as follows: Active: 4854772 kB Inactive: 5386896 kB Active(anon): 33468 kB Inactive(anon): 412616 kB Active(file): 4821304 kB Inactive(file): 4974280 kB Mlocked: 10948 kB AnonPages: ...


0

chaning the .pcapng into .pcap also worked for me ...$ tcpdump -i enp43s0f1 -c 10 -w logs/temp.pcapng tcpdump: logs/temp.pcapng: Permission denied ...$ tcpdump -i enp43s0f1 -c 10 -w logs/temp.pcap tcpdump: listening on enp43s0f1, link-type EN10MB (Ethernet), capture size 262144 bytes ^C0 packets captured 0 packets received by filter 0 packets dropped by ...


0

Key must much with the certificate you use. Otherwise you won't be able to use them together. One way to make sure both key and certificate match (certificate comes from the private key being used) is by checking their modulus with openssl. openssl rsa -in file.key -noout -modulus openssl x509 -in file.crt -noout -modulus Note: If certificate or key are ...


0

In my experience, Committed_AS has been more accurate than MemAvailable. Especially with highly spikey workload the MemAvailable seems to be more like some kind of average instead of true value over short time periods. That said, I don't remember using data from Committed_AS with kernels older than version 4.15 so I don't know if historical behavior was ...


Top 50 recent answers are included