tripathysagar/man_text huggingface dataset:
# pam_namespace_helper

## NAME



           pam_namespace_helper - Helper binary that creates home directories
    


## SYNOPSIS



    
           **pam_namespace_helper**
    


## DESCRIPTION



           _pam_namespace_helper_ is a helper program for the _pam_namespace_
           module that sets up a private namespace for a session with
           polyinstantiated directories. The helper ensures that the
           namespace mount points exist before they are started to be used
           for the polyinstantiated directories. Mount points for home
           directories (lines with $HOME) are not created.
    
           _pam_namespace_helper_ should be run by systemd at system startup.
           It should also be run by the administrator after defining the
           polyinstantiated directories but before enabling them.
    


* * *
# btrfs-select-super

## NAME



           btrfs-select-super - overwrite primary superblock with a backup
           copy
    


## SYNOPSIS



           **btrfs-select-super** -s number _< device>_
    


## DESCRIPTION



           Destructively overwrite all copies of the superblock with a
           specified copy. This helps in certain cases, for example when
           write barriers were disabled during a power failure and not all
           superblocks were written, or if the primary superblock is damaged,
           eg. accidentally overwritten.
    
           The filesystem specified by _device_ must not be mounted.
    
               **Note**
    
               **Prior to overwriting the primary superblock, please make sure**
               **that the backup copies are valid!**
    
           To dump a superblock use the **btrfs inspect-internal dump-super**
           command.
    
           Then run the check (in the non-repair mode) using the command
           **btrfs check -s** where _-s_ specifies the superblock copy to use.
    
           Superblock copies exist in the following offsets on the device:
    
           •   primary: _64KiB_ (65536)
    
           •   1st copy: _64MiB_ (67108864)
    
           •   2nd copy: _256GiB_ (274877906944)
    
           A superblock size is _4KiB_ (4096).
    


## OPTIONS



           -s|--super _< superblock>_
               use 'superblock’th superblock copy, valid values are 0 1 or 2
               if the respective superblock offset is within the device size
    


* * *
# semodule_expand

## NAME



           semodule_expand - Expand a SELinux policy module package.
    


## SYNOPSIS



           **semodule_expand [-ahV] [ -c [version]] basemodpkg outputfile**
    


## DESCRIPTION



           semodule_expand is a developer tool for manually expanding a base
           policy module package into a kernel binary policy file.  This tool
           is not necessary for normal operation of SELinux.  In normal
           operation, such expanding is performed internally by libsemanage
           in response to semodule commands.  Base policy module packages can
           be created directly by semodule_package or by semodule_link (when
           linking together a set of packages into a single package).
    


## OPTIONS



           **-h** show help
    
           **-V** show version
    
           **-c [version]**
                  policy version to create
    
           **-a** Do not check assertions.  This will cause the policy to not
                  check any neverallow rules.
    


* * *
# cups-snmp

## NAME



           snmp - cups snmp backend (deprecated)
    


## SYNOPSIS



           **/usr/lib/cups/backend/snmp** _ip-address-or-hostname_
           **/usr/libexec/cups/backend/snmp** _ip-address-or-hostname_
           **lpinfo -v --include-schemes** snmp
    


## DESCRIPTION



           The **DEPRECATED** CUPS SNMP backend provides legacy discovery and
           identification of network printers using SNMPv1.  When used for
           discovery through the scheduler, the backend will list all
           printers that respond to a broadcast SNMPv1 query with the
           "public" community name.  Additional queries are then sent to
           printers that respond in order to determine the correct device
           URI, make and model, and other information needed for printing.
    
           In the first form, the SNMP backend is run directly by the user to
           look up the device URI and other information when you have an IP
           address or hostname.  This can be used for programs that need to
           configure print queues where the user has supplied an address but
           nothing else.
    
           In the second form, the SNMP backend is run indirectly using the
           lpinfo(8) command.  The output provides all printers detected via
           SNMP on the configured broadcast addresses.  _Note: no broadcast_
           _addresses are configured by default._
    


## ENVIRONMENT



           The DebugLevel value can be overridden using the CUPS_DEBUG_LEVEL
           environment variable.  The MaxRunTime value can be overridden
           using the CUPS_MAX_RUN_TIME environment variable.
    


## FILES



           The SNMP backend reads the _/etc/cups/snmp.conf_ configuration file,
           if present, to set the default broadcast address, community name,
           and logging level.
    


## NOTES



           The CUPS SNMP backend is deprecated and will no longer be
           supported in a future version of CUPS.
    


## CONFORMING TO



           The CUPS SNMP backend uses the information from the Host, Printer,
           and Port Monitor MIBs along with some vendor private MIBs and
           intelligent port probes to determine the correct device URI and
           make and model for each printer.
    


* * *
# rpm-plugin-prioreset

## NAME



           rpm-plugin-prioreset - Plugin for the RPM Package Manager to fix
           issues with priorities of deamons on SysV init
    


## Description



           In general scriptlets run with the same priority as rpm(8) itself.
           However on legacy SysV init systems, properties of the parent
           process can be inherited by the actual daemons on restart.  As a
           result daemons may end up with unwanted nice or ionice values.
           This plugin resets the scriptlet process priorities after forking,
           and can be used to counter that effect.  Should not be used with
           systemd(1) because it's not needed there, and the effect is
           counter-productive.
    


## Configuration



           There are currently no options for this plugin in particular.  See
           rpm-plugins(8) on how to control plugins in general.
    


* * *
# semanage-user

## NAME



           **semanage-user - SELinux Policy Management SELinux User mapping**
           **tool**
    


## SYNOPSIS



           **semanage user [-h] [-n] [-N] [-S STORE] [ --add ( -L LEVEL -R**
           **ROLES -r RANGE SEUSER) | --delete SEUSER | --deleteall | --extract**
           **| --list [-C] | --modify ( -L LEVEL -R ROLES -r RANGE SEUSER ) ]**
    


## DESCRIPTION



           semanage is used to configure certain elements of SELinux policy
           without requiring modification to or recompilation from policy
           sources.  **semanage user** controls the mapping between an SELinux
           User and the roles and MLS/MCS levels.
    


## OPTIONS



           _-h, --help_
                  Show this help message and exit
    
           _-n, --noheading_
                  Do not print heading when listing the specified object type
    
           _-N, --noreload_
                  Do not reload policy after commit
    
           _-S STORE, --store STORE_
                  Select an alternate SELinux Policy Store to manage
    
           _-C, --locallist_
                  List local customizations
    
           _-a, --add_
                  Add a record of the specified object type
    
           _-d, --delete_
                  Delete a record of the specified object type
    
           _-m, --modify_
                  Modify a record of the specified object type
    
           _-l, --list_
                  List records of the specified object type
    
           _-E, --extract_
                  Extract customizable commands, for use within a transaction
    
           _-D, --deleteall_
                  Remove all local customizations
    
           _-L LEVEL, --level LEVEL_
                  Default SELinux Level for SELinux user, s0 Default.
                  (MLS/MCS Systems only)
    
           _-r RANGE, --range RANGE_
                  MLS/MCS Security Range (MLS/MCS Systems only) SELinux Range
                  for SELinux login mapping defaults to the SELinux user
                  record range. SELinux Range for SELinux user defaults to
                  s0.
    
           _-R [ROLES], --roles [ROLES]_
                  SELinux Roles. You must enclose multiple roles within
                  quotes, separate by spaces. Or specify -R multiple times.
    


## EXAMPLE



           List SELinux users
           # semanage user -l
           Modify groups for staff_u user
           # semanage user -m -R "system_r unconfined_r staff_r" staff_u
           Assign user topsecret_u role staff_r and range s0-TopSecret
           # semanage user -a -R "staff_r" -rs0-TopSecret topsecret_u
    


* * *
# dump-utmp

## NAME



           dump-utmp - print a utmp file in human-readable format
    


## SYNOPSYS



           **dump-utmp**[**-hrR**] [**-n** <_recs_ >] <**files** >
                 [**--num** <_recs_ >] [**--raw**] [**--reverse**] [**--help**]
    


## OPTIONS



           The following options are supported:
    
           **-h, --help**
                  Print a help message and the default location of the
                  process accounting file and exit.
    
           **-r, --reverse**
                  Print the output in reverse order.
    
           **-R, --raw**
                  The records will be printed without any parsing.
    
           **-n, --num NUMRECS**
                  Display only the first NUMRECS number of records.
    


* * *
# ibchecknet

## NAME



           ibchecknet - validate IB subnet and report errors
    


## SYNOPSIS



           **ibchecknet**[-h] [-N | -nocolor] [<topology-file> | -C ca_name -P
           ca_port -t(imeout) timeout_ms]
    


## DESCRIPTION



           ibchecknet is a script which uses a full topology file that was
           created by ibnetdiscover, and scans the network to validate the
           connectivity and reports errors (from port counters).
    


## OPTIONS



           -N | -nocolor use mono rather than color mode
    
           -C <ca_name>    use the specified ca_name.
    
           -P <ca_port>    use the specified ca_port.
    
           -t <timeout_ms> override the default timeout for the solicited
           mads.
    


* * *
# raid6check

## NAME



           raid6check - check MD RAID6 device for errors _aka_ Linux Software
           RAID
    


## SYNOPSIS



           **raid6check** _< raid6 device> <start stripe> <number of stripes>_
    


## DESCRIPTION



           RAID6 devices in which one single component drive has errors can
           use the double parity in order to find out which component drive.
           The "raid6check" tool checks, for each stripe, the double parity
           consistency, reports mismatches and, if possible, which component
           drive has the mismatch.  Since it works at stripe level, it can
           report different drives with mismatches at different stripes.
    
           "raid6check" requires a non-degraded RAID6 MD device as first
           parameter, a starting stripe (usually 0) and the number of stripes
           to be checked.  If this third parameter is also 0, it will check
           the array up to the end.
    
           "raid6check" will start printing information about the RAID6, then
           for each stripe, it will report the parity rotation status.  In
           case of parity mismatches, "raid6check" reports, if possible,
           which component drive could be responsible. Otherwise it reports
           that it is not possible to find the component drive.
    
           If the given MD device is not a RAID6, "raid6check" will, of
           course, not continue.
    
           If the RAID6 MD device is degraded, "raid6check" will report an
           error and it will not proceed further.
    
           No write operations are performed on the array or the components.
           Furthermore, the checked array can be online and in use during the
           operation of "raid6check".
    


## EXAMPLES



             **raid6check /dev/md0 0 0**
           This will check /dev/md0 from start to end.
    
             **raid6check /dev/md3 0 1**
           This will check the first stripe of /dev/md3.
    
             **raid6check /dev/md1 1000 0**
           This will check /dev/md1 from stripe 1000 up to the end.
    
             **raid6check /dev/m127 128 256**
           This will check 256 stripes of /dev/md127 starting from stripe
           128.
    
             **raid6check /dev/md0 0 0 | grep -i error > md0_err.log**
           This will check /dev/md0 completely and create a log file only
           with errors, if any.
    


## FILES



           "raid6check" uses directly the component drives as found in /dev.
           Furthermore, the sysfs interface is needed in order to find out
           the RAID6 parameters.
    


## BUGS



           Negative parameters can lead to unexpected results.
    
           It is not clear what will happen if the RAID6 MD device gets
           degraded during the check.
    
           The latest version of _raid6check_ should always be available from
    
                  **https://www.kernel.org/pub/linux/utils/raid/mdadm/ **
    
           Related man pages:
    
           mdadm(8) mdmon(8), mdadm.conf(5), md(4).
    


* * *
# rpcdebug

## NAME



           rpcdebug - set and clear NFS and RPC kernel debug flags
    


## SYNOPSIS



           **rpcdebug -vh**
           **rpcdebug -m** _module_
           **rpcdebug -m** _module_ **-s** _flags_...
           **rpcdebug -m** _module_ **-c** _flags_...
    


## DESCRIPTION



           The **rpcdebug** command allows an administrator to set and clear the
           Linux kernel's NFS client and server debug flags.  Setting these
           flags causes the kernel to emit messages to the system log in
           response to NFS activity; this is typically useful when debugging
           NFS problems.
    
           The first form in the synopsis can be used to list all available
           debug flags.  The second form shows the currently set debug flags
           for the given module.  The third form sets one or more flags, and
           the fourth form clears one or more flags.
    
           The value **all** may be used to set or clear all the flags for the
           given module.
    


## OPTIONS



           **-c** Clear the given debug flags.
    
           **-h** Print a help message and exit.  When combined with the **-v**
                  option, also prints the available debug flags.
    
           **-m** _module_
                  Specify which module's flags to set or clear.  Available
                  modules are:
    
                  **nfsd** The NFS server.
    
                  **nfs** The NFS client.
    
                  **nlm** The Network Lock Manager, in either an NFS client or
                         server.
    
                  **rpc** The Remote Procedure Call module, in either an NFS
                         client or server.
    
           **-s** Set the given debug flags.
    
           **-v** Increase the verbosity of **rpcdebug** 's output.
    


## FILES



           **/proc/sys/sunrpc/{rpc,nfs,nfsd,nlm}_debug**
                  procfs-based interface to kernel debug flags.
    


## BUGS



           Bugs can be found or reported at **http://nfs.sf.net/ **.
    


* * *
# rpm-plugin-fapolicyd

## NAME



           rpm-plugin-fapolicyd - Fapolicyd plugin for the RPM Package
           Manager
    


## Description



           The plugin gathers metadata of currently installed files.  It
           sends the information about files and about ongoing rpm
           transaction to the fapolicyd daemon.  The information is written
           to Linux pipe which is placed in
           /var/run/fapolicyd/fapolicyd.fifo.
    


## Configuration



           There are currently no options for this plugin in particular.  See
           rpm-plugins(8) on how to control plugins in general.
    


* * *
# tc-skbprio

## NAME



           skbprio - SKB Priority Queue
    


## SYNOPSIS



           **tc qdisc ... add skbprio [ limit** packets **]**
    


