Table des matières
2 billet(s) pour janvier 2026
| Git - Duplication d'un dépôt | 2026/01/19 10:22 | Jean-Baptiste |
| Exemple simple de conf Nagios | 2026/01/14 10:07 | Jean-Baptiste |
Notes Communication inter-processus RPC
Voir :
Exemple :
- RestAPI
- gRPC / Protocol Buffers
- GraphQL
- ZeroMQ /ZeroRPC et autres
- Socket.io
- RSocket.io
- Apache Avro
- Apache Thrift
Notes nested virtualization
prereq
Source : https://gist.github.com/plembo/782e1511e463221b5772e85b6f2f72d4#file-nestedvirtkvm-md
- Make sure that the Intel-VT-x/AMD-V extensions are enabled in the host machine's BIOS. For Intel:
grep vmx /proc/cpuinfo
For AMD:
grep svm /proc/cpuinfo
- Check to see if /etc/modprobe.d/qemu-system-x86.conf exists and if it does not have the following line, add it and reboot:
options kvm_intel nested=1
- Go into the graphical virt-manager, open the subject guest's config, and click on “CPUs”.
- Check the box “Copy host CPU configuration” and Apply.
- Restart the virtual machine, open a terminal in it and check for the extensions:
grep vmx /proc/cpuinfo
Source : https://docs.fedoraproject.org/en-US/quick-docs/using-nested-virtualization-in-kvm/
Checking if nested virtualization is supported
cat /sys/module/kvm_intel/parameters/nested Y
To enable nested virtualization for Intel processors:
Shut down all running VMs and unload the kvm_probe module:
sudo modprobe -r kvm_intel
Activate the nesting feature:
sudo modprobe kvm_intel nested=1
Nested virtualization is enabled until the host is rebooted. To enable it permanently, add the following line to the /etc/modprobe.d/kvm.conf file:
options kvm_intel nested=1
To enable nested virtualization for AMD processors:
Shut down all running VMs and unload the kvm_amd module:
sudo modprobe -r kvm_amd
Activate the nesting feature:
sudo modprobe kvm_amd nested=1
Nested virtualization is enabled until the host is rebooted. To enable it permanently, add the following line to the /etc/modprobe.d/kvm.conf file:
options kvm_amd nested=1
Testing nested virtualization
virt-host-validate
Notes IPython derrière un reverse proxy
Docker-compose
Password less.
docker-compose.yml
version: '3.7' services: ipython: image: jupyter/base-notebook restart: unless-stopped # Warning : No password ! command: ["start-notebook.sh", "--NotebookApp.token=''","--NotebookApp.password=''"] environment: GRANT_SUDO: "no" user: root ports: - '127.0.0.1:8083:8888' volumes: - ipython_work:/home/jovyan/work networks: - ipython-net networks: ipython-net: name: ipython-net volumes: ipython_work:
J'ai eu me même pb : http://stackoverflow.com/questions/22665809/how-to-configure-ipython-behind-nginx-in-a-subpath
server { listen 80; root /usr/share/nginx/www; index index.html index.htm index.php ; server_name notebook.mondomain.fr ; error_log /var/log/nginx/error-notebook.log; location / { proxy_pass http://localhost:5001; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-NginX-Proxy true; # WebSocket support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_read_timeout 86400; } location ^~ /static/ { alias /usr/share/ipython/notebook/static/; } }
cd mkdir books vim ipython_notebook_config.py
c = get_config() c.IPKernelApp.pylab = 'inline' # if you want plotting support always c.NotebookApp.open_browser = False c.NotebookApp.port = 5001
vi /etc/cron.allow crontab -e @reboot cd ${HOME}/books ; ipython3 notebook --pylab=inline --no-browser --profile=notebook >${HOME}/notebook.log 2>${HOME}/notebook.err
Notes install IPython sous Android avec Termux
Install iPython sur Android Termux
pkg update pkg upgrade pip install --user ipython
Notes fichiers - binaire executable exe elf
Voir aussi :
file exefile strings exefile objdump -s -j .rodata exefile ldd exefile
readelf -x .rodata hello_world.o
| -h | Displays the ELF header, which contains key information about the file’s structure. |
| -S | Lists all the sections in the ELF file, showing details about each section’s address, size, type, and attributes. |
| -l | Displays the program headers, which describe the segments used at runtime. |
| -s | Shows the symbol table, including symbols defined and used in the ELF file. |
| -r | Displays the relocation sections, showing how the binary modifies itself at runtime. |
| -d | Displays the dynamic section, which contains information about dynamic linking. |
| -n | Displays core notes, which include metadata such as the build ID. |
Autres
objdump -d /lib64/libc-2.9.so | fgrep -A5 '<time>:'
