Differences

This shows you the differences between two versions of the page.

--- start [2024/11/15 12:11] – dokuroot
+++ start [2025/09/30 12:42] (current) – dokuroot
@@ Line 1: / Line 1: @@
-====== LANDING PAGE OF THE QUARK TOP!! ======
+====== RANDOMIZED THINGS FOR THE QUARK TOP ======
+A hint as to why this page is named as such: https://cms.cern/news/two-most-massive-quarks-put-spotlight-higgs-boson
+\\
+[[taskwarrior-notes|Notes on Taskwarrior]]
+[[iloveclim-dep-notes|Notes on iLOVECLIM dependencies]]
+====== Admunix related things ======
+==== Working as www-data "user" ====
+<code>
+sudo su - www-data -s /bin/bash
+</code>
+====== Network related things ======
+==== DNS Server check with dig ====
+Check this for details: https://jvns.ca/blog/2021/11/04/how-do-you-tell-if-a-problem-is-caused-by-dns \\
+As a summary, try to get the website dns through:
+<code>
+$ dig iloveclim.eu
+</code>
+which, if functionnal will respond something like
+<code>
+iloveclim.eu.		3600	IN	A	78.196.23.159
+</code>
+Trying a non-existing sub-domain:
+<code>
+$ dig toto.iloveclim.eu
+toto.iloveclim.eu.		IN	A
+</code>
+To check with a different name server, provide the nameserver ip as in (e.g. cloudfare):
+<code>
+$ dig @1.1.1.1 toto.iloveclim.eu
+</code>
+(this allows to check for DNS failures in current nameserver)
+====== FORTRAN related things ======
+==== Create a callgraph ====
+We can use valgrind to create a callgraph as follows. After compiling the code with the -pg option run:
+<code>
+valgrind --dsymutil=yes --tool=callgrind myexec.x
+</code>
+After the run, obtained ''callgrind.out.1234'' file can be processed with gprof2dot as:
+<code>
+gprof2dot.py -n0 -e0 ./callgrind.out.1992 -f callgrind > callgrind.out.1234.dot
+</code>
+Then use dot to create the actual graph:
+<code>
+dot -Tpng out.dot -o out.png
+</code>
+In the case you want to filter out the system calls from the graph, the solution of : [[https://stackoverflow.com/a/7774742]] works like a charm.