## DESCRIPTION



           SKB Priority Queue is a queueing discipline intended to prioritize
           the most important packets during a denial-of-service ( **DoS**)
           attack. The priority of a packet is given by **skb- >priority **, where
           a higher value places the packet closer to the exit of the queue.
           When the queue is full, the lowest priority packet in the queue is
           dropped to make room for the packet to be added if it has higher
           priority. If the packet to be added has lower priority than all
           packets in the queue, it is dropped.
    
           Without SKB priority queue, queue length limits must be imposed on
           individual sub-queues, and there is no straightforward way to
           enforce a global queue length limit across all priorities. SKBprio
           queue enforces a global queue length limit while not restricting
           the lengths of individual sub-queues.
    
           While SKB Priority Queue is agnostic to how **skb- >priority **is
           assigned. A typical use case is to copy the 6-bit DS field of IPv4
           and IPv6 packets using tc-skbedit(8).  If **skb- >priority **is greater
           or equal to 64, the priority is assumed to be 63.  Priorities less
           than 64 are taken at face value.
    
           SKB Priority Queue enables routers to locally decide which packets
           to drop under a DoS attack.  Priorities should be assigned to
           packets such that the higher the priority, the more expected
           behavior a source shows.  So sources have an incentive to play by
           the rules.
    


## ALGORITHM



           Skbprio maintains 64 lists (priorities go from 0 to 63).  When a
           packet is enqueued, it gets inserted at the **tail** of its priority
           list. When a packet needs to be sent out to the network, it is
           taken from the head of the highest priority list. When the queue
           is full, the packet at the tail of the lowest priority list is
           dropped to serve the ingress packet - if it is of higher priority,
           otherwise the ingress packet is dropped. This algorithm allocates
           as much bandwidth as possible to high priority packets, while only
           servicing low priority packets when there is enough bandwidth.
    


## PARAMETERS



           limit  Maximum queue size specified in packets. It defaults to 64.
                  The range for this parameter is [0, UINT32_MAX].
    


* * *
# rpmdb

## NAME



           rpmdb - RPM Database Tool
    


## SYNOPSIS



           **rpmdb**{**--initdb|--rebuilddb**}
    
           **rpmdb**{**--verifydb**}
    
           **rpmdb**{**--exportdb|--importdb**}
    


## DESCRIPTION



           The general form of an rpmdb command is
    
           **rpmdb**{**--initdb|--rebuilddb**} [**-v**] [**--dbpath** _DIRECTORY_] [**--root**
           _DIRECTORY_]
    
           Use **--initdb** to create a new database if one doesn't already exist
           (existing database is not overwritten), use **--rebuilddb** to rebuild
           the database indices from the installed package headers.
    
           **--verifydb** performs a low-level integrity check on the database.
    
           **--exportdb** exports the database in header-list format, suitable
           for transporting to another host or database type.
    
           **--importdb** imports a database from a header-list format as created
           by **--exportdb**.
    


* * *
# systemd-machine-id-commit.service

## NAME



           systemd-machine-id-commit.service - Commit a transient machine ID
           to disk
    


## SYNOPSIS



           systemd-machine-id-commit.service
    


## DESCRIPTION



           systemd-machine-id-commit.service is an early boot service
           responsible for committing transient /etc/machine-id files to a
           writable disk file system. See machine-id(5) for more information
           about machine IDs.
    
           This service is started after local-fs.target in case
           /etc/machine-id is a mount point of its own (usually from a memory
           file system such as "tmpfs") and /etc is writable. The service
           will invoke **systemd-machine-id-setup --commit** , which writes the
           current transient machine ID to disk and unmount the
           /etc/machine-id file in a race-free manner to ensure that file is
           always valid and accessible for other processes. See
           systemd-machine-id-setup(1) for details.
    
           The main use case of this service are systems where
           /etc/machine-id is read-only and initially not initialized. In
           this case, the system manager will generate a transient machine ID
           file on a memory file system, and mount it over /etc/machine-id,
           during the early boot phase. This service is then invoked in a
           later boot phase, as soon as /etc/ has been remounted writable and
           the ID may thus be committed to disk to make it permanent.
    


* * *
# resizecons

## NAME



           resizecons - change kernel idea of the console size
    


## SYNOPSIS



           **resizecons** _COLSxROWS_
           **resizecons -lines** _ROWS_
    


## DESCRIPTION



           The _resizecons_ command tries to change the videomode of the
           console.  There are several aspects to this: (a) the kernel must
           know about it, (b) the hardware must know about it, (c) user
           programs must know about it, (d) the console font may have to be
           adapted.
    
           (a) The kernel is told about the change using the ioctl VT_RESIZE.
           This causes the kernel to reallocate console screen memory for all
           virtual consoles, and might fail if there is not enough memory.
           (In that case, try to disallocate some virtual consoles first.)
           If this ioctl succeeds, but a later step fails (e.g., because you
           do not have root permissions), you may be left with a very messy
           screen.
    
           The most difficult part of this is (b), since it requires detailed
           knowledge of the video card hardware, and the setting of numerous
           registers. Only changing the number of rows is slightly easier,
           and _resizecons_ will try to do that itself, when given the _-lines_
           option. (Probably, root permission will be required.)  The command
           _resizecons COLSxROWS_ will execute _restoretextmode -r COLSxROWS_
           (and hence requires that you have svgalib installed). Here
           COLSxROWS is a file that was created earlier by _restoretextmode -w_
           _COLSxROWS._  Again, either root permissions are required, or
           _restoretextmode_ has to be suid root.
    
           In order to deal with (c), _resizecons_ does a `stty rows ROWS cols
           COLS' for each active console (in the range tty0..tty15), and
           sends a SIGWINCH signal to _selection_ if it finds the file
           /tmp/selection.pid.
    
           Finally, (d) is dealt with by executing a _setfont_ command. Most
           likely, the wrong font is loaded, and you may want to do another
           _setfont_ yourself afterwards.
    


## BUGS



           _resizecons_ does not work on all hardware.  This command used to be
           called _resize,_ but was renamed to avoid conflict with another
           command with the same name.
    


* * *
# pam_rhosts

## NAME



           pam_rhosts - The rhosts PAM module
    


## SYNOPSIS



    
           **pam_rhosts.so**
    


## DESCRIPTION



           This module performs the standard network authentication for
           services, as used by traditional implementations of **rlogin** and **rsh**
           etc.
    
           The authentication mechanism of this module is based on the
           contents of two files; /etc/hosts.equiv (or and ~/.rhosts.
           Firstly, hosts listed in the former file are treated as equivalent
           to the localhost. Secondly, entries in the user's own copy of the
           latter file is used to map "_remote-host remote-user_ " pairs to that
           user's account on the current host. Access is granted to the user
           if their host is present in /etc/hosts.equiv and their remote
           account is identical to their local one, or if their remote
           account has an entry in their personal configuration file.
    
           The module authenticates a remote user (internally specified by
           the item _PAM_RUSER_ connecting from the remote host (internally
           specified by the item **PAM_RHOST**). Accordingly, for applications to
           be compatible this authentication module they must set these items
           prior to calling **pam_authenticate()**. The module is not capable of
           independently probing the network connection for such information.
    


## OPTIONS



           **debug**
               Print debug information.
    
           **silent**
               Don't print informative messages.
    
           **superuser=**_account_
               Handle _account_ as root.
    


## MODULE TYPES PROVIDED



           Only the **auth** module type is provided.
    


## RETURN VALUES



           PAM_AUTH_ERR
               The remote host, remote user name or the local user name
               couldn't be determined or access was denied by .rhosts file.
    
           PAM_USER_UNKNOWN
               User is not known to system.
    


## EXAMPLES



           To grant a remote user access by /etc/hosts.equiv or .rhosts for
           **rsh** add the following lines to /etc/pam.d/rsh:
    
               #%PAM-1.0
               #
               auth     required       pam_rhosts.so
               auth     required       pam_nologin.so
               auth     required       pam_env.so
               auth     required       pam_unix.so
    


* * *
# hg-ssh

## NAME



           hg-ssh - restricted ssh login shell for Mercurial
    


## SYNOPSIS



           **hg-ssh** repositories...
    


## DESCRIPTION



           **hg-ssh** is a wrapper for ssh access to a limited set of mercurial
           repos.
    
           To be used in ~/.ssh/authorized_keys with the "command" option,
           see sshd(8): command="hg-ssh path/to/repo1 /path/to/repo2 ~/repo3
           ~user/repo4" ssh-dss ...  (probably together with these other
           useful options:
           no-port-forwarding,no-X11-forwarding,no-agent-forwarding)
    
           This allows pull/push over ssh from/to the repositories given as
           arguments.
    
           If all your repositories are subdirectories of a common directory,
           you can allow shorter paths with: command="cd
           path/to/my/repositories && hg-ssh repo1 subdir/repo2"
    
           You can use pattern matching of your normal shell, e.g.:
           command="cd repos && hg-ssh user/thomas/*
           projects/{mercurial,foo}"
    
           You can also add a --read-only flag to allow read-only access to a
           key, e.g.: command="hg-ssh --read-only repos/*"
    


## BUGS



           Probably lots, please post them to the mailing list (see Resources
           below) when you find them.
    


## RESOURCES



           Main Web Site: https://mercurial-scm.org/
    
           Source code repository: https://www.mercurial-scm.org/repo/hg
    
           Mailing list:
           https://www.mercurial-scm.org/mailman/listinfo/mercurial/
    


## COPYING



           Copyright (C) 2005-2016 Olivia Mackall.  Free use of this software
           is granted under the terms of the GNU General Public License
           version 2 or any later version.
    


* * *
# rpm2archive

## NAME



           rpm2archive - Create tar archive from RPM Package Manager (RPM)
           package.
    


## SYNOPSIS



           **rpm2archive {-n|--nocompression} {-f|--format=pax|cpio}**_FILES_
    


## DESCRIPTION



           **rpm2archive** converts the .rpm files specified as arguments to tar
           archives on standard out.
    
           If a '-' argument is given, an rpm stream is read from standard
           in.
    
           If standard out is connected to a terminal, the output is written
           to tar files with a ".tgz" suffix, **gzip**(1) compressed by default.
    
           In opposite to **rpm2cpio rpm2archive** also works with RPM packages
           containing files greater than 4GB which are not supported by **cpio**.
    


## OPTIONS



           **-n, --nocompression**
                  Generate uncompressed tar archive and use ".tar" as postfix
                  of the file name.
    
           **-f, --format=pax|cpio**
                  Generate archive in specified format: **pax**(the default
                  format) or **cpio**.  Note that the cpio format cannot host
                  files over 4GB in size and is only supported here for
                  backwards compatibility.
    


## EXAMPLES



           **rpm2archive glint-1.0-1.i386.rpm | tar -xvz**
           **rpm2archive glint-1.0-1.i386.rpm ; tar -xvz**
           **glint-1.0-1.i386.rpm.tgz**
           **cat glint-1.0-1.i386.rpm | rpm2archive - | tar -tvz**
    


* * *
# systemd-environment-d-generator

## NAME



           systemd-environment-d-generator, 30-systemd-environment-d-
           generator - Load variables specified by environment.d
    


## SYNOPSIS



           /usr/lib/systemd/user-environment-generators/30-systemd-environment-d-generator
    


## DESCRIPTION



           systemd-environment-d-generator is a
           systemd.environment-generator(7) that reads environment
           configuration specified by environment.d(5) configuration files
           and passes it to the systemd(1) user manager instance.
    


* * *
# unix_chkpwd

## NAME



           unix_chkpwd - Helper binary that verifies the password of the
           current user
    


## SYNOPSIS



    
           **unix_chkpwd**[...]
    


## DESCRIPTION



           _unix_chkpwd_ is a helper program for the _pam_unix_ module that
           verifies the password of the current user. It also checks password
           and account expiration dates in _shadow_. It is not intended to be
           run directly from the command line and logs a security violation
           if done so.
    
           It is typically installed setuid root or setgid shadow.
    
           The interface of the helper - command line options, and
           input/output data format are internal to the _pam_unix_ module and
           it should not be called directly from applications.
    


* * *
# btrace

## NAME



           btrace - perform live tracing for block devices
    


## SYNOPSIS



           **btrace [-s] [-t] [-w** _N_] [-n _N_] [-b _N_] [-r _< dbg mnt>_] [-a
           <_trace_ >...] <_dev_ >...
    


## DESCRIPTION



           The _btrace_ script provides a quick and easy way to do live tracing
           of block devices.  It calls _blktrace_ on the specified devices and
           pipes the output through _blkparse_ for formatting.  See blktrace
           (8) for more in-depth information about how _blktrace_ works.
    


## OPTIONS



    
           **-s** Displays data sorted by program (see _blkparse_ (1)).
    
           **-t** Displays time deltas per IO (see _blkparse_ (1)).
    
           **-w** _N_ Sets run time to the number of seconds specified (see
               _blktrace_ (8)).
    
           **-n** _N_ Specifies the number of buffers to use (see _blktrace_ (8)).
    
           **-b** _N_ Specifies buffer size for event extraction (scaled by 1024)
               (see _blktrace_ (8)).
    
           **-r** _< dbg mnt>_ Specifies the debugfs mountpoint.
    
           **-a <**_trace_ >...  Adds mask to current filter (see _blktrace_ (8)).
    
           **<**_dev_ > Specifies the device to trace.
    


## EXAMPLE



           Simply running
    
               % btrace /dev/sda
    
           will show a trace of the device _/dev/sda_.
    


* * *
# tc-cgroup

## NAME



           cgroup - control group based traffic control filter
    


## SYNOPSIS



           **tc filter**... **cgroup**[ **match** _EMATCH_TREE_ ] [ **action** _ACTION_SPEC_ ]
    


## DESCRIPTION



           This filter serves as a hint to **tc** that the assigned class ID of
           the net_cls control group the process the packet originates from
           belongs to should be used for classification. Obviously, it is
           useful for locally generated packets only.
    


## OPTIONS



           **action** _ACTION_SPEC_
                  Apply an action from the generic actions framework on
                  matching packets.
    
           **match** _EMATCH_TREE_
                  Match packets using the extended match infrastructure. See
                  tc-ematch(8) for a detailed description of the allowed
                  syntax in _EMATCH_TREE_.
    


## EXAMPLES



           In order to use this filter, a net_cls control group has to be
           created first and class as well as process ID(s) assigned to it.
           The following creates a net_cls cgroup named "foobar":
    
                  modprobe cls_cgroup
                  mkdir /sys/fs/cgroup/net_cls
                  mount -t cgroup -onet_cls net_cls /sys/fs/cgroup/net_cls
                  mkdir /sys/fs/cgroup/net_cls/foobar
    
           To assign a class ID to the created cgroup, a file named
           _net_cls.classid_ has to be created which contains the class ID to
           be assigned as a hexadecimal, 64bit wide number. The upper 32bits
           are reserved for the major handle, the remaining hold the minor.
           So a class ID of e.g.  **ff:be** has to be written like so: **0xff00be**
           (leading zeroes may be omitted). To continue the above example,
           the following assigns class ID 1:2 to foobar cgroup:
    
                  echo 0x10002 > /sys/fs/cgroup/net_cls/foobar/net_cls.classid
    
           Finally some PIDs can be assigned to the given cgroup:
    
                  echo 1234 > /sys/fs/cgroup/net_cls/foobar/tasks
                  echo 5678 > /sys/fs/cgroup/net_cls/foobar/tasks
    
           Now by simply attaching a **cgroup** filter to a **qdisc** makes packets
           from PIDs 1234 and 5678 be pushed into class 1:2.
    


* * *
# rdma-monitor

## NAME



           rdma-monitor - RDMA events monitoring
    


## SYNOPSIS



           **rdma**[ _OPTIONS_ ] **monitor**{ _help_ }
    
           _OPTIONS_ := { **-V**[_ersion_] }
    
           **rdma monitor**
    
           **rdma monitor help**
    


## DESCRIPTION



       **rdma monitor - utility can monitor RDMA device events on all RDMA**
           **devices.**
           **rdma** opens an RDMA Netlink socket, listens on it and dumps the
           event info.
    
           The event types supported are RDMA device
           registration/unregistration and net device attachment/detachment.
    


## EXAMPLES



           rdma monitor
               Listen for events of all RDMA devices
    


* * *
# xfs_protofile

## NAME



           xfs_protofile - create a protofile for use with mkfs.xfs
    


## SYNOPSIS



           **xfs_protofile** _path_ [ _paths..._  ]
           **xfs_protofile -V**
    


## DESCRIPTION



           **xfs_protofile** walks a directory tree to generate a protofile.  The
           protofile format is specified in the **mkfs.xfs**(8) manual page and
           is derived from 3rd edition Unix.
    


## OPTIONS



           _path_   Create protofile directives to copy this path into the root
                  directory.  If the path is a directory, protofile
                  directives will be emitted to replicate the entire subtree
                  as a subtree of the root directory.  If the path is a not a
                  directory, protofile directives will be emitted to create
                  the file as an entry in the root directory.  The first path
                  must resolve to a directory.
    


## BUGS



           Filenames cannot contain spaces.  Extended attributes are not
           copied into the filesystem.
    


* * *
# xfs_freeze

## NAME



           xfs_freeze - suspend access to an XFS filesystem
    


## SYNOPSIS



           **xfs_freeze**[ **-f** | **-u**] _mount-point_
           **xfs_freeze -V**
    


## DESCRIPTION



           **xfs_freeze** suspends and resumes access to an XFS filesystem (see
           xfs(5)).
    
           **xfs_freeze** halts new access to the filesystem and creates a stable
           image on disk.  **xfs_freeze** is intended to be used with volume
           managers and hardware RAID devices that support the creation of
           snapshots.
    
           The _mount-point_ argument is the pathname of the directory where
           the filesystem is mounted.  The filesystem must be mounted to be
           frozen (see mount(8)).
    
           The **-f** flag requests the specified XFS filesystem to be frozen
           from new modifications.  When this is selected, all ongoing
           transactions in the filesystem are allowed to complete, new write
           system calls are halted, other calls which modify the filesystem
           are halted, and all dirty data, metadata, and log information are
           written to disk.  Any process attempting to write to the frozen
           filesystem will block waiting for the filesystem to be unfrozen.
    
           Note that even after freezing, the on-disk filesystem can contain
           information on files that are still in the process of unlinking.
           These files will not be unlinked until the filesystem is unfrozen
           or a clean mount of the snapshot is complete.
    
           The **-u** flag is used to un-freeze the filesystem and allow
           operations to continue.  Any filesystem modifications that were
           blocked by the freeze are unblocked and allowed to complete.
    
           The **-V** flag prints the version number and exits.
    
           Unless **-V** is specified, one of **-f** or **-u** must be supplied to
           **xfs_freeze**.
    


## NOTES



           A copy of a frozen XFS filesystem will usually have the same
           universally unique identifier (UUID) as the original, and thus may
           be prevented from being mounted.  The XFS **nouuid** mount option can
           be used to circumvent this issue.
    
           In Linux kernel version 2.6.29, the interface which XFS uses to
           freeze and unfreeze was elevated to the VFS, so that this tool can
           now be used on many other Linux filesystems.
    


* * *
# semanage-ibpkey

## NAME



           **semanage-ibpkey - SELinux Policy Management ibpkey mapping tool**
    


## SYNOPSIS



           **semanage ibpkey [-h] [-n] [-N] [-S STORE] [ --add -t TYPE -x**
           **SUBNET_PREFIX -r RANGE ibpkey_name | ibpkey_range | --delete -x**
           **SUBNET_PREFIX ibpkey_name | ibpkey_range | --deleteall | --extract**
           **| --list [-C] | --modify -t TYPE -x SUBNET_PREFIX -r RANGE**
           **ibpkey_name | ibpkey_range ]**
    


## DESCRIPTION



           semanage is used to configure certain elements of SELinux policy
           without requiring modification to or recompilation from policy
           sources.  **semanage ibpkey** controls the ibpkey number to ibpkey
           type definitions.
    


## OPTIONS



           _-h, --help_
                  Show this help message and exit
    
           _-n, --noheading_
                  Do not print heading when listing the specified object type
    
           _-N, --noreload_
                  Do not reload policy after commit
    
           _-S STORE, --store STORE_
                  Select an alternate SELinux Policy Store to manage
    
           _-C, --locallist_
                  List local customizations
    
           _-a, --add_
                  Add a record of the specified object type
    
           _-d, --delete_
                  Delete a record of the specified object type
    
           _-m, --modify_
                  Modify a record of the specified object type
    
           _-l, --list_
                  List records of the specified object type
    
           _-E, --extract_
                  Extract customizable commands, for use within a transaction
    
           _-D, --deleteall_
                  Remove all local customizations
    
           _-t TYPE, --type TYPE_
                  SELinux type for the object
    
           _-r RANGE, --range RANGE_
                  MLS/MCS Security Range (MLS/MCS Systems only) SELinux Range
                  for SELinux login mapping defaults to the SELinux user
                  record range. SELinux Range for SELinux user defaults to
                  s0.
    
           _-x SUBNET_PREFIX, --subnet_prefix SUBNET_PREFIX_
                  Subnet prefix for the specified pkey or range of pkeys.
    


## EXAMPLE



           List all ibpkey definitions
           # semanage ibpkey -l
           Label pkey 0x8FFF (limited membership default pkey) as a default pkey type
           # semanage ibpkey -a -t default_ibpkey_t -x fe80:: 0x8FFF
    


* * *
# pam_securetty

## NAME



           pam_securetty - Limit root login to special devices
    


## SYNOPSIS



    
           **pam_securetty.so**[debug]
    


## DESCRIPTION



           pam_securetty is a PAM module that allows root logins only if the
           user is logging in on a "secure" tty, as defined by the listing in
           the securetty file. pam_securetty checks at first, if
           /etc/securetty exists. If not and it was built with vendordir
           support, it will use /securetty. pam_securetty also checks that
           the securetty files are plain files and not world writable. It
           will also allow root logins on the tty specified with **console=**
           switch on the kernel command line and on ttys from the
           /sys/class/tty/console/active.
    
           This module has no effect on non-root users and requires that the
           application fills in the **PAM_TTY** item correctly.
    
           For canonical usage, should be listed as a **required** authentication
           method before any **sufficient** authentication methods.
    


## OPTIONS



           **debug**
               Print debug information.
    
           **noconsole**
               Do not automatically allow root logins on the kernel console
               device, as specified on the kernel command line or by the sys
               file, if it is not also specified in the securetty file.
    


## MODULE TYPES PROVIDED



           Only the **auth** module type is provided.
    


## RETURN VALUES



           PAM_SUCCESS
               The user is allowed to continue authentication. Either the
               user is not root, or the root user is trying to log in on an
               acceptable device.
    
           PAM_AUTH_ERR
               Authentication is rejected. Either root is attempting to log
               in via an unacceptable device, or the securetty file is world
               writable or not a normal file.
    
           PAM_BUF_ERR
               Memory buffer error.
    
           PAM_CONV_ERR
               The conversation method supplied by the application failed to
               obtain the username.
    
           PAM_INCOMPLETE
               The conversation method supplied by the application returned
               PAM_CONV_AGAIN.
    
           PAM_SERVICE_ERR
               An error occurred while the module was determining the user's
               name or tty, or the module could not open the securetty file.
    
           PAM_USER_UNKNOWN
               The module could not find the user name in the /etc/passwd
               file to verify whether the user had a UID of 0. Therefore, the
               results of running this module are ignored.
    


## EXAMPLES



               auth  required  pam_securetty.so
               auth  required  pam_unix.so
    


* * *
# run_init

## NAME



           run_init - run an init script in the proper SELinux context
    


## SYNOPSIS



           **run_init** _SCRIPT_ [[_ARGS_]...]
    


## DESCRIPTION



           Run a init script under the proper context, which is specified in
           /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.
    


## FILES



           /etc/passwd - user account information
           /etc/shadow - encrypted passwords and age information
           /etc/selinux/POLICYTYPE/contexts/initrc_context - contains the
           context to run init scripts under
    


* * *