AdminSysGNULinux

Outils pour utilisateurs

Outils du site

Piste : • blog
blog

Table des matières

10 billet(s) pour avril 2026

Pb wine2026/04/19 11:09Jean-Baptiste
Inclure ASM dans Go lang2026/04/19 02:27Jean-Baptiste
Inclure du C dans Go lang2026/04/19 01:32Jean-Baptiste
Notes API REST2026/04/18 21:40Jean-Baptiste
Création image conteneur - exemple de multi-stage builds2026/04/18 17:07Jean-Baptiste
Exécuter du code python avec go lang2026/04/18 17:00Jean-Baptiste
Inclure des appels à Go lang dans Python2026/04/18 16:14Jean-Baptiste
Notes protocoles TCP/IP - IGMP et multicast2026/04/15 09:42Jean-Baptiste
Notes go lang programmation fonctionnelle2026/04/13 22:27Jean-Baptiste
Notes ping ICMP2026/04/03 23:01Jean-Baptiste

Xorg.conf généré par nvidia-xconfig

Voir : 

nvidia-xconfig
nvidia-xconfig -a
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 440.64
 
Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection
 
Section "Files"
EndSection
 
Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection
 
Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection
 
Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection
 
Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection
 
Section "Screen"
    Identifier     "Screen0"
    Device         "nvidia"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Faire fonctionner la carte intégrée pour l'écran

Voir LinuxFr - Utiliser la carte graphique NVIDIA et la carte INTEL intégrée

PS : Xorg est obligé de créer un “Screen” par carte graphique, et qu'un Screen n'est pas un écran physique

/etc/X11/xorg.conf
Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen1"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    #Option         "ConstrainCursor" "off"
    Option         "UseDisplayDevice" "none"
    Option         "ProbeAllGpus" "false"
    Option         "AllowEmptyInitialConfiguration"
    #Option         "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier     "Intel"
    BusID          "PCI:0:2:0"
    Driver         "modesetting"
    VendorName     "Intel Corporation"
    #BoardName      "Display controller"
    #ModelName      "Device 3e98"
    #Option         "AccelMethod" "SNA"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Intel"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "nvidia"
EndSection
$ lspci | grep 'Display controller: Intel Corporation Device' | awk -F'[:. ]' '{print $1, $2, $3}' | sed -r 's|0([0-9]) |\1:|g'
0:2:0

https://github.com/Bumblebee-Project/Bumblebee/blob/master/conf/xorg.conf.nvidia

xorg.conf
Section "ServerLayout"
    Identifier  "Layout0"
    Option      "AutoAddDevices" "false"
    Option      "AutoAddGPU" "false"
EndSection

Section "Device"
    Identifier  "DiscreteNvidia"
    Driver      "nvidia"
    VendorName  "NVIDIA Corporation"

#   If the X server does not automatically detect your VGA device,
#   you can manually set it here.
#   To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
#   as you see in the commented example.
#   This Setting may be needed in some platforms with more than one
#   nvidia card, which may confuse the proprietary driver (e.g.,
#   trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
#   BusID "PCI:01:00:0"

#   Setting ProbeAllGpus to false prevents the new proprietary driver
#   instance spawned to try to control the integrated graphics card,
#   which is already being managed outside bumblebee.
#   This option doesn't hurt and it is required on platforms running
#   more than one nvidia graphics card with the proprietary driver.
#   (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
#   If this option is not set, the new Xorg may blacken the screen and
#   render it unusable (unless you have some way to run killall Xorg).
    Option "ProbeAllGpus" "false"

    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "UseDisplayDevice" "none"
EndSection

https://gist.githubusercontent.com/mokkabonna/7ebf99590e42fcee9dfe/raw/6963a2e2ff6255a2ee251435953eba27cc9f5275/gistfile1.txt

xorg.conf
Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    #Inactive "intel" # Not supported ?
EndSection

Section "Device"
    Identifier "intel"
    Driver "intel"
    BusID "PCI:0@0:2:0"
    Option "AccelMethod" "SNA"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:2@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

https://gist.githubusercontent.com/dvejmz/879eebb607b9069b536b/raw/df2ec920573326cd05f95452d5af87a4d055e6e4/sample-xorg.conf

xorg.conf
Section "ServerLayout"
	Identifier "layout"
	Screen 0 "nvidia"
	#Inactive "intel" # Not supported ?
EndSection

