en tant que guide de l’utilisateur d’un système installé. Il couvre de nombreux aspects de l’administration du système à l’ aide d’exemples de commandes de l’interpréteur pour les non-développeurs. Référence l’administrateur . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.5 Outils graphiques d’administration du système . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.6 Consoles virtuelles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 6.1.1 Usurpation de la chaîne User-Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 6.1.2 Extension

............................................................................. 12 Un outil d'administration ............................................................................................ XP Ouvrez Panneau de configuration -> Services (NT) ou Panneau de configuration -> Outils d'administration -> Services (2000, XP). Cette capture d'écran montre l'état des services sous Windows 2000. Tapez le commande suivante (c'est sensible à la casse sur toutes les plateformes sauf Windows): gsec -user sysdba -password masterkey Vous devriez alors avoir l'invite de commande de l'utilitaire gsec :

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2020.23) 17 / 307 1.23 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.23 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2020.22) 16 / 294 1.22 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.22 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.6) 15 / 173 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.9) 15 / 173 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.4) 15 / 167 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.3) 15 / 159 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate lignes de vie peuvent être imbriquées, et il est possible de les colorer. @startuml participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest PlantUML (1.2019.2) 15 / 159 1.20 Return 1 DIAGRAMME DE SÉQUENCE deactivate B deactivate A A -> User: Done deactivate A @enduml 1.20 Return A new command return for generating a return message with

participant User User -> A: DoWork activate A A -> B: << createRequest >> activate B B -> C: DoWork activate C C --> B: WorkDone destroy C B --> A: RequestCreated deactivate B A -> User: Done deactivate participant User User -> A: DoWork activate A #FFBBBB A -> A: Internal call activate A #DarkSalmon A -> B: << createRequest >> activate B B --> A: RequestCreated deactivate B deactivate A A -> User: Done 60 skinparam sequenceParticipant underline actor User participant "First Class" as A participant "Second Class" as B participant "Last Class" as C User -> A: DoWork activate A A -> B: Create Request activate