tripathysagar/man_text huggingface dataset:
# setpgid

## NAME



           setpgid - run a program in a new process group
    


## SYNOPSIS



           **setpgid**[options] _program_ [_arguments_]
    


## DESCRIPTION



           **setpgid** runs a program in a new process group.
    


## OPTIONS



           **-f** , **--foreground**
               Make the new process group the foreground process group of the
               controlling terminal if there is a controlling terminal.
    
           **-h** , **--help**
               Display help text and exit.
    
           **-V** , **--version**
               Display version and exit.
    


## AVAILABILITY



           The **setpgid** command is part of the util-linux package which can be
           downloaded from Linux Kernel Archive
           <https://www.kernel.org/pub/linux/utils/util-linux/>. This page is
           part of the _util-linux_ (a random collection of Linux utilities)
           project. Information about the project can be found at 
           ⟨https://www.kernel.org/pub/linux/utils/util-linux/⟩. If you have a
           bug report for this manual page, send it to
           util-linux@vger.kernel.org. This page was obtained from the
           project's upstream Git repository
           ⟨git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git⟩ on
           2025-08-11. (At that time, the date of the most recent commit that
           was found in the repository was 2025-08-05.) If you discover any
           rendering problems in this HTML version of the page, or you
           believe there is a better or more up-to-date source for the page,
           or you have corrections or improvements to the information in this
           COLOPHON (which is _not_ part of the original manual page), send a
           mail to man-pages@man7.org
    
    util-linux 2.42-start-521-ec46  2025-08-09                     _SETPGID_(1)
    


* * *
# dh_gencontrol

## NAME



           dh_gencontrol - generate and install control file
    


## SYNOPSIS



           **dh_gencontrol**[_debhelper options_] [**--**_params_]
    


## DESCRIPTION



           **dh_gencontrol** is a debhelper program that is responsible for
           generating control files, and installing them into the _DEBIAN_
           directory with the proper permissions.
    
           This program is merely a wrapper around dpkg-gencontrol(1), which
           calls it once for each package being acted on (plus related dbgsym
           packages), and passes in some additional useful flags.
    
           **Note** that if you use **dh_gencontrol** , you must also use
           dh_builddeb(1) to build the packages.  Otherwise, your build may
           fail to build as **dh_gencontrol**(via dpkg-gencontrol(1)) declares
           which packages are built.  As debhelper automatically generates
           dbgsym packages, it some times adds additional packages, which
           will be built by dh_builddeb(1).
    


## OPTIONS



           **--**_params_
               Pass _params_ to dpkg-gencontrol(1).
    
           **-u** _params_ , **--dpkg-gencontrol-params=**_params_
               This is another way to pass _params_ to dpkg-gencontrol(1).  It
               is deprecated; use **--** instead.
    


* * *
# pmsignal

## NAME



           **pmsignal** - send a signal to one or more processes
    


## SYNOPSIS



           **$PCP_BINADM_DIR/pmsignal**[**-alnp**] [**-s** _signal_] [_PID_ ...|_name_ ...]
    


## DESCRIPTION



           **pmsignal** provides a cross-platform event signalling mechanism for
           use with tools from the Performance Co-Pilot toolkit.  It can be
           used to send a named _signal_ (only HUP, USR1, TERM, and KILL are
           accepted) to one or more processes.
    
           The processes are specified directly using PIDs or as program
           names (with either the **-a** or **-p** options).  In the **all** case, the
           set of all running processes is searched for a basename(1) match
           on _name_.  In the **program** case, process identifiers are extracted
           from files in the $PCP_RUN_DIR directory where file names are
           matched on _name_.pid.
    
           The **-n** option reports the list of process identifiers that would
           have been signalled, but no signals are actually sent.
    
           If a _signal_ is not specified, then the TERM signal will be sent.
           The list of supported signals is reported when using the **-l**
           option.
    
           On Linux and UNIX platforms, _pmsignal_ is a simple wrapper around
           the kill(1) command.  On Windows, the is no direct equivalent to
           this mechanism, and so an alternate mechanism has been implemented
           - this is only honoured by PCP tools, however, not all Windows
           utilities.
    


## OPTIONS



           The available command line options are:
    
           **-a** , **--all**
                Send signal to all named processes.
    
           **-l** , **--list**
                List supported signals.
    
           **-n** , **--dry-run**
                List processes that would be affected.
    
           **-p** , **--program**
                Extract programs from PCP runtime PID files.
    
           **-s** _signal_ , **--signal** =_signal_
                Specify the signal to send, one of: HUP, USR1, TERM, KILL.
    
           **-?** , **--help**
                Display usage message and exit.
    


