Table des matières
4 billet(s) pour janvier 2026
| AWX sur K8S Kind - partage de fichier pour les blob - Execution pods | 2026/01/26 10:15 | Jean-Baptiste |
| Notes rsh rcp | 2026/01/21 18:08 | Jean-Baptiste |
| 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 matériel matos hardware
Test
Voir SMART
Test chauf CPU
for i in $(seq $(getconf _NPROCESSORS_ONLN)); do yes > /dev/null & done
CPU
Voir aussi : Unités de traitement de données (DPU) Data Processing Unit
AltairX : le processeur du futur ?
x86-64_v2 (ou v2) : Processeurs anciens à partir de Intel Core i ou AMD FX-41xx et actuels x86-64_v3 (ou v3) : Processeurs actuels à partir de Intel Core i 4xxx, Pentium G3xxx ou Celeron G18xx ou AMD Athlon X4
Réseau
NAS
QNAP
Électronique
Notes LXQT
Chemins
| Xdg Data Home | /home/user1/.local/share |
| Xdg Config Home | /home/user1/.config |
| Xdg Data Dirs | /home/user1/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share |
| Xdg Cache Home | /home/user1/.cache |
| Xdg Runtime Home | /run/user/1000 |
| Xdg Autostart Dirs | /etc/xdg/autostart |
| Xdg Autostart Home | /home/user1/.config/autostart |
Désactiver le zoom du gestionnaire de fenêtre xfwm4
Lancer xfwm4-tweaks-settings puis
Compositor - Zoom destop with mouse wheel
Ce qui revient à changer
~/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml
<?xml version="1.0" encoding="UTF-8"?> <channel name="xfwm4" version="1.0"> <property name="general" type="empty"> <!-- others lines --> <!-- property name="zoom_desktop" type="bool" value="true"/ --> <property name="zoom_desktop" type="bool" value="false"/> <!-- others lines --> </property> </channel>
Compilation lximage-qt
sudo apt-get install git make cmake #sudo apt-get install qtbase5-dev libqt5widgets5 libqt5x11extras5-dev qttools5-dev libqt5svg5-dev libfm-qt-dev #sudo apt-get install $(apt-cache search ^qt |grep dev |grep ^qt |awk '{print $1}' |grep dev$) sudo apt-get build-dep lximage-qt git clone https://github.com/lxqt/lximage-qt cd lximage-qt mkdir build cd build cmake .. make -j $(nproc)
Transparence LXQt LXDE
sudo apt-get install compton compton-conf
Puis lancer compton-conf
~/.config/openbox/autostart
#@compton -c -r 16 -l -24 -t -12 -G -b @compton
Alt Tab affiche les applications de tous les écrans virtuels
Source https://www.mostad.eu/how-to-make-alt-tab-show-windows-from-all-desktops-in-lubuntu/
Ajouter :
<allDesktops>yes</allDesktops>
dans le fichier ci dessous
~/.config/openbox/lxqt-rc.xml
<!-- Keybindings for window switching --> <keybind key="A-Tab"> <action name="NextWindow"> <allDesktops>yes</allDesktops> <finalactions> <action name="Focus"/> <action name="Raise"/> <action name="Unshade"/> </finalactions> </action> </keybind> <keybind key="A-S-Tab"> <action name="PreviousWindow"> <allDesktops>yes</allDesktops> <finalactions> <action name="Focus"/> <action name="Raise"/> <action name="Unshade"/> </finalactions> </action> </keybind>
Puis
openbox --reconfigure
Autres
Openbox as Window Manager
~/.config/lxqt/session.conf
[General] __userfile__=true #window_manager=xfwm4 window_manager=openbox
Pb après débrancher le second écran, les fenêtres sont inaccessibles
Solution
~/.config/openbox/lxqt-rc.xml
<keybind key="W-F1"> <action name="MoveResizeTo"> <!-- move the window to the second monitor --> <monitor>1</monitor> <!-- put the window in the bottom right corner --> <x>center</x> <y>center</y> </action> </keybind>
Reload de la conf OpenBox
openbox --reconfigure
Pb
Clef USB / Removable media open with
Solution :
- Open the LXQt Configuration Center (lxqt-config) and click on “File Associations” there. Or directly start lxqt-config-file-associations.
- Navigate to “inode → mount-point”, click “Change”, and choose “PCManFM-Qt File Manager”, the default file manager of LXQt.
- Let's also disable the additional popup of PCManFM-Qt when inserting a medium. (Reasons: it does not appear for SD cards which seems to be a bug, it is redundant anyway as there's still the bottom right popover, and the PCManFM-Qt popup is not part of the planned “proper solution” in the future.) :
- In PCManFM-Qt, go to “Edit → Preferences → Volume”.
- In section “Auto Mount”, uncheck all three options.
- Confirm with “OK”.
~/.config/mimeapps.list
[Default Applications] inode/mount-point=pcmanfm-qt.desktop;
Si pb file association file browser
~/.local/share/applications/mimeapps.list
[Added Associations] #inode/directory=nautilus.desktop #inode/directory=nemo.desktop inode/directory=pcmanfm-qt.desktop
Perso
apt-get install ibus nm-tray pavucontrol-qt vlc-plugin-qt apt-get install snapd #snap install --classic notepadqq apt-get install notepadqq
sudo apt-get install featherpad
Preferences → Text → Dark Color Scheme
~/.config/featherpad/fp.conf
[text] darkColorScheme=true
Voir
apt-cache search qt |awk '{print $1}' |grep '\-qt$'
~/.bashrc
ssh-add -l >/dev/null if [[ $? -eq 1 ]] then ssh-add fi
sudo update-alternatives --config x-session-manager
Notes LXDE
Pb
Source : https://www.raspberrypi.org/forums/viewtopic.php?t=163858
Voir : PolKit (anciennement PolicyKit)
Quand : à l'ouverture de la session utilisateur
Erreur
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PolicyKit1 was not provided by any .service files
Solution
apt-get install policykit-1
Notes
policykit-gnome ou lxpolkit ?
Notes LVM
Voir :
lv_attrs
man 8 lvs
Extents are the smallest units of space that you can allocate in LVM. Physical extents (PE) and logical extents (LE) has the default size of 4 MiB that you can configure. All extents have the same size. When you create a logical volume (LV) within a VG, LVM allocates physical extents on the PVs
Création LVs
lvcreate -l 100%FREE -n newlv vg_data
Script - get size lv_size & vgfree space
lvs --readonly --noheadings --nosuffix --units=m /dev/mapper/applivg-lv_plop -o lv_size vgs --readonly --noheadings --nosuffix --units=m applivg -o vgfree
Pb
# pvcreate /dev/sda3 Device /dev/sda3 not found (or ignored by filtering).
# pvcreate -vvv /dev/sda3 2>&1|grep '/dev/sda3'
/dev/sda3: Skipping: Too small to hold a PV
Tags
vgchange --deltag T9 --deltag T10 --addtag T13 --addtag T14 grant pvs -o pv_tags /dev/sda2 vgs -o vg_tags /dev/VolGroup00 lvs -o lv_tags /dev/VolGroup00/LogVol00
Use the following command to list all the logical volumes with the database tag
lvs @database
Use the following command to list the currently active host tags
lvm tags
Autres
Resize the PV when some data was allocated at the end of the LVM.
pvs -v --segments /dev/sda5 pvmove --alloc anywhere /dev/sda5:yyyy-end pvs -v --segments /dev/sda5
Notes luks cryptsetup
Voir aussi :
- homectl
- Clevis / Tang Server
Add a new passphrase
cryptsetup luksAddKey /dev/nvme0n1p3
cryptsetup luksDump /dev/sda2
Upgrade your LUKS key derivation function
Source :
lsblk sudo cryptsetup luksHeaderBackup /dev/whatever --header-backup-file /tmp/luksheader
Copy that to a USB stick or something. If something goes wrong here you'll be able to boot a live image and run
sudo cryptsetup luksHeaderRestore /dev/whatever --header-backup-file luksheader
to restore it.
(Edit to add: Once everything is working, delete this backup! It contains the old weak key, and someone with it can potentially use that to brute force your disk encryption key using the old KDF even if you've updated the on-disk KDF.)
Next, run
sudo cryptsetup luksDump /dev/whatever
and look for the Version: line. If it's version 1, you need to update the header to LUKS2. Run
sudo cryptsetup convert /dev/whatever --type luks2
and follow the prompts. Make sure your system still boots, and if not go back and restore the backup of your header. Assuming everything is ok at this point, run
sudo cryptsetup luksDump /dev/whatever
again and look for the PBKDF: line in each keyslot (pay attention only to the keyslots, ignore any references to pbkdf2 that come after the Digests: line). If the PBKDF is either pbkdf2 or argon2i you should convert to argon2id. Run the following:
sudo cryptsetup luksConvertKey /dev/whatever --pbkdf argon2id
and follow the prompts. If you have multiple passwords associated with your drive you'll have multiple keyslots, and you'll need to repeat this for each password.
Distributions! You should really be handling this sort of thing on upgrade. People who installed their systems with your encryption defaults several years ago are now much less secure than people who perform a fresh install today. Please please please do something about this.
