. . . . . . . . . 8 1.2.3 Permissions du système de fichiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2.4 Contrôle des permissions pour les fichiers nouvellement nouvellement créés : umask . . . . . . . . . . . . . . . . . . . 10 1.2.5 Permissions pour les groupes d’utilisateurs (group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.2.6 Horodatage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 6.1.1 Usurpation de la chaîne User-Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 6.1.2 Extension

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 : Administrator (sur système Windows, si Firebird est lancé par cet utilisateur) a aussi besoin de permissions d'accès aux objets de la base. Par soucis de simplicité ici, nous allons voir comment se connecter specify a database SQL>CONNECT "C:\Program Files\Firebird\Firebird_1_5\examples\employee.fdb"# CON>user 'SYSDBA' password 'masterkey';# Firebird 1.5 Guide de démarrage 16 Important • Dans isql, chaque

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