## PCP ENVIRONMENT



           Environment variables with the prefix **PCP_** are used to
           parameterize the file and directory names used by PCP.  On each
           installation, the file _/etc/pcp.conf_ contains the local values for
           these variables.  The **$PCP_CONF** variable may be used to specify an
           alternative configuration file, as described in pcp.conf(5).
    


* * *
# trace-cmd-stat

## NAME



           trace-cmd-stat - show the status of the tracing (ftrace) system
    


## SYNOPSIS



           **trace-cmd stat**[_OPTIONS_]
    


## DESCRIPTION



           The trace-cmd(1) stat displays the various status of the tracing
           (ftrace) system. The status that it shows is:
    
           **Instances:** List all configured ftrace instances.
    
           **Tracer:** if one of the tracers (like function_graph) is active.
           Otherwise nothing is displayed.
    
           **Events:** Lists the events that are enable.
    
           **Event filters:** Shows any filters that are set for any events
    
           **Function filters:** Shows any filters for the function tracers
    
           **Graph functions:** Shows any functions that the function graph
           tracer should graph
    
           **Buffers:** Shows the trace buffer size if they have been expanded.
           By default, tracing buffers are in a compressed format until they
           are used. If they are compressed, the buffer display will not be
           shown.
    
           **Trace clock:** If the tracing clock is anything other than the
           default "local" it will be displayed.
    
           **Trace CPU mask:** If not all available CPUs are in the tracing CPU
           mask, then the tracing CPU mask will be displayed.
    
           **Trace max latency:** Shows the value of the trace max latency if it
           is other than zero.
    
           **Kprobes:** Shows any kprobes that are defined for tracing.
    
           **Uprobes:** Shows any uprobes that are defined for tracing.
    
           **Error log:** Dump the content of ftrace error_log file.
    


## OPTIONS



           **-B** _buffer-name_
               Display the status of a given buffer instance. May be
               specified more than once to display the status of multiple
               instances.
    
           **-t**
               If **-B** is also specified, show the status of the top level
               tracing directory as well as the instance(s).
    
           **-o**
               Display the all the options along with their values. If they
               start with "no", then the option is disabled.
    


## RESOURCES



           **https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/ **
    


## COPYING



           Copyright (C) 2014 Red Hat, Inc. Free use of this software is
           granted under the terms of the GNU Public License (GPL).
    


## NOTES



            1. rostedt@goodmis.org
               mailto:rostedt@goodmis.org
    


* * *
# repo-graph

## NAME



           repo-graph - output a full package dependency graph in dot format
    


## SYNOPSIS



           **repo-graph**[options]
    


## DESCRIPTION



           **repo-graph** is a program that generates a full package dependency
           list from a yum repository and outputs it in dot format.
    


## OPTIONS



           **-h, --help**
                  Display a help message, and then quit.
    
           **--repoid=REPOID**
                  Specify repo ids to query, can be specified multiple times
                  (default is all enabled).
    
           **-c CONFIG**
                  Config file to use (defaults to /etc/yum.conf).
    


* * *
# mariadbd-safe-helper

## NAME



           mariadbd-safe-helper - helper script (mysqld_safe_helper is now a
           symlink to mariadbd-safe-helper)
    


## DESCRIPTION



           Use: Helper script.
    
           For more information, please refer to the MariaDB Knowledge Base,
           available online at https://mariadb.com/kb/
    


* * *
# stg-name

## NAME



           stg-name - Print patch name of a StGit revision
    


## SYNOPSIS



           _stg name_ [OPTIONS] [revision]
    


## DESCRIPTION



           Print the patch name of a StGit revision.
    
           Try to get the name of the patch in the current branch as
           specified by a StGit revision. Revisions can be specified in the
           all the forms accepted by "stg id" command.
    


## OPTIONS



           -b <branch>, --branch=<branch>
               Use <branch> instead of current branch
    
           --showbranch
               Display the branch name with the patch
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# trace-cmd-check-events

## NAME



           trace-cmd-check-events - parse the event formats on local system
    


## SYNOPSIS



           **trace-cmd check-events**[_OPTIONS_]
    


## DESCRIPTION



           The trace-cmd(1) check-events parses format strings for all the
           events on the local system. It returns whether all the format
           strings can be parsed correctly. It will load plugins unless
           specified otherwise.
    
           This is useful to check for any trace event format strings which
           may contain some internal kernel function references which cannot
           be decoded outside of the kernel. This may mean that either the
           unparsed format strings of the trace events need to be changed or
           that a plugin needs to be created to parse them.
    


## OPTIONS



           **-N** - Don’t load plugins
    
           **--verbose**[=_level_]
               Set the log level. Supported log levels are "none",
               "critical", "error", "warning", "info", "debug", "all" or
               their identifiers "0", "1", "2", "3", "4", "5", "6". Setting
               the log level to specific value enables all logs from that and
               all previous levels. The level will default to "info" if one
               is not specified.
    
                   Example: enable all critical, error and warning logs
    
                   trace-cmd check-events --verbose=warning
    


## RESOURCES



           **https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/ **
    


## COPYING



           Copyright (C) 2011 Google, Inc. Free use of this software is
           granted under the terms of the GNU Public License (GPL).
    


## NOTES



            1. vnagarnaik@google.com
               mailto:vnagarnaik@google.com
    


* * *
# setsid

## NAME



           setsid - run a program in a new session
    


## SYNOPSIS



           **setsid**[options] _program_ [_arguments_]
    


## DESCRIPTION



           **setsid** runs a program in a new session. The command calls fork(2)
           if already a process group leader. Otherwise, it executes a
           program in the current process. This default behavior is possible
           to override by the **--fork** option.
    


## OPTIONS



           **-c** , **--ctty**
               Set the controlling terminal to the current one.
    
           **-f** , **--fork**
               Always create a new process.
    
           **-w** , **--wait**
               Wait for the execution of the program to end, and return the
               exit status of this program as the exit status of **setsid**.
    
           **-h** , **--help**
               Display help text and exit.
    
           **-V** , **--version**
               Display version and exit.
    


## AVAILABILITY



           The **setsid** command is part of the util-linux package which can be
           downloaded from Linux Kernel Archive
           <https://www.kernel.org/pub/linux/utils/util-linux/>. This page is
           part of the _util-linux_ (a random collection of Linux utilities)
           project. Information about the project can be found at 
           ⟨https://www.kernel.org/pub/linux/utils/util-linux/⟩. If you have a
           bug report for this manual page, send it to
           util-linux@vger.kernel.org. This page was obtained from the
           project's upstream Git repository
           ⟨git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git⟩ on
           2025-08-11. (At that time, the date of the most recent commit that
           was found in the repository was 2025-08-05.) If you discover any
           rendering problems in this HTML version of the page, or you
           believe there is a better or more up-to-date source for the page,
           or you have corrections or improvements to the information in this
           COLOPHON (which is _not_ part of the original manual page), send a
           mail to man-pages@man7.org
    
    util-linux 2.42-start-521-ec46  2025-08-09                      _SETSID_(1)
    


* * *
# base32

## NAME



           base32 - base32 encode/decode data and print to standard output
    


## SYNOPSIS



           **base32**[_OPTION_]... [_FILE_]
    


## DESCRIPTION



           Base32 encode or decode FILE, or standard input, to standard
           output.
    
           With no FILE, or when FILE is -, read standard input.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-d** , **--decode**
                  decode data
    
           **-i** , **--ignore-garbage**
                  when decoding, ignore non-alphabet characters
    
           **-w** , **--wrap** =_COLS_
                  wrap encoded lines after COLS character (default 76).  Use
                  0 to disable line wrapping
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           The data are encoded as described for the base32 alphabet in RFC
           4648.  When decoding, the input may contain newlines in addition
           to the bytes of the formal base32 alphabet.  Use **--ignore-garbage**
           to attempt to recover from any other non-alphabet bytes in the
           encoded stream.
    


* * *
# lookbib

## Name



           lookbib - search bibliographic databases interactively
    


## Synopsis



           **lookbib**[**-i** _string_] [**-t** _n_] _file_ ...
    
           **lookbib --help**
    
           **lookbib -v**
    
           **lookbib --version**
    


## Description



           _lookbib_ writes a prompt to the standard error stream (unless the
           standard input stream is not a terminal), reads from the standard
           input a line containing a set of keywords, searches each
           bibliographic database _file_ for references containing those
           keywords, writes any references found to the standard output
           stream, and repeats this process until the end of input.  For each
           database _file_ to be searched, if an index file _.i_ created by
           _indxbib_(1) exists, then it will be searched instead; each index
           can cover multiple databases.
    


## Options



           **--help** displays a usage message, while **-v** and **--version** show
           version information; all exit afterward.
    
           **-i** _string_
                  When searching files for which no index exists, ignore the
                  contents of fields whose names are in _string_.
    
           **-t** _n_   Require only the first _n_ characters of keys to be given.
                  The default is 6.
    


## Exit status



           _lookbib_ exits with status **0** on successful operation, status **2** if
           the program cannot interpret its command-line arguments, and
           status **1** if it encounters an error during operation.
    


## Files



           file _.i_ Index files.
    


## See also



           “Some Applications of Inverted Indexes on the Unix System”, by M.
           E. Lesk, 1978, AT&T Bell Laboratories Computing Science Technical
           Report No. 69.
    
           _refer_(1), _lkbib_(1), _indxbib_(1)
    


* * *
# stg-top

## NAME



           stg-top - Print the name of the top patch
    


## SYNOPSIS



           _stg top_ [OPTIONS]
    


## DESCRIPTION



           Print the name of the top patch.
    
           The topmost patch is the currently applied patch. An error message
           will be printed if no patches are applied.
    


## OPTIONS



           -b <branch>, --branch=<branch>
               Use <branch> instead of current branch
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# split

## NAME



           split - split a file into pieces
    


## SYNOPSIS



           **split**[_OPTION_]... [_FILE_ [_PREFIX_]]
    


## DESCRIPTION



           Output pieces of FILE to PREFIXaa, PREFIXab, ...; default size is
           1000 lines, and default PREFIX is 'x'.
    
           With no FILE, or when FILE is -, read standard input.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-a** , **--suffix-length** =_N_
                  generate suffixes of length N (default 2)
    
           **--additional-suffix** =_SUFFIX_
                  append an additional SUFFIX to file names
    
           **-b** , **--bytes** =_SIZE_
                  put SIZE bytes per output file
    
           **-C** , **--line-bytes** =_SIZE_
                  put at most SIZE bytes of records per output file
    
           **-d** use numeric suffixes starting at 0, not alphabetic
    
           **--numeric-suffixes**[=_FROM_]
                  same as **-d** , but allow setting the start value
    
           **-x** use hex suffixes starting at 0, not alphabetic
    
           **--hex-suffixes**[=_FROM_]
                  same as **-x** , but allow setting the start value
    
           **-e** , **--elide-empty-files**
                  do not generate empty output files with '-n'
    
           **--filter** =_COMMAND_
                  write to shell COMMAND; file name is $FILE
    
           **-l** , **--lines** =_NUMBER_
                  put NUMBER lines/records per output file
    
           **-n** , **--number** =_CHUNKS_
                  generate CHUNKS output files; see explanation below
    
           **-t** , **--separator** =_SEP_
                  use SEP instead of newline as the record separator; '\0'
                  (zero) specifies the NUL character
    
           **-u** , **--unbuffered**
                  immediately copy input to output with '-n r/...'
    
           **--verbose**
                  print a diagnostic just before each output file is opened
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           The SIZE argument is an integer and optional unit (example: 10K is
           10*1024).  Units are K,M,G,T,P,E,Z,Y,R,Q (powers of 1024) or
           KB,MB,... (powers of 1000).  Binary prefixes can be used, too:
           KiB=K, MiB=M, and so on.
    
       **CHUNKS may be:**
           N      split into N files based on size of input
    
           K/N    output Kth of N to stdout
    
           l/N    split into N files without splitting lines/records
    
           l/K/N  output Kth of N to stdout without splitting lines/records
    
           r/N    like 'l' but use round robin distribution
    
           r/K/N  likewise but only output Kth of N to stdout
    


* * *
# sum

## NAME



           sum - checksum and count the blocks in a file
    


## SYNOPSIS



           **sum**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Print or check BSD (16-bit) checksums.
    
           With no FILE, or when FILE is -, read standard input.
    
           **-r** use BSD sum algorithm (the default), use 1K blocks
    
           **-s** , **--sysv**
                  use System V sum algorithm, use 512 bytes blocks
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# pmlogbasename

## NAME



           **pmlogbasename** - basename of a PCP archive
    


## SYNOPSIS



           **pmlogbasename**[**-D** _debug_] _name_
    


## DESCRIPTION



           **pmlogbasename** takes _name_ (usually the name of one of the physical
           files in a PCP archive) and strips it of any compression suffixes
           then strips it of any PCP archive component suffixes, then reports
           the result (the basename of a PCP archive) on standard output.
    
           The compression suffixes known to PCP are: **.xz** , **.lzma** , **.bz2** , **.bz** ,
           **.gz** , **.Z** and **.z**.
    
           The PCP archive component suffixes are: **.meta** , **.index** and **.**_< n>_ for
           any integer _< n>_.
    
           For the most part the stripping is purely textual and is done
           without tests for the existence of any of the associated files,
           although if _name_ does not match the pattern of a valid file name
           for a PCP archive then the output is _name_ without any stripping.
    
           The one exception is when _name_ ends with _.N_ where _N_ is a sequence
           of 1 or more digits, in which case an ambiguity occurs.  For
           example consider _name_ to be **20241125.05.48** , where this could mean
           the archive basename is really **20241125.05.48** or it could mean
           this refers to volume **48** of the archive basename **20241125.05**.  In
           the former case, the file _name_**.meta**(or one of the compressed
           versions of this) should exist and _pmlogbasename_ probes the
           filesystem to determine if such a file exists.
    


## DEBUGGING OPTIONS



           The **-D** or **--debug** option enables the output of additional
           diagnostics on _stderr_ to help triage problems, although the
           information is sometimes cryptic and primarily intended to provide
           guidance for developers rather end-users.  _debug_ is a comma
           separated list of debugging options; use pmdbg(1) with the **-l**
           option to obtain a list of the available debugging options and
           their meaning.
    
           Debugging options specific to **pmlogbasename** are as follows:
           ┌────────┬───────────────────────────────────────────────────────┐
           │ **Option** │ **Description** │
           ├────────┼───────────────────────────────────────────────────────┤
           │ **appl0** │ report the name of each file that exists and          │
           │        │ potentially matches _name_                              │
           ├────────┼───────────────────────────────────────────────────────┤
           │ **appl1** │ report the name of each file that does **not** exist but  │
           │        │ was probed looking for matches with _name_              │
           └────────┴───────────────────────────────────────────────────────┘
    


* * *
# dh_usrlocal

## NAME



           dh_usrlocal - migrate usr/local directories to maintainer scripts
    


## SYNOPSIS



           **dh_usrlocal**[_debhelper options_] [**-n**]
    


## DESCRIPTION



           **dh_usrlocal** is a debhelper program that can be used for building
           packages that will provide a subdirectory in _/usr/local_ when
           installed.
    
           It finds subdirectories of _usr/local_ in the package build
           directory, and removes them, replacing them with maintainer script
           snippets (unless **-n** is used) to create the directories at install
           time, and remove them when the package is removed, in a manner
           compliant with Debian policy. These snippets are inserted into the
           maintainer scripts by **dh_installdeb**. See dh_installdeb(1) for an
           explanation of debhelper maintainer script snippets.
    
           When the _DEB_RULES_REQUIRES_ROOT_ environment variable is not
           (effectively) _binary-targets_ , the directories in _/usr/local_ will
           be handled as if they were owned by root:root (see below).
    
           When the _DEB_RULES_REQUIRES_ROOT_ environment variable has an
           effective value of _binary-targets_ , the owners, groups and
           permissions will be preserved with the sole exception where the
           directory is owned by root:root.
    
           If a directory is owned by root:root, then ownership will be
           determined at install time.  The ownership and permission bits
           will either be root:root mode 0755 or root:staff mode 02775.  The
           actual choice depends on whether the system has
           _/etc/staff-group-for-usr-local_ (as documented in the Debian Policy
           Manual §9.1.2 since version 4.1.4)
    


## OPTIONS



           **-n** , **--no-scripts**
               Do not modify _postinst_ /_prerm_ scripts.
    


## NOTES



           Note that this command is not idempotent. dh_prep(1) should be
           called between invocations of this command. Otherwise, it may
           cause multiple instances of the same text to be added to
           maintainer scripts.
    


## CONFORMS TO



           Debian policy, version 2.2
    


* * *
# galera_new_cluster

## NAME



           galera_new_cluster - starting a new Galera cluster
    


## DESCRIPTION



           Used to bootstrap a new Galera Cluster when all nodes are down.
           Run galera_new_cluster on the first node only.  On the remaining
           nodes simply run 'service @DAEMON_NAME@ start'.
    
           •   **--help** , **-h**
    
               Display a help message and exit.
    


* * *
# git-for-each-repo

## NAME



           git-for-each-repo - Run a Git command on a list of repositories
    


## SYNOPSIS



           _git for-each-repo_ --config=<config> [--] <arguments>
    


## DESCRIPTION



           Run a Git command on a list of repositories. The arguments after
           the known options or **--** indicator are used as the arguments for
           the Git subprocess.
    
           THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.
    
           For example, we could run maintenance on each of a list of
           repositories stored in a **maintenance.repo** config variable using
    
               git for-each-repo --config=maintenance.repo maintenance run
    
           This will run **git -C** _< repo>_ **maintenance run** for each value _< repo>_
           in the multi-valued config variable **maintenance.repo**.
    


## OPTIONS



           --config=<config>
               Use the given config variable as a multi-valued list storing
               absolute path names. Iterate on that list of paths to run the
               given arguments.
    
               These config values are loaded from system, global, and local
               Git config, as available. If **git for-each-repo** is run in a
               directory that is not a Git repository, then only the system
               and global config is used.
    
           --keep-going
               Continue with the remaining repositories if the command failed
               on a repository. The exit code will still indicate that the
               overall operation was not successful.
    
               Note that the exact exit code of the failing command is not
               passed through as the exit code of the **for-each-repo** command:
               If the command failed in any of the specified repositories,
               the overall exit code will be 1.
    


