Use correct syntax markup for shell
Approved by: carlavilla
This commit is contained in:
parent
55c95407aa
commit
a9a9e66105
666 changed files with 17924 additions and 17924 deletions
|
|
@ -92,7 +92,7 @@ This section aims to illustrate the meanings of some of the terms defined above
|
|||
|
||||
This simple example shows `alice` man:su[1]'ing to `root`.
|
||||
|
||||
[source,bash]
|
||||
[source,shell]
|
||||
....
|
||||
% whoami
|
||||
alice
|
||||
|
|
@ -116,7 +116,7 @@ root
|
|||
|
||||
The example below shows `eve` try to initiate an man:ssh[1] connection to `login.example.com`, ask to log in as `bob`, and succeed. Bob should have chosen a better password!
|
||||
|
||||
[source,bash]
|
||||
[source,shell]
|
||||
....
|
||||
% whoami
|
||||
eve
|
||||
|
|
@ -289,7 +289,7 @@ auth required pam_nologin.so no_warn
|
|||
|
||||
As a consequence of this simplified syntax, it is possible to use the same policy for multiple services by linking each service name to a same policy file. For instance, to use the same policy for the `su` and `sudo` services, one could do as follows:
|
||||
|
||||
[source,bash]
|
||||
[source,shell]
|
||||
....
|
||||
# cd /etc/pam.d
|
||||
# ln -s su sudo
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue