AdminSysGNULinux

Outils pour utilisateurs

Outils du site

Piste : • blog
blog

Table des matières

3 billet(s) pour avril 2026

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

Coloration des pages man grâce à Most

http://identity-labs.fr/article-5-installation-dun-serveur-lamp-debian-zend-server

Nous allons installer Most, un utilitaire qui ajoute la coloration aux pages de manuel: 

apt-get install most

Puis indiquons à man qu'il doit utiliser most 

update-alternatives --config pager
2025/03/24 15:06

Yum force pb erreur le fichier de l'installation entre en conflit avec le fichier du paquet

Comment faire un yum --force en trichant un peu

Pb

le fichier /var/www de l'installation de httpd-2.4.6-40.el7.centos.1.x86_64 entre en conflit avec le fichier du paquet plop-1.8.8-2.noarch

Solution

Solution possible : Refaire proprement le package plop

ou forcer ! Nous allons utiliser yumdownloader (packet yum-utils) 

yum install yum-utils
yumdownloader httpd
rpm -Uvh --force httpd-2.4.6-40.el7.centos.1.x86_64.rpm

Pour que ça marche, il faut faire la même chose avec toutes les dépendances 

# yumdownloader --resolve httpd-tools
yumdownloader httpd-tools
rpm -Uvh --force httpd-2.4.6-40.el7.centos.1.x86_64.rpm httpd-tools-2.4.6-40.el7.centos.1.x86_64.rpm
2025/03/24 15:06

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
, , ,

<< 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