## SUBPROCESS BEHAVIOR



           If any **git -C** _< repo> <arguments>_ subprocess returns a non-zero
           exit code, then the **git for-each-repo** process returns that exit
           code without running more subprocesses.
    
           Each **git -C** _< repo> <arguments>_ subprocess inherits the standard
           file descriptors **stdin** , **stdout** , and **stderr**.
    


## GIT



           Part of the git(1) suite
    


* * *
# stg-init

## NAME



           stg-init - Initialize a StGit stack on a branch
    


## SYNOPSIS



           _stg init_ [OPTIONS]
    


## DESCRIPTION



           Initialize a StGit stack on a branch.
    
           Initializing a branch with a StGit stack commits initial, empty
           stack state for the branch to the repository. Theses stack
           metadata commits are tracked by the **refs/stacks/ <branch>**
           reference. Updated stack state is committed by each StGit command
           that modifies the stack. StGit users do not have to do anything
           with the **refs/stacks/ <branch> **ref directly.
    
           Some StGit commands, such as **stg new** and **stg uncommit** , will
           automatically initialize the stack, so it is often not necessary
           to explicitly initialize the stack on a branch. Also, branches
           created with **stg branch --create** are automatically initialized.
    
           The branch must already exist and point to a commit before
           initializing a StGit stack.
    
           StGit stack metadata can be deinitialized from a branch using **stg**
           **branch --cleanup**. See stg-branch(1) for more details.
    


## OPTIONS



           -b <branch>, --branch=<branch>
               Use <branch> instead of current branch
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# pcp-numastat

## NAME



           **pcp-numastat** - report on NUMA memory allocation
    


## SYNOPSIS



           **pcp**[_pcp options_] **numastat**[**-Vw?**]
    


## DESCRIPTION



           **pcp-numastat** displays NUMA allocation statistics from the kernel
           memory allocator.  Each process has NUMA policies that specify on
           which node pages are allocated.  The performance counters in the
           kernel track on which nodes memory is allocated and these values
           are sampled and reported by **pcp-numastat**.
    
           Counters are maintained individually for each NUMA node.  Details
           of the semantics of each reported metric can be retrieved using
           the following command:
    
                # pminfo ‐dt mem.numa.alloc
    


## OPTIONS



           When invoked via the pcp(1) command, the **-h** /**--host** , **-a** /**--archive** ,
           **-O** /**--origin** , **-Z** /**--timezone** and several other _pcp options_ become
           indirectly available; refer to PCPIntro(1) for a complete
           description of these options.
    
           The additional command line options available for **pcp-numastat**
           are:
    
           **-V** , **--version**
                Display the current version of the command.
    
           **-w** _width_ , **--width** =_width_
                Limit display to _width_.
    
           **-?** , **--help**
                Display usage message and exit.
    


## NOTES



           **pcp-numastat** is inspired by the **numastat**(1) command and produces
           exactly the same output.
    


## PCP ENVIRONMENT



           Environment variables with the prefix **PCP_** are used to
           parameterize the file and directory names used by PCP.  On each
           installation, the file _/etc/pcp.conf_ contains the local values for
           these variables.  The **$PCP_CONF** variable may be used to specify an
           alternative configuration file, as described in pcp.conf(5).
    
           For environment variables affecting PCP tools, see
           pmGetOptions(3).
    


* * *
# stg-export

## NAME



           stg-export - Export patches to a directory
    


## SYNOPSIS



           _stg export_ [OPTIONS] [patch]...
    


## DESCRIPTION



           Export a range of patches to a given directory in unified diff
           format. All applied patches are exported by default.
    
           Patches are exported to _patches- <branch>_ by default. The _--dir_
           option may be used to specify a different output directory.
    
           The patch file output may be customized via a template file found
           at "$GIT_DIR/patchexport.tmpl",
           "~/.stgit/templates/patchexport.tmpl", or
           "$(prefix)/share/stgit/templates". The following variables are
           supported in the template file:
    
               %(description)s - patch description
               %(shortdescr)s  - the first line of the patch description
               %(longdescr)s   - the rest of the patch description, after the first line
               %(diffstat)s    - the diff statistics
               %(authname)s    - author name
               %(authemail)s   - author email
               %(authdate)s    - patch creation date (ISO-8601 format)
               %(commname)s    - committer name
               %(commemail)s   - committer email
    


## OPTIONS



           -b <branch>, --branch=<branch>
               Use <branch> instead of current branch
    
           -d <dir>, --dir=<dir>
               Export patches to <dir> instead of the default
    
           -p, --patch
               Suffix patch file names with ".patch"
    
           -e <ext>, --extension=<ext>
               Suffix patch file names with ".<ext>"
    
           -n, --numbered
               Prefix patch file names with order numbers.
    
           -t <file>, --template=<file>
               Use <file> as template
    
           -s, --stdout
               Export to stdout instead of directory
    
           -O <option>, --diff-opt=<option>
               Pass additional <option> to **git diff**.
    
               See the git-diff(1) man page. This option may be specified
               multiple times.
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# flatpak-remotes

## NAME



           flatpak-remotes - List remote repositories
    


## SYNOPSIS



    
           **flatpak remotes**[OPTION...]
    


## DESCRIPTION



           Lists the known remote repositories, in priority order.
    
           By default, both per-user and system-wide installations are shown.
           Use the **--user** , **--system** or **--installation** options to change this.
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Show help options and exit.
    
           **-u** , **--user**
               Show the per-user configuration.
    
           **--system**
               Show the default system-wide configuration.
    
           **--installation=NAME**
               Show a system-wide installation by NAME among those defined in
               /etc/flatpak/installations.d/. Using **--installation=default** is
               equivalent to using **--system**.
    
           **-d** , **--show-details**
               Show more information for each repository in addition to the
               name. Equivalent to **--columns=all**.
    
           **--show-disabled**
               Show disabled repos.
    
           **-v** , **--verbose**
               Print debug information during command processing.
    
           **--ostree-verbose**
               Print OSTree debug information during command processing.
    
           **--columns=FIELD,...**
               Specify what information to show about each ref. You can list
               multiple fields, or use this option multiple times.
    
               Append :s[tart], :m[iddle], :e[nd] or :f[ull] to column names
               to change ellipsization.
    


## FIELDS



           The following fields are understood by the **--columns** option:
    
           name
               Show the name of the remote
    
           title
               Show the title of the remote
    
           url
               Show the URL of the remote
    
           filter
               Show the path to the client-side filter of the remote.
    
           collection
               Show the collection ID of the remote
    
           priority
               Show the priority of the remote
    
           options
               Show options
    
           comment
               Show comment
    
           description
               Show description
    
           homepage
               Show homepage
    
           icon
               Show icon
    
           all
               Show all columns
    
           help
               Show the list of available columns
    
           Note that field names can be abbreviated to a unique prefix.
    


## EXAMPLES



           **$ flatpak remotes --user --show-details**
    
               testrepo  Test Repository      http://209.132.179.91/repo/ no-gpg-verify
    


* * *
# shift

## PROLOG



           This manual page is part of the POSIX Programmer's Manual.  The
           Linux implementation of this interface may differ (consult the
           corresponding Linux manual page for details of Linux behavior), or
           the interface may not be implemented on Linux.
    


## NAME



           shift — shift positional parameters
    


## SYNOPSIS



           shift **[**_n_**]**
    


## DESCRIPTION



           The positional parameters shall be shifted. Positional parameter 1
           shall be assigned the value of parameter (1+_n_), parameter 2 shall
           be assigned the value of parameter (2+_n_), and so on. The
           parameters represented by the numbers **"$#"** down to **"$#-n+1"** shall
           be unset, and the parameter **'#'** is updated to reflect the new
           number of positional parameters.
    
           The value _n_ shall be an unsigned decimal integer less than or
           equal to the value of the special parameter **'#'**.  If _n_ is not
           given, it shall be assumed to be 1. If _n_ is 0, the positional and
           special parameters are not changed.
    


## OPTIONS



           None.
    


## OPERANDS



           See the DESCRIPTION.
    


## STDIN



           Not used.
    


## INPUT FILES



           None.
    


## ENVIRONMENT VARIABLES



           None.
    


## ASYNCHRONOUS EVENTS



           Default.
    


## STDOUT



           Not used.
    


## STDERR



           The standard error shall be used only for diagnostic messages.
    


## OUTPUT FILES



           None.
    


## EXTENDED DESCRIPTION



           None.
    


## EXIT STATUS



           If the _n_ operand is invalid or is greater than **"$#"** , this may be
           considered a syntax error and a non-interactive shell may exit; if
           the shell does not exit in this case, a non-zero exit status shall
           be returned. Otherwise, zero shall be returned.
    


## CONSEQUENCES OF ERRORS



           Default.
    
           _The following sections are informative._
    


## APPLICATION USAGE



           None.
    


## EXAMPLES



           **$** set a b c d e
           **$** shift 2
           **$** echo $*
           **c d e**
    


## RATIONALE



           None.
    


## FUTURE DIRECTIONS



           None.
    


* * *
# dh_installinitramfs

## NAME



           dh_installinitramfs - install initramfs hooks and setup
           maintscripts
    


## SYNOPSIS



           **dh_installinitramfs**[**debhelper options**] [**-n**]
    


## DESCRIPTION



           **dh_installinitramfs** is a debhelper program that is responsible for
           installing Debian package provided initramfs hooks.
    
           If **dh_installinitramfs** installs or detects one or more initramfs
           hooks in the package, then it also automatically generates the
           noawait trigger **update-initframfs** command needed to interface with
           the Debian initramfs system.  This trigger is inserted into the
           packaging by dh_installdeb(1).
    


## FILES



           debian/_package_.initramfs-hook
               Assumed to be an initramfs hook that will be installed into
               _usr/share/initramfs-tools/hooks/package_ in the package build
               directory. See **HOOK SCRIPTS** in **initramfs-tools**(8) for more
               information about initramfs hooks.
    


## OPTIONS



           **-n** , **--no-scripts**
               Do not add the **update-initramfs** trigger even if it seems like
               the package might need it.  The option is called **--no-scripts**
               for historical reasons as **dh_installinitramfs** would previously
               generate maintainer scripts that called **update-initramfs -u**.
    
               Use this option, if you need to interface with the
               **update-initramfs** system that is not satisfied by the noawait
               trigger (e.g. because you need the extra guarantees and
               head-aches of a await trigger).
    


## NOTES



           Note that this command is not idempotent. dh_prep(1) should be
           called between invocations of this command. Otherwise, it may
           cause multiple instances of the same text to be added to triggers
           file.
    


* * *
# trace-cmd-stack

## NAME



           trace-cmd-stack - read, enable or disable Ftrace Linux kernel
           stack tracing.
    


## SYNOPSIS



           **trace-cmd stack**
    


## DESCRIPTION



           The trace-cmd(1) stack enables the Ftrace stack tracer within the
           kernel. The stack tracer enables the function tracer and at each
           function call within the kernel, the stack is checked. When a new
           maximum usage stack is discovered, it is recorded.
    
           When no option is used, the current stack is displayed.
    
           To enable the stack tracer, use the option **--start** , and to disable
           the stack tracer, use the option **--stop**. The output will be the
           maximum stack found since the start was enabled.
    
           Use **--reset** to reset the stack counter to zero.
    
           User **--verbose**[=_level_] to set the log level. Supported log levels
           are "none", "critical", "error", "warning", "info", "debug", "all"
           or their identifiers "0", "1", "2", "3", "4", "5", "6". Setting
           the log level to specific value enables all logs from that and all
           previous levels. The level will default to "info" if one is not
           specified.
    


## RESOURCES



           **https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/ **
    


## COPYING



           Copyright (C) 2010 Red Hat, Inc. Free use of this software is
           granted under the terms of the GNU Public License (GPL).
    


## NOTES



            1. rostedt@goodmis.org
               mailto:rostedt@goodmis.org
    


* * *
# continue

## PROLOG



           This manual page is part of the POSIX Programmer's Manual.  The
           Linux implementation of this interface may differ (consult the
           corresponding Linux manual page for details of Linux behavior), or
           the interface may not be implemented on Linux.
    


## NAME



           continue — continue for, while, or until loop
    


## SYNOPSIS



           continue **[**_n_**]**
    


## DESCRIPTION



           If _n_ is specified, the _continue_ utility shall return to the top of
           the _n_ th enclosing **for** , **while** , or **until** loop. If _n_ is not
           specified, _continue_ shall behave as if _n_ was specified as 1.
           Returning to the top of the loop involves repeating the condition
           list of a **while** or **until** loop or performing the next assignment of
           a **for** loop, and re-executing the loop if appropriate.
    
           The value of _n_ is a positive decimal integer. If _n_ is greater than
           the number of enclosing loops, the outermost enclosing loop shall
           be used. If there is no enclosing loop, the behavior is
           unspecified.
    
           The meaning of ``enclosing'' shall be as specified in the
           description of the _break_ utility.
    


## OPTIONS



           None.
    


## OPERANDS



           See the DESCRIPTION.
    


## STDIN



           Not used.
    


## INPUT FILES



           None.
    


## ENVIRONMENT VARIABLES



           None.
    


## ASYNCHRONOUS EVENTS



           Default.
    


## STDOUT



           Not used.
    


## STDERR



           The standard error shall be used only for diagnostic messages.
    


## OUTPUT FILES



           None.
    


## EXTENDED DESCRIPTION



           None.
    


## EXIT STATUS



            0    Successful completion.
    
           >0    The _n_ value was not an unsigned decimal integer greater than
                 or equal to 1.
    


## CONSEQUENCES OF ERRORS



           Default.
    
           _The following sections are informative._
    


## APPLICATION USAGE



           None.
    


## EXAMPLES



           for i in *
           do
               if test -d "$i"
               then continue
               fi
               printf '"%s" is not a directory.\n' "$i"
           done
    


## RATIONALE



           None.
    


## FUTURE DIRECTIONS



           None.
    


* * *