policycoreutils: run_init: clarification of the usage in the manual page
It's a very minor thing really, but I believe (on the basis of an off-list question) that the manual page for policycoreutils/run_init can be improved by the following short patch which aims to further clarify the intended usage of such tool and mention that it caters for one (somewhat hidden) compile-time option. Signed-off-by: Eric Paris <eparis@redhat.com> Acked-by: Dan Walsh <dwalsh@redhat.com>
This commit is contained in:
parent
d761cc9849
commit
3ed7221bf7
|
@ -9,6 +9,10 @@ run_init \- run an init script in the proper SELinux context
|
||||||
.PP
|
.PP
|
||||||
Run a init script under the proper context, which is specified in
|
Run a init script under the proper context, which is specified in
|
||||||
/etc/selinux/POLICYTYPE/contexts/initrc_context.
|
/etc/selinux/POLICYTYPE/contexts/initrc_context.
|
||||||
|
It is generally used interactively as it requires either shadow or
|
||||||
|
PAM user authentication (depending on compile-time options). It
|
||||||
|
should be possible to configure PAM such that interactive input is
|
||||||
|
not required. Check your PAM documentation.
|
||||||
.SH FILES
|
.SH FILES
|
||||||
/etc/passwd - user account information
|
/etc/passwd - user account information
|
||||||
.br
|
.br
|
||||||
|
|
Loading…
Reference in New Issue