Section "Device"
	Identifier "nvidia"
	Driver "nvidia"
	BusID "PCI:1:0:0"
EndSection

Section "Screen"
	Identifier "nvidia"
	Device "nvidia"
	Option "AllowEmptyInitialConfiguration" "Yes"
EndSection

Section "Device"
	Identifier "intel"
	Driver "modesetting"
	Option "AccelMethod" "none"
EndSection

Section "Screen"
	Identifier "intel"
	Device "intel"
EndSection
2025/03/24 15:06

windows - Tester un flux quand telnet n'est pas la

tnc 192.168.120.198 -Port 80

ou 

Test-NetConnection 192.168.120.198 -Port 80
2025/03/24 15:06
, , ,

Windows - Active Directory - Vérifier si un compte AD est verrouillé - locked

# export KRB5CCNAME=/var/lib/sss/db/ccache_ACME.LOCAL
# ldapsearch -H ldap://ldap.acme.local -Y GSSAPI -N -b "DC=ACME,DC=LOCAL" "(CN=COMPTE_AD_A_TESTER)" |grep -i lock
SASL/GSSAPI authentication started
SASL username: PLOP@ACME.LOCAL
SASL SSF: 256
SASL data security layer installed.
lockoutTime: 133195559287541069

Le compte est bien verrouillé.
Si lockoutTime != 0 alors le compte est verrouillé.

Pour connaître depuis quand le compte est verrouillé sous windows : 

C:\WINDOWS\system32>w32tm /ntte 133195559287541069
154161 12:38:48.7541069 - 30/01/2023 14:38:48

FIXME

2025/03/24 15:06
, , ,

VPN dans une VM dédiée qui fera office de router

Test avec LibVirt et OpenVPN :

Ma VM est config de la sorte : eth1 192.168.100.220 tun0 10.8.0.14 (Client OpenVPN configuré)

Au début depuis l'hôte je ne peut piguer que eth1

Je cherche à pourvoir piguer l'interface tun0 (toujours depuis l'hôte)

Sur la VM 

echo 1 > /proc/sys/net/ipv4/ip_forward

Sur l'hôte (virbr0 est l'interface NAT de libvirt) 

ip route add 10.8.0.0/24 via 192.168.100.220 dev virbr0
ping 10.8.0.14

Ça marche

Par contre je ne peut pas encore piguer le server VPN (10.8.0.1)

Pour cela :

Sur la VM (tun0 est l'interface VPN) 

iptables -t nat -A POSTROUTING -o tun0 -j MASQUERADE
2025/03/24 15:06
, , ,

VM Création de FS LVM à chaud

Voir scsiadd
Voir draft-vm-disques-a-chaud 

ls -l /dev/sd*
brw-rw---T 1 root disk 8, 0 févr. 25 16:19 /dev/sda
brw-rw---T 1 root disk 8, 1 févr. 25 16:19 /dev/sda1
brw-rw---T 1 root disk 8, 2 févr. 25 16:19 /dev/sda2
brw-rw---T 1 root disk 8, 5 févr. 25 16:37 /dev/sda5
echo "- - -" > /sys/class/scsi_host/host0/scan
echo "- - -" > /sys/class/scsi_host/host1/scan
echo "- - -" > /sys/class/scsi_host/host2/scan

Voir : http://hdeterssac.free.fr/?p=117 http://ma.ttias.be/increase-a-vmware-disk-size-vmdk-formatted-as-linux-lvm-without-rebooting/

Pour la partie LVM : http://doc.ubuntu-fr.org/lvm 

ls -l /dev/sd*
brw-rw---T 1 root disk 8,  0 févr. 25 16:19 /dev/sda
brw-rw---T 1 root disk 8,  1 févr. 25 16:19 /dev/sda1
brw-rw---T 1 root disk 8,  2 févr. 25 16:19 /dev/sda2
brw-rw---T 1 root disk 8,  5 févr. 25 16:37 /dev/sda5
brw-rw---T 1 root disk 8, 16 févr. 25 16:57 /dev/sdb

pvcreate /dev/sdb 
  Writing physical volume data to disk "/dev/sdb"
  Physical volume "/dev/sdb" successfully created

vgcreate vg_data /dev/sdb
  Volume group "vg_data" successfully created

lvcreate -L 5G -n mysql vg_data
  Logical volume "mysql" created
2025/03/24 15:06
, , , ,

<< Billets récents | Anciens billets >>

blog.txt · Dernière modification : de 127.0.0.1
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki