mount.glusterfs

title: mount.glusterfs(8)

text:
# mount.glusterfs(8)

## NAME
mount.glusterfs - script to mount native GlusterFS volume

## SYNOPSIS
mount -t glusterfs [-o <options>] <volumeserver>:/<volume>[/<subdir>] <mountpoint>

mount -t glusterfs [-o <options>] <server1>,<server2>,

<server3>,..<serverN>:/<volname>[/<subdir>] <mount_point>

mount -t glusterfs [-o <options>] <path/to/volumefile> <mountpoint>

## DESCRIPTION
This tool is part of glusterfs(8) package, which is used to mount using GlusterFS native binary.

mount.glusterfs is meant to be used by the mount(8) command for mounting native GlusterFS client. This subcommand, however, can also be used as a standalone command with limited functionality.

## OPTIONS

### Basic options
log-file=LOG-FILE

File to use for logging [default:/var/log/glusterfs/glusterfs.log]

log-level=LOG-LEVEL

Logging severity. Valid options are TRACE, DEBUG, WARNING, ERROR, CRITICAL INFO and NONE [default: INFO]

acl

Mount the filesystem with POSIX ACL support

fopen-keep-cache[=BOOL]

Do not purge the cache on file open (default: false)

worm

Mount the filesystem in 'worm' mode

aux-gfid-mount

Enable access to filesystem through gfid directly

ro

Mount the filesystem read-only

enable-ino32=BOOL

Use 32-bit inodes when mounting to workaround broken applications that don't support 64-bit inodes

mem-accounting

Enable internal memory accounting

capability

Enable file capability setting and retrival

thin-client

Enables thin mount and connects via gfproxyd daemon

localtime-logging

Use local timestamps instead of UTC in mount log entries

### Advanced options
attribute-timeout=SECONDS

Set attribute timeout to SECONDS for inodes in fuse kernel module [default: 1]

entry-timeout=SECONDS

Set entry timeout to SECONDS in fuse kernel module [default: 1]

background-qlen=N

Set fuse module's background queue length to N [default: 64]

gid-timeout=SECONDS

Set auxiliary group list timeout to SECONDS for fuse translator [default: 0]

negative-timeout=SECONDS

Set negative timeout to SECONDS in fuse kernel module [default: 0]

volume-name=VOLUME-NAME

Volume name to be used for MOUNT-POINT [default: top most volume in VOLUME-FILE]

direct-io-mode=BOOL|auto

Specify fuse direct I/O strategy [default: auto]

congestion-threshold=N

Set fuse module's congestion threshold to N [default: 48]

ubdir-mount=N

Set the subdirectory mount option [default: NULL, ie, no subdirectory mount]

backup-volfile-servers=SERVERLIST

Provide list of backup volfile servers in the following format [default: None] If use IPv6 address in SERVERLIST, it is required to use '[' and ']' to surround IPv6 address. $ mount -t glusterfs -obackup-volfile-servers=<server2>: <server3>:...:<serverN> <server1>:/<volname> <mount_point> $ mount -t glusterfs -obackup-volfile-servers=<[ipv6_addr2]>: <[ipv6_addr3]>:...:<[ipv6_addrN]> <ipv6_addr1>:/<volname> <mount_point>

backupvolfile-server=SERVER

Provide list of backup volfile servers in the following format [default: None] $ mount -t glusterfs -obackupvolfile-server=<server2> <server1>:/<volname> <mount_point>

fetch-attempts=N

Deprecated option - placed here for backward compatibility [default: 1]

lru-limit=N

Set fuse module's limit for number of inodes kept in LRU list to N [default: 65536]

invalidate-limit=N

Suspend fuse invalidations implied by 'lru-limit' if number of outstanding invalidations reaches N

background-qlen=N

Set fuse module's background queue length to N [default: 64]

no-root-squash=BOOL

disable root squashing for the trusted client [default: off]

root-squash=BOOL

enable root squashing for the trusted client [default: on]

use-readdirp=BOOL

Use readdirp() mode in fuse kernel module [default: on]

dump-fuse=PATH

Dump fuse traffic to PATH

kernel-writeback-cache=BOOL

Enable fuse in-kernel writeback cache [default: off]

attr-times-granularity=NS

Declare supported granularity of file attribute [default: 0]

auto-invalidation=BOOL

controls whether fuse-kernel can auto-invalidate attribute, dentry and page-cache. Disable this only if same files/directories are not accessed across two different mounts concurrently [default: on]

## FILES
/etc/fstab

A typical GlusterFS entry in /etc/fstab looks like below server1:/mirror /mnt/mirror glusterfs log-file=/var/log/mirror.log,acl 0 0

/proc/mounts

An example entry of a GlusterFS mountpoint in /proc/mounts looks like below server1:/mirror /mnt/glusterfs fuse.glusterfs rw,allow_other,default_permissions,max_read=131072 0 0

## SEE ALSO
glusterfs(8), mount(8), gluster(8)

## COPYRIGHT
Copyright(c) 2006-2013 Red Hat, Inc. <http://www.redhat.com>


glusterd

title: glusterd(8)

text:
# glusterd(8)

## NAME
Glusterd - Gluster elastic volume management daemon

## SYNOPSIS
glusterd [OPTION...]

## DESCRIPTION
The glusterd daemon is used for elastic volume management. The daemon must be run on all export servers.

## OPTIONS

### Basic options
-l <LOGFILE>, --log-file=<LOGFILE>

File to use for logging.

-L <LOGLEVEL>, --log-level=<LOGLEVEL>

Logging severity. Valid options are TRACE, DEBUG, INFO, WARNING, ERROR and CRITICAL (the default is INFO).

--localtime-logging

Enable localtime log timestamps.

--debug

Run the program in debug mode. This option sets --no-daemon, --log-level to DEBUG and --log-file to console.

-N, --no-daemon

Run the program in the foreground.

### Miscellaneous Options:
-?, --help

Display this help.

--usage

Display a short usage message.

-V, --version

Print the program version.

## FILES
/var/lib/glusterd/*

## SEE ALSO

```
fusermount(1), mount.glusterfs(8), glusterfs(8), gluster(8)
```

## COPYRIGHT

```
Copyright(c) 2006-2011  Gluster, Inc.  <http://www.gluster.com>
```


title: gluster-setgfid2path(8)

text:
# gluster-setgfid2path(8)

## NAME
gluster-setgfid2path - Gluster tool to set GFID to Path xattrs

## SYNOPSIS
gluster-setgfid2path file

## DESCRIPTION
New feature introduced with Gluster release 3.12, to find full path from GFID. This feature can be enabled using Volume set command gluster volume set <VOLUME> storage.gfid2path enable

Once gfid2path feature is enabled, it starts recording the necessary xattrs required for the feature. But it will not add xattrs for the already existing files. This tool provides facility to update the gfid2path xattrs for the given file path.

## EXAMPLES
To add xattrs of a single file,

```
gluster-setgfid2path /bricks/b1/hello.txt
```

```

```

To set xattr for all the existing files, run the below script on each bricks.

```
BRICK=/bricks/b1
find $BRICK -type d \( -path "${BRICK}/.trashcan" -o -path \

    "${BRICK}/.glusterfs" \) -prune -o -type f \

    -exec gluster-setgfid2path {} \;
```

```

```

## SEE ALSO

```
gluster(8)
```

## COPYRIGHT

```
Copyright(c) 2017   Red Hat, Inc.   <http://www.redhat.com>
```


gluster

title: gluster(8)

text:
# gluster(8)

## NAME
gluster - Gluster Console Manager (command line utility)

## SYNOPSIS
gluster

To run the program and display gluster prompt:

gluster [--remote-host=<gluster_node>] [--mode=script] [--xml]

(or)

To specify a command directly:

gluster [commands] [options] [--remote-host=<gluster_node>] [--mode=script] [--xml]

## DESCRIPTION
The Gluster Console Manager is a command line utility for elastic volume management. You can run the gluster command on any export server. The command enables administrators to perform cloud operations, such as creating, expanding, shrinking, rebalancing, and migrating volumes without needing to schedule server downtime.

## COMMANDS

### Volume Commands
volume info [all|<VOLNAME>]

Display information about all volumes, or the specified volume.

volume list

List all volumes in cluster

volume status [all | <VOLNAME> [nfs|shd|<BRICK>|quotad]] [detail|clients|mem|inode|fd|callpool|tasks|client-list]

Display status of all or specified volume(s)/brick

volume create <NEW-VOLNAME> [stripe <COUNT>] [[replica <COUNT> [arbiter <COUNT>]]|[replica 2 thin-arbiter 1]] [disperse [<COUNT>]] [disperse-data <COUNT>] [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK> ... <TA-BRICK>

Create a new volume of the specified type using the specified bricks and transport type (the default transport type is tcp). To create a volume with both transports (tcp and rdma), give 'transport tcp,rdma' as an option.

volume delete <VOLNAME>

Delete the specified volume.

volume start <VOLNAME>

Start the specified volume.

volume stop <VOLNAME> [force]

Stop the specified volume.

volume set <VOLNAME> <OPTION> <PARAMETER> [<OPTION> <PARAMETER>] ...

Set the volume options.

volume get <VOLNAME/all> <OPTION/all>

Get the value of the all options or given option for volume <VOLNAME> or all option. gluster volume get all all is to get all global options

volume reset <VOLNAME> [option] [force]

Reset all the reconfigured options

volume barrier <VOLNAME> {enable|disable}

Barrier/unbarrier file operations on a volume

volume clear-locks <VOLNAME> <path> kind {blocked|granted|all}{inode [range]|entry [basename]|posix [range]}

Clear locks held on path

volume help

Display help for the volume command.

### Brick Commands
volume add-brick <VOLNAME> <NEW-BRICK> ...

Add the specified brick to the specified volume.

volume remove-brick <VOLNAME> <BRICK> ...

Remove the specified brick from the specified volume.

Note: If you remove the brick, the data stored in that brick will not be available. You can migrate data from one brick to another using replace-brick option.

volume reset-brick <VOLNAME> <SOURCE-BRICK> {{start} | {<NEW-BRICK> commit}}

Brings down or replaces the specified source brick with the new brick.

volume replace-brick <VOLNAME> <SOURCE-BRICK> <NEW-BRICK> commit force

Replace the specified source brick with a new brick.

volume rebalance <VOLNAME> start

Start rebalancing the specified volume.

volume rebalance <VOLNAME> stop

Stop rebalancing the specified volume.

volume rebalance <VOLNAME> status

Display the rebalance status of the specified volume.

### Log Commands
volume log <VOLNAME> rotate [BRICK]

Rotate the log file for corresponding volume/brick.

volume profile <VOLNAME> {start|info [peek|incremental [peek]|cumulative|clear]|stop} [nfs]

Profile operations on the volume. Once started, volume profile <volname> info provides cumulative statistics of the FOPs performed.

volume top <VOLNAME> {open|read|write|opendir|readdir|clear} [nfs|brick <brick>] [list-cnt <value>] | {read-perf|write-perf} [bs <size> count <count>] [brick <brick>] [list-cnt <value>]

Generates a profile of a volume representing the performance and bottlenecks/hotspots of each brick.

volume statedump <VOLNAME> [[nfs|quotad] [all|mem|iobuf|callpool|priv|fd|inode|history]... | [client <hostname:process-id>]]

Dumps the in memory state of the specified process or the bricks of the volume.

volume sync <HOSTNAME> [all|<VOLNAME>]

Sync the volume information from a peer

### Peer Commands
peer probe <HOSTNAME>

Probe the specified peer. In case the <HOSTNAME> given belongs to an already probed peer, the peer probe command will add the hostname to the peer if required.

peer detach <HOSTNAME>

Detach the specified peer.

peer status

Display the status of peers.

pool list

List all the nodes in the pool (including localhost)

peer help

Display help for the peer command.

### Quota Commands
volume quota <VOLNAME> enable

Enable quota on the specified volume. This will cause all the directories in the filesystem hierarchy to be accounted and updated thereafter on each operation in the the filesystem. To kick start this accounting, a crawl is done over the hierarchy with an auxiliary client.

volume quota <VOLNAME> disable

Disable quota on the volume. This will disable enforcement and accounting in the filesystem. Any configured limits will be lost.

volume quota <VOLNAME> limit-usage <PATH> <SIZE> [<PERCENT>]

Set a usage limit on the given path. Any previously set limit is overridden to the new value. The soft limit can optionally be specified (as a percentage of hard limit). If soft limit percentage is not provided the default soft limit value for the volume is used to decide the soft limit.

volume quota <VOLNAME> limit-objects <PATH> <SIZE> [<PERCENT>]

Set an inode limit on the given path. Any previously set limit is overridden to the new value. The soft limit can optionally be specified (as a percentage of hard limit). If soft limit percentage is not provided the default soft limit value for the volume is used to decide the soft limit.

NOTE: valid units of SIZE are : B, KB, MB, GB, TB, PB. If no unit is specified, the unit defaults to bytes.

volume quota <VOLNAME> remove <PATH>

Remove any usage limit configured on the specified directory. Note that if any limit is configured on the ancestors of this directory (previous directories along the path), they will still be honored and enforced.

volume quota <VOLNAME> remove-objects <PATH>

Remove any inode limit configured on the specified directory. Note that if any limit is configured on the ancestors of this directory (previous directories along the path), they will still be honored and enforced.

volume quota <VOLNAME> list <PATH>

Lists the usage and limits configured on directory(s). If a path is given only the limit that has been configured on the directory(if any) is displayed along with the directory's usage. If no path is given, usage and limits are displayed for all directories that has limits configured.

volume quota <VOLNAME> list-objects <PATH>

Lists the inode usage and inode limits configured on directory(s). If a path is given only the limit that has been configured on the directory(if any) is displayed along with the directory's inode usage. If no path is given, usage and limits are displayed for all directories that has limits configured.

volume quota <VOLNAME> default-soft-limit <PERCENT>

Set the percentage value for default soft limit for the volume.

volume quota <VOLNAME> soft-timeout <TIME>

Set the soft timeout for the volume. The interval in which limits are retested before the soft limit is breached.

volume quota <VOLNAME> hard-timeout <TIME>

Set the hard timeout for the volume. The interval in which limits are retested after the soft limit is breached.

volume quota <VOLNAME> alert-time <TIME>

Set the frequency in which warning messages need to be logged (in the brick logs) once soft limit is breached.

volume inode-quota <VOLNAME> enable/disable

Enable/disable inode-quota for <VOLNAME>

volume quota help

Display help for volume quota commands

NOTE: valid units of time and their symbols are : hours(h/hr), minutes(m/min), seconds(s/sec), weeks(w/wk), Days(d/days).

### Geo-replication Commands
Note: password-less ssh, from the primary node (where these commands are executed) to the secondary node <SECONDARY_HOST>, is a prerequisite for the geo-replication commands.

system:: execute gsec_create

Generates pem keys which are required for push-pem

volume geo-replication <PRIMARY_VOL> <SECONDARY_HOST>::<SECONDARY_VOL> create [[ssh-port n][[no-verify]|[push-pem]]] [force]

Create a new geo-replication session from <PRIMARY_VOL> to <SECONDARY_HOST> host machine having <SECONDARY_VOL>. Use ssh-port n if custom SSH port is configured in secondary nodes. Use no-verify if the rsa-keys of nodes in primary volume is distributed to secondary nodes through an external agent. Use push-pem to push the keys automatically.

volume geo-replication <PRIMARY_VOL> <SECONDARY_HOST>::<SECONDARY_VOL> {start|stop} [force]

Start/stop the geo-replication session from <PRIMARY_VOL> to <SECONDARY_HOST> host machine having <SECONDARY_VOL>.

volume geo-replication [<PRIMARY_VOL> [<SECONDARY_HOST>::<SECONDARY_VOL>]] status [detail]

Query status of the geo-replication session from <PRIMARY_VOL> to <SECONDARY_HOST> host machine having <SECONDARY_VOL>.

volume geo-replication <PRIMARY_VOL> <SECONDARY_HOST>::<SECONDARY_VOL> {pause|resume} [force]

Pause/resume the geo-replication session from <PRIMARY_VOL> to <SECONDARY_HOST> host machine having <SECONDARY_VOL>.

volume geo-replication <PRIMARY_VOL> <SECONDARY_HOST>::<SECONDARY_VOL> delete [reset-sync-time]

Delete the geo-replication session from <PRIMARY_VOL> to <SECONDARY_HOST> host machine having <SECONDARY_VOL>. Optionally you can also reset the sync time in case you need to resync the entire volume on session recreate.

volume geo-replication <PRIMARY_VOL> <SECONDARY_HOST>::<SECONDARY_VOL> config [[!]<options> [<value>]]

View (when no option provided) or set configuration for this geo-replication session. Use "!<OPTION>" to reset option <OPTION> to default value.

### Bitrot Commands
volume bitrot <VOLNAME> {enable|disable}

Enable/disable bitrot for volume <VOLNAME>

volume bitrot <VOLNAME> signing-time <time-in-secs>

Waiting time for an object after last fd is closed to start signing process.

volume bitrot <VOLNAME> signer-threads <count>

Number of signing process threads. Usually set to number of available cores.

volume bitrot <VOLNAME> scrub-throttle {lazy|normal|aggressive}

Scrub-throttle value is a measure of how fast or slow the scrubber scrubs the filesystem for volume <VOLNAME>

volume bitrot <VOLNAME> scrub-frequency {hourly|daily|weekly|biweekly|monthly}

Scrub frequency for volume <VOLNAME>

volume bitrot <VOLNAME> scrub {pause|resume|status|ondemand}

Pause/Resume scrub. Upon resume, scrubber continues where it left off. status option shows the statistics of scrubber. ondemand option starts the scrubbing immediately if the scrubber is not paused or already running.

volume bitrot help

Display help for volume bitrot commands

### Snapshot Commands
snapshot create <snapname> <volname> [no-timestamp] [description <description>] [force]

Creates a snapshot of a GlusterFS volume. User can provide a snap-name and a description to identify the snap. Snap will be created by appending timestamp in GMT. User can override this behaviour using "no-timestamp" option. The description cannot be more than 1024 characters. To be able to take a snapshot, volume should be present and it should be in started state.

snapshot restore <snapname>

Restores an already taken snapshot of a GlusterFS volume. Snapshot restore is an offline activity therefore if the volume is online (in started state) then the restore operation will fail. Once the snapshot is restored it will not be available in the list of snapshots.

snapshot clone <clonename> <snapname>

Create a clone of a snapshot volume, the resulting volume will be GlusterFS volume. User can provide a clone-name. To be able to take a clone, snapshot should be present and it should be in activated state.

snapshot delete ( all | <snapname> | volume <volname> )

If snapname is specified then mentioned snapshot is deleted. If volname is specified then all snapshots belonging to that particular volume is deleted. If keyword *all* is used then all snapshots belonging to the system is deleted.

snapshot list [volname]

Lists all snapshots taken. If volname is provided, then only the snapshots belonging to that particular volume is listed.

snapshot info [snapname | (volume <volname>)]

This command gives information such as snapshot name, snapshot UUID, time at which snapshot was created, and it lists down the snap-volume-name, number of snapshots already taken and number of snapshots still available for that particular volume, and the state of the snapshot. If snapname is specified then info of the mentioned snapshot is displayed. If volname is specified then info of all snapshots belonging to that volume is displayed. If both snapname and volname is not specified then info of all the snapshots present in the system are displayed.

snapshot status [snapname | (volume <volname>)]

This command gives status of the snapshot. The details included are snapshot brick path, volume group(LVM details), status of the snapshot bricks, PID of the bricks, data percentage filled for that particular volume group to which the snapshots belong to, and total size of the logical volume. If snapname is specified then status of the mentioned snapshot is displayed. If volname is specified then status of all snapshots belonging to that volume is displayed. If both snapname and volname is not specified then status of all the snapshots present in the system are displayed.

snapshot config [volname] ([snap-max-hard-limit <count>] [snap-max-soft-limit <percent>]) | ([auto-delete <enable|disable>]) | ([activate-on-create <enable|disable>])

Displays and sets the snapshot config values. snapshot config without any keywords displays the snapshot config values of all volumes in the system. If volname is provided, then the snapshot config values of that volume is displayed.

Snapshot config command along with keywords can be used to change the existing config values. If volname is provided then config value of that volume is changed, else it will set/change the system limit.

snap-max-soft-limit and auto-delete are global options, that will be inherited by all volumes in the system and cannot be set to individual volumes.

snap-max-hard-limit can be set globally, as well as per volume. The lowest limit between the global system limit and the volume specific limit, becomes the "Effective snap-max-hard-limit" for a volume.

snap-max-soft-limit is a percentage value, which is applied on the "Effective snap-max-hard-limit" to get the "Effective snap-max-soft-limit".

When auto-delete feature is enabled, then upon reaching the "Effective snap-max-soft-limit", with every successful snapshot creation, the oldest snapshot will be deleted.

When auto-delete feature is disabled, then upon reaching the "Effective snap-max-soft-limit", the user gets a warning with every successful snapshot creation.

When auto-delete feature is disabled, then upon reaching the "Effective snap-max-hard-limit", further snapshot creations will not be allowed.

activate-on-create is disabled by default. If you enable activate-on-create, then further snapshot will be activated during the time of snapshot creation.

snapshot activate <snapname>

Activates the mentioned snapshot. Note : By default the snapshot is activated during snapshot creation.

snapshot deactivate <snapname>

Deactivates the mentioned snapshot.

snapshot help

Display help for the snapshot commands.

### Self-heal Commands
volume heal <VOLNAME>

Triggers index self heal for the files that need healing.

volume heal <VOLNAME> [enable | disable]

Enable/disable self-heal-daemon for volume <VOLNAME>.

volume heal <VOLNAME> full

Triggers self heal on all the files.

volume heal <VOLNAME> info

Lists the files that need healing.

volume heal <VOLNAME> info split-brain

Lists the files which are in split-brain state.

volume heal <VOLNAME> statistics

Lists the crawl statistics.

volume heal <VOLNAME> statistics heal-count

Displays the count of files to be healed.

volume heal <VOLNAME> statistics heal-count replica <HOSTNAME:BRICKNAME>

Displays the number of files to be healed from a particular replica subvolume to which the brick <HOSTNAME:BRICKNAME> belongs.

volume heal <VOLNAME> split-brain bigger-file <FILE>

Performs healing of <FILE> which is in split-brain by choosing the bigger file in the replica as source.

volume heal <VOLNAME> split-brain source-brick <HOSTNAME:BRICKNAME>

Selects <HOSTNAME:BRICKNAME> as the source for all the files that are in split-brain in that replica and heals them.

volume heal <VOLNAME> split-brain source-brick <HOSTNAME:BRICKNAME> <FILE>

Selects the split-brained <FILE> present in <HOSTNAME:BRICKNAME> as source and completes heal.

### Other Commands
get-state [<daemon>] [[odir </path/to/output/dir/>] [file <filename>]] [detail|volumeoptions]

Get local state representation of mentioned daemon and store data in provided path information

help

Display the command options.

quit

Exit the gluster command line interface.

## FILES
/var/lib/glusterd/*

## SEE ALSO

```
fusermount(1), mount.glusterfs(8), glusterfs(8), glusterd(8)
```

## COPYRIGHT

```
Copyright(c) 2006-2011  Gluster, Inc.  <http://www.gluster.com>
```


glusterfs

title: glusterfs(8)

summary: clustered file system

text:
# glusterfs(8)

## NAME
GlusterFS - clustered file system

## SYNOPSIS
glusterfs [options] [mountpoint]

## DESCRIPTION
GlusterFS is a clustered file system, capable of scaling to several peta-bytes. It aggregates various storage bricks over Infiniband RDMA or TCP/IP and interconnect into one large parallel network file system. Storage bricks can be made of any commodity hardware, such as x86-64 server with SATA-II RAID and Infiniband HBA.

GlusterFS is fully POSIX compliant file system. On client side, it has dependency on FUSE package, on server side, it works seemlessly on different operating systems. Currently supported on GNU/Linux and Solaris.

## OPTIONS

### Basic options
-f, --volfile=VOLUME-FILE

File to use as VOLUME-FILE.

-l, --log-file=LOGFILE

File to use for logging (the default is <INSTALL-DIR>/var/log/glusterfs/<MOUNT-POINT>.log).

-L, --log-level=LOGLEVEL

Logging severity. Valid options are TRACE, DEBUG, INFO, WARNING, ERROR and CRITICAL (the default is INFO).

-s, --volfile-server=SERVER

Server to get the volume from. This option overrides --volfile option.

--volfile-max-fetch-attempts=MAX-ATTEMPTS

Maximum number of connect attempts to server. This option should be provided with --volfile-server option (the default is 1).

### Advanced options
--acl

Mount the filesystem with POSIX ACL support.

--localtime-logging

Enable localtime log timestamps.

--debug

Run in debug mode. This option sets --no-daemon, --log-level to DEBUG, and --log-file to console.

--enable-ino32=BOOL

Use 32-bit inodes when mounting to workaround application that doesn't support 64-bit inodes.

--fopen-keep-cache[=BOOL]

Do not purge the cache on file open (default: false).

--mac-compat=BOOL

Provide stubs for attributes needed for seamless operation on Macs (the default is off).

-N, --no-daemon

Run in the foreground.

-p, --pid-file=PIDFILE

File to use as PID file.

--read-only

Mount the file system in 'read-only' mode.

--selinux

Enable SELinux label (extended attributes) support on inodes.

-S, --socket-file=SOCKFILE

File to use as unix-socket.

--volfile-id=KEY

Key of the volume file to be fetched from the server.

--volfile-server-port=PORT

Port number of volfile server.

--volfile-server-transport=TRANSPORT

Transport type to get volume file from server (the default is tcp).

--volume-name=VOLUME-NAME

Volume name to be used for MOUNT-POINT (the default is top most volume in VOLUME-FILE).

--worm

Mount the filesystem in 'worm' mode.

--xlator-option=VOLUME-NAME.OPTION=VALUE

Add/Override a translator option for a volume with the specified value.

--subdir-mount=SUBDIR-MOUNT-PATH

Mount subdirectory instead of the '/' of volume.

### Fuse options
--attr-times-granularity=NANOSECONDS

Declare supported granularity of file attribute times (default is 0 which kernel handles as unspecified; valid real values are between 1 and 1000000000).

--attribute-timeout=SECONDS

Set attribute timeout to SECONDS for inodes in fuse kernel module (the default is 1).

--background-qlen=N

Set fuse module's background queue length to N (the default is 64).

--congestion-threshold=N

Set fuse module's congestion threshold to N (the default is 48).

--direct-io-mode=BOOL|auto

Specify fuse direct I/O strategy (the default is auto).

--dump-fuse=PATH

Dump fuse traffic to PATH

--entry-timeout=SECONDS

Set entry timeout to SECONDS in fuse kernel module (the default is 1).

--gid-timeout=SECONDS

Set auxiliary group list timeout to SECONDS for fuse translator (the default is 0).

--kernel-writeback-cache=BOOL

Enable fuse in-kernel writeback cache.

--negative-timeout=SECONDS

Set negative timeout to SECONDS in fuse kernel module (the default is 0).

--auto-invalidation=BOOL

controls whether fuse-kernel can auto-invalidate attribute, dentry and page-cache. Disable this only if same files/directories are not accessed across two different mounts concurrently [default: on].

--volfile-check

Enable strict volume file checking.

### Miscellaneous Options
-?, --help

Display this help.

--usage

Display a short usage message.

-V, --version

Print the program version.

## FILES
/var/lib/glusterd/vols/*/*.vol

## EXAMPLES
mount a volume named foo on server bar with log level DEBUG on mount point /mnt/foo

\# glusterfs --log-level=DEBUG --volfile-id=foo --volfile-server=bar /mnt/foo

## SEE ALSO

```
fusermount(1), mount.glusterfs(8), gluster(8)
```

## COPYRIGHT

```
Copyright(c) 2006-2011  Red Hat, Inc.  <http://www.redhat.com>
```


glusterfsd

title: glusterfsd(8)

summary: Clustered Filesystem.

text:
# glusterfsd(8)

## NAME
GlusterFS - Clustered Filesystem.

## SYNOPSIS
glusterfsd [options] [mountpoint]

## DESCRIPTION
GlusterFS is a clustered file-system capable of scaling to several peta-bytes. It aggregates various storage bricks over Infiniband RDMA or TCP/IP interconnect into one large parallel network file system. Storage bricks can be made of any commodity hardware such as x86-64 server with SATA-II RAID and Infiniband HBA.

GlusterFS is fully POSIX compliant FileSystem. On client side, it has dependency on FUSE package, on server side, it works seemlessly on different OSes. (Currently supported on GNU/Linux, Solaris).

## OPTIONS
Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options.

### Basic options
-f, --volfile=VOLUME-FILE

File to use as VOLUME-FILE [default:/etc/glusterfs/glusterfs.vol]

-l, --log-file=LOGFILE

File to use for logging [default:/var/log/glusterfs/glusterfs.log]

-L, --log-level=LOGLEVEL

Logging severity. Valid options are TRACE, DEBUG, INFO, WARNING, ERROR and CRITICAL [default: WARNING]

-s, --volfile-server=SERVER

Server to get the volume from. This option overrides --volfile option

### Advanced options
--localtime-logging

Enable localtime log timestamps.

--debug

Run in debug mode. This option sets --no-daemon, --log-level to DEBUG and --log-file to console

-N, --no-daemon

Run in foreground

--read-only

Makes the filesystem read-only

-p, --pid-file=PIDFILE

File to use as pid file

-S SOCKFILE

Socket file to used for inter-process communication

--brick-name DIRECTORY

Directory to be used as export directory for GlusterFS

--brick-port PORT

Brick Port to be registered with Gluster portmapper

--volfile-id=KEY

KEY of the volume file to be fetched from server

--volfile-server-port=PORT

Port number of volfile server

--volfile-server-transport=TRANSPORT

Transport type to get volume file from server [default: tcp]

--volume-name=VOLUME-NAME

Volume name to be used for MOUNT-POINT [default: top most volume in VOLUME-FILE]

--xlator-option=VOLUME-NAME.OPTION=VALUE

Add/override a translator option for a volume with the specified value

### Fuse options
--attribute-timeout=SECONDS

Set attribute timeout to SECONDS for inodes in fuse kernel module [default: 1]

--entry-timeout=SECONDS

Set entry timeout to SECONDS in fuse kernel module [default: 1]

--direct-io-mode=BOOL

Enable/Disable direct-io mode in fuse module [default: enable]

--resolve-gids

Resolve all auxiliary groups in fuse translator (max 32 otherwise)

--auto-invalidation=BOOL

controls whether fuse-kernel can auto-invalidate attribute, dentry and page-cache. Disable this only if same files/directories are not accessed across two different mounts concurrently [default: on]

### Miscellaneous Options
-?, --help

Give this help list

--usage

Give a short usage message

-V, --version

Print program version

## FILES
/etc/glusterfs/*.vol

## EXAMPLES
Start a GlusterFS server on localhost with volume name foo

glusterfsd -s localhost --volfile-id foo.server.media-disk-1 -p /var/lib/glusterd/vols/foo/run/server-media-disk-1.pid -S /tmp/<uniqueid>.socket --brick-name /media/disk-1 -l /var/log/glusterfs/bricks/media-disk-1.log --brick-port 24009 --xlator-option foo-server.listen-port=24009

## SEE ALSO

```
fusermount(1), mount.glusterfs(8), gluster(8)
```

## COPYRIGHT

```
Copyright(c) 2006-2011  Gluster, Inc.  <http://www.gluster.com>
```


mount.glusterfs

title: mount.glusterfs(8)

text:
# mount.glusterfs(8)

## NAME
mount.glusterfs - script to mount native GlusterFS volume

## SYNOPSIS
mount -t glusterfs [-o <options>] <volumeserver>:/<volume>[/<subdir>] <mountpoint>

mount -t glusterfs [-o <options>] <server1>,<server2>,

<server3>,..<serverN>:/<volname>[/<subdir>] <mount_point>

mount -t glusterfs [-o <options>] <path/to/volumefile> <mountpoint>

## DESCRIPTION
This tool is part of glusterfs(8) package, which is used to mount using GlusterFS native binary.

mount.glusterfs is meant to be used by the mount(8) command for mounting native GlusterFS client. This subcommand, however, can also be used as a standalone command with limited functionality.

## OPTIONS

### Basic options
log-file=LOG-FILE

File to use for logging [default:/var/log/glusterfs/glusterfs.log]

log-level=LOG-LEVEL

Logging severity. Valid options are TRACE, DEBUG, WARNING, ERROR, CRITICAL INFO and NONE [default: INFO]

acl

Mount the filesystem with POSIX ACL support

fopen-keep-cache[=BOOL]

Do not purge the cache on file open (default: false)

worm

Mount the filesystem in 'worm' mode

aux-gfid-mount

Enable access to filesystem through gfid directly

ro

Mount the filesystem read-only

enable-ino32=BOOL

Use 32-bit inodes when mounting to workaround broken applications that don't support 64-bit inodes

mem-accounting

Enable internal memory accounting

capability

Enable file capability setting and retrival

thin-client

Enables thin mount and connects via gfproxyd daemon

localtime-logging

Use local timestamps instead of UTC in mount log entries

### Advanced options
attribute-timeout=SECONDS

Set attribute timeout to SECONDS for inodes in fuse kernel module [default: 1]

entry-timeout=SECONDS

Set entry timeout to SECONDS in fuse kernel module [default: 1]

background-qlen=N

Set fuse module's background queue length to N [default: 64]

gid-timeout=SECONDS

Set auxiliary group list timeout to SECONDS for fuse translator [default: 0]

negative-timeout=SECONDS

Set negative timeout to SECONDS in fuse kernel module [default: 0]

volume-name=VOLUME-NAME

Volume name to be used for MOUNT-POINT [default: top most volume in VOLUME-FILE]

direct-io-mode=BOOL|auto

Specify fuse direct I/O strategy [default: auto]

congestion-threshold=N

Set fuse module's congestion threshold to N [default: 48]

ubdir-mount=N

Set the subdirectory mount option [default: NULL, ie, no subdirectory mount]

backup-volfile-servers=SERVERLIST

Provide list of backup volfile servers in the following format [default: None] If use IPv6 address in SERVERLIST, it is required to use '[' and ']' to surround IPv6 address. $ mount -t glusterfs -obackup-volfile-servers=<server2>: <server3>:...:<serverN> <server1>:/<volname> <mount_point> $ mount -t glusterfs -obackup-volfile-servers=<[ipv6_addr2]>: <[ipv6_addr3]>:...:<[ipv6_addrN]> <ipv6_addr1>:/<volname> <mount_point>

backupvolfile-server=SERVER

Provide list of backup volfile servers in the following format [default: None] $ mount -t glusterfs -obackupvolfile-server=<server2> <server1>:/<volname> <mount_point>

fetch-attempts=N

Deprecated option - placed here for backward compatibility [default: 1]

lru-limit=N

Set fuse module's limit for number of inodes kept in LRU list to N [default: 65536]

inode-table-size=N

Set the inode hash table size to N - this must be a power of 2 greater than or equal to 65536 and will be rounded up if not [default: 65536]

invalidate-limit=N

Suspend fuse invalidations implied by 'lru-limit' if number of outstanding invalidations reaches N

background-qlen=N

Set fuse module's background queue length to N [default: 64]

no-root-squash=BOOL

disable root squashing for the trusted client [default: off]

root-squash=BOOL

enable root squashing for the trusted client [default: on]

use-readdirp=BOOL

Use readdirp() mode in fuse kernel module [default: on]

dump-fuse=PATH

Dump fuse traffic to PATH

kernel-writeback-cache=BOOL

Enable fuse in-kernel writeback cache [default: off]

attr-times-granularity=NS

Declare supported granularity of file attribute [default: 0]

auto-invalidation=BOOL

controls whether fuse-kernel can auto-invalidate attribute, dentry and page-cache. Disable this only if same files/directories are not accessed across two different mounts concurrently [default: on]

## FILES
/etc/fstab

A typical GlusterFS entry in /etc/fstab looks like below server1:/mirror /mnt/mirror glusterfs log-file=/var/log/mirror.log,acl 0 0

/proc/mounts

An example entry of a GlusterFS mountpoint in /proc/mounts looks like below server1:/mirror /mnt/glusterfs fuse.glusterfs rw,allow_other,default_permissions,max_read=131072 0 0

## SEE ALSO
glusterfs(8), mount(8), gluster(8)

## COPYRIGHT
Copyright(c) 2006-2013 Red Hat, Inc. <http://www.redhat.com>


glusterd

title: glusterd(8)

summary: Gluster elastic volume management daemon


goa-daemon

package: gnome-online-accounts

title: goa-daemon(8)

summary: GNOME Online Accounts Daemon

text:
# goa-daemon(8)

## NAME
goa-daemon - GNOME Online Accounts Daemon

## SYNOPSIS
goa-daemon [--help] [--replace] [--version]

## DESCRIPTION
The goa-daemon program provides the org.gnome.OnlineAccounts name on the session message bus. Users or administrators should never need to start this daemon as it will be automatically started by dbus-daemon(1) whenever an application sends a D-Bus message to the org.gnome.OnlineAccounts name on the session bus.

## CONFIGURATION FILE
The goa-daemon program stores configuration in the $XDG_CONFIG_HOME/goa-1.0/accounts.conf (typically ~/.config/goa-1.0/accounts.conf) file. The format of this file is private and 3rd party programs or libraries should never read it. This file does not contain any passwords or secrets.

See the XDG Base Directory Specification[1] for more information about $XDG_CONFIG_HOME.

## SECRETS
The goa-daemon program stores secrets (such as OAuth tokens) in GNOME Keyring[2]. The format of the stored secrets is private and 3rd party programs or libraries should never read, modify or delete these secrets.

## OPTIONS
--replace

Replace existing instance.

--version

Show program version.

--help

Show help options.

## AUTHOR
Written by David Zeuthen <zeuthen@gmail.com> with a lot of help from many others.

## BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues. There are some debugging tips at https://wiki.gnome.org/Projects/GnomeOnlineAccounts/Debugging

## SEE ALSO
dbus-daemon(1)

## NOTES
1.

XDG Base Directory Specification

http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html

2.

GNOME Keyring

https://wiki.gnome.org/Projects/GnomeKeyring


addgnupghome

title: addgnupghome(8)

summary: Create .gnupg home directories

text:
# addgnupghome(8)

## NAME
addgnupghome - Create .gnupg home directories

## SYNOPSIS
addgnupghome account_1 account_2...account_n

## DESCRIPTION
If GnuPG is installed on a system with existing user accounts, it is sometimes required to populate the GnuPG home directory with existing files. Especially a ‘trustlist.txt’ and a keybox with some initial certificates are often desired. This script helps to do this by copying all files from ‘/etc/skel/.gnupg’ to the home directories of the accounts given on the command line. It takes care not to overwrite existing GnuPG home directories.

addgnupghome is invoked by root as:

```
addgnupghome account1 account2 ... accountn
```


applygnupgdefaults

title: applygnupgdefaults(8)

text:
# applygnupgdefaults(8)

## NAME
applygnupgdefaults - Run gpgconf --apply-defaults for all users.

## SYNOPSIS
applygnupgdefaults

## DESCRIPTION
This is a legacy script. Modern application should use the per component global configuration files under ‘/etc/gnupg/’.

This script is a wrapper around gpgconf to run it with the command --apply-defaults for all real users with an existing GnuPG home directory. Admins might want to use this script to update he GnuPG configuration files for all users after ‘/etc/gnupg/gpgconf.conf’ has been changed. This allows enforcing certain policies for all users. Note, that this is not a bulletproof way to force a user to use certain options. A user may always directly edit the configuration files and bypass gpgconf.

applygnupgdefaults is invoked by root as:

```
applygnupgdefaults
```


dirmngr

title: dirmngr(8)

summary: GnuPG's network access daemon

text:
# dirmngr(8)

## NAME
dirmngr - GnuPG's network access daemon

## SYNOPSIS
dirmngr [options] command [args]

## DESCRIPTION
Since version 2.1 of GnuPG, dirmngr takes care of accessing the OpenPGP keyservers. As with previous versions it is also used as a server for managing and downloading certificate revocation lists (CRLs) for X.509 certificates, downloading X.509 certificates, and providing access to OCSP providers. Dirmngr is invoked internally by gpg, gpgsm, or via the gpg-connect-agent tool.

## COMMANDS
Commands are not distinguished from options except for the fact that only one command is allowed.

--version

Print the program version and licensing information. Note that you cannot abbreviate this command.

--help, -h

Print a usage message summarizing the most useful command-line options. Note that you cannot abbreviate this command.

--dump-options

Print a list of all available options and commands. Note that you cannot abbreviate this command.

--server

Run in server mode and wait for commands on the stdin. The default mode is to create a socket and listen for commands there. This is only used for testing.

--daemon

Run in background daemon mode and listen for commands on a socket. This is the way dirmngr is started on demand by the other GnuPG components. To force starting dirmngr it is in general best to use gpgconf --launch dirmngr.

--supervised

Run in the foreground, sending logs to stderr, and listening on file descriptor 3, which must already be bound to a listening socket. This option is deprecated and not supported on Windows.

--list-crls

List the contents of the CRL cache on stdout. This is probably only useful for debugging purposes.

--load-crl file

This command requires a filename as additional argument, and it will make Dirmngr try to import the CRL in file into it's cache. Note, that this is only possible if Dirmngr is able to retrieve the CA's certificate directly by its own means. In general it is better to use gpgsm's --call-dirmngr loadcrl filename command so that gpgsm can help dirmngr.

--fetch-crl url

This command requires an URL as additional argument, and it will make dirmngr try to retrieve and import the CRL from that url into it's cache. This is mainly useful for debugging purposes. The dirmngr-client provides the same feature for a running dirmngr.

--shutdown

This commands shuts down an running instance of Dirmngr. This command has currently no effect.

--flush

This command removes all CRLs from Dirmngr's cache. Client requests will thus trigger reading of fresh CRLs.

## OPTIONS
Note that all long options with the exception of --options and --homedir may also be given in the configuration file after stripping off the two leading dashes.

--options file

Reads configuration from file instead of from the default per-user configuration file. The default configuration file is named ‘dirmngr.conf’ and expected in the home directory.

--homedir dir

Set the name of the home directory to dir. This option is only effective when used on the command line. The default is the directory named ‘.gnupg’ directly below the home directory of the user unless the environment variable GNUPGHOME has been set in which case its value will be used. Many kinds of data are stored within this directory.

-v

--verbose

Outputs additional information while running. You can increase the verbosity by giving several verbose commands to dirmngr, such as -vv.

--log-file file

Append all logging output to file. This is very helpful in seeing what the agent actually does. Use ‘socket://’ to log to socket.

--compatibility-flags flags

Set compatibility flags to work around certain problems or to emulate bugs. The flags are given as a comma separated list of flag names and are OR-ed together. The special flag "none" clears the list and allows to start over with an empty list. To get a list of available flags the sole word "help" can be used.

--debug-level level

Select the debug level for investigating problems. level may be a numeric value or by a keyword:

none

No debugging at all. A value of less than 1 may be used instead of the keyword.

basic

Some basic debug messages. A value between 1 and 2 may be used instead of the keyword.

advanced

More verbose debug messages. A value between 3 and 5 may be used instead of the keyword.

expert

Even more detailed messages. A value between 6 and 8 may be used instead of the keyword.

guru

All of the debug messages you can get. A value greater than 8 may be used instead of the keyword. The creation of hash tracing files is only enabled if the keyword is used.

How these messages are mapped to the actual debugging flags is not specified and may change with newer releases of this program. They are however carefully selected to best aid in debugging.

--debug flags

Set debug flags. All flags are or-ed and flags may be given in C syntax (e.g. 0x0042) or as a comma separated list of flag names. To get a list of all supported flags the single word "help" can be used. This option is only useful for debugging and the behavior may change at any time without notice.

--debug-all

Same as --debug=0xffffffff

--tls-debug level

Enable debugging of the TLS layer at level. The details of the debug level depend on the used TLS library and are not set in stone.

--debug-wait n

When running in server mode, wait n seconds before entering the actual processing loop and print the pid. This gives time to attach a debugger.

--disable-check-own-socket

On some platforms dirmngr is able to detect the removal of its socket file and shutdown itself. This option disable this self-test for debugging purposes.

-s

--sh

-c

--csh

Format the info output in daemon mode for use with the standard Bourne shell respective the C-shell. The default is to guess it based on the environment variable SHELL which is in almost all cases sufficient.

--force

Enabling this option forces loading of expired CRLs; this is only useful for debugging.

--use-tor

--no-use-tor

The option --use-tor switches Dirmngr and thus GnuPG into ``Tor mode'' to route all network access via Tor (an anonymity network). Certain other features are disabled in this mode. The effect of --use-tor cannot be overridden by any other command or even by reloading dirmngr. The use of --no-use-tor disables the use of Tor. The default is to use Tor if it is available on startup or after reloading dirmngr. The test on the availability of Tor is done by trying to connect to a SOCKS proxy at either port 9050 or 9150; if another type of proxy is listening on one of these ports, you should use --no-use-tor.

--standard-resolver

This option forces the use of the system's standard DNS resolver code. This is mainly used for debugging. Note that on Windows a standard resolver is not used and all DNS access will return the error ``Not Implemented'' if this option is used. Using this together with enabled Tor mode returns the error ``Not Enabled''.

--recursive-resolver

When possible use a recursive resolver instead of a stub resolver.

--resolver-timeout n

Set the timeout for the DNS resolver to N seconds. The default are 30 seconds.

--connect-timeout n

--connect-quick-timeout n

Set the timeout for HTTP and generic TCP connection attempts to N seconds. The value set with the quick variant is used when the --quick option has been given to certain Assuan commands. The quick value is capped at the value of the regular connect timeout. The default values are 15 and 2 seconds. Note that the timeout values are for each connection attempt; the connection code will attempt to connect all addresses listed for a server.

--listen-backlog n

Set the size of the queue for pending connections. The default is 64.

--allow-version-check

Allow Dirmngr to connect to https://versions.gnupg.org to get the list of current software versions. If this option is enabled the list is retrieved in case the local copy does not exist or is older than 5 to 7 days. See the option --query-swdb of the command gpgconf for more details. Note, that regardless of this option a version check can always be triggered using this command:

```
       gpg-connect-agent --dirmngr 'loadswdb --force' /bye
```

--keyserver name

Use name as your keyserver. This is the server that gpg communicates with to receive keys, send keys, and search for keys. The format of the name is a URI: `scheme:[//]keyservername[:port]' The scheme is the type of keyserver: "hkp" for the HTTP (or compatible) keyservers or "ldap" for the LDAP keyservers. Note that your particular installation of GnuPG may have other keyserver types available as well. Keyserver schemes are case-insensitive. After the keyserver name, optional keyserver configuration options may be provided. These are the same as the --keyserver-options of gpg, but apply only to this particular keyserver. Some keyservers synchronize with each other, so there is not always a need to send keys to more than one server. Some keyservers use round robin DNS to give a different keyserver each time you use it.

If exactly two keyservers are configured and only one is a Tor hidden service (.onion), Dirmngr selects the keyserver to use depending on whether Tor is locally running or not. The check for a running Tor is done for each new connection.

If no keyserver is explicitly configured, dirmngr will use the built-in default of https://keyserver.ubuntu.com.

Windows users with a keyserver running on their Active Directory may use the short form ldap:/// for name to access this directory.

For accessing anonymous LDAP keyservers name is in general just a ldaps://ldap.example.com. A BaseDN parameter should never be specified. If authentication is required things are more complicated and two methods are available:

The modern method (since version 2.2.28) is to use the very same syntax as used with the option --ldapserver. Please see over there for details; here is an example:

```
       keyserver ldap:ldap.example.com::uid=USERNAME,ou=GnuPG Users,

       dc=example,dc=com:PASSWORD::starttls
```

The other method is to use a full URL for name; for example:

```
       keyserver ldaps://ldap.example.com/????bindname=uid=USERNAME

       %2Cou=GnuPG%20Users%2Cdc=example%2Cdc=com,password=PASSWORD
```

Put this all on one line without any spaces and keep the '%2C'

as given. Replace USERNAME, PASSWORD, and the 'dc' parts

according to the instructions received from your LDAP

administrator. Note that only simple authentication

(i.e. cleartext passwords) is supported and thus using ldaps is

strongly suggested (since 2.2.28 "ldaps" defaults to port 389

and uses STARTTLS). On Windows authentication via AD can be

requested by adding gpgNtds=1 after the fourth question

mark instead of the bindname and password parameter.

--nameserver ipaddr

In ``Tor mode'' Dirmngr uses a public resolver via Tor to resolve DNS names. If the default public resolver, which is 8.8.8.8, shall not be used a different one can be given using this option. Note that a numerical IP address must be given (IPv6 or IPv4) and that no error checking is done for ipaddr.

--disable-ipv4

--disable-ipv6

Disable the use of all IPv4 or IPv6 addresses.

--disable-ldap

Entirely disables the use of LDAP.

--disable-http

Entirely disables the use of HTTP.

--ignore-http-dp

When looking for the location of a CRL, the to be tested certificate usually contains so called CRL Distribution Point (DP) entries which are URLs describing the way to access the CRL. The first found DP entry is used. With this option all entries using the HTTP scheme are ignored when looking for a suitable DP.

--ignore-ldap-dp

This is similar to --ignore-http-dp but ignores entries using the LDAP scheme. Both options may be combined resulting in ignoring DPs entirely.

--ignore-ocsp-service-url

Ignore all OCSP URLs contained in the certificate. The effect is to force the use of the default responder.

--honor-http-proxy

If the environment variable ‘http_proxy’ has been set, use its value to access HTTP servers.

--http-proxy host[:port]

Use host and port to access HTTP servers. The use of this option overrides the environment variable ‘http_proxy’ regardless whether --honor-http-proxy has been set.

--ldap-proxy host[:port]

Use host and port to connect to LDAP servers. If port is omitted, port 389 (standard LDAP port) is used. This overrides any specified host and port part in a LDAP URL and will also be used if host and port have been omitted from the URL.

--only-ldap-proxy

Never use anything else but the LDAP "proxy" as configured with --ldap-proxy. Usually dirmngr tries to use other configured LDAP server if the connection using the "proxy" failed.

--ldapserverlist-file file

Read the list of LDAP servers to consult for CRLs and X.509 certificates from file instead of the default per-user ldap server list file. The default value for file is ‘dirmngr_ldapservers.conf’. This server list file contains one LDAP server per line in the format

hostname:port:username:password:base_dn:flags

Lines starting with a ‘#’ are comments.

Note that as usual all strings entered are expected to be UTF-8 encoded. Obviously this will lead to problems if the password has originally been encoded as Latin-1. There is no other solution here than to put such a password in the binary encoding into the file (i.e. non-ascii characters won't show up readable). ([The gpgconf tool might be helpful for frontends as it enables editing this configuration file using percent-escaped strings.])

--ldapserver spec

This is an alternative way to specify LDAP servers for CRL and X.509 certificate retrieval. If this option is used the servers configured in ‘dirmngr_ldapservers.conf’ (or the file given by --ldapserverlist-file) are cleared. Note that ‘dirmngr_ldapservers.conf’ is not read again by a reload signal. However, --ldapserver options are read again. spec is either a proper LDAP URL or a colon delimited list of the form

hostname:port:username:password:base_dn:flags:

with an optional prefix of ldap: (but without the two slashes which would turn this into a proper LDAP URL). flags is a list of one or more comma delimited keywords:

plain

The default: Do not use a TLS secured connection at all; the default port is 389.

starttls

Use STARTTLS to secure the connection; the default port is 389.

ldaptls

Tunnel LDAP through a TLS connection; the default port is 636.

ntds

On Windows authenticate the LDAP connection using the Active Directory with the current user.

areconly

On Windows use only the A or AAAA record when resolving the LDAP server name.

Note that in an URL style specification the scheme ldaps:// refers to STARTTLS and _not_ to LDAP-over-TLS.

--ldaptimeout secs

Specify the number of seconds to wait for an LDAP query before timing out. The default are 15 seconds. 0 will never timeout.

--add-servers

This option makes dirmngr add any servers it discovers when validating certificates against CRLs to the internal list of servers to consult for certificates and CRLs. This option should in general not be used. This option might be useful when trying to validate a certificate that has a CRL distribution point that points to a server that is not already listed in the ldapserverlist. Dirmngr will always go to this server and try to download the CRL, but chances are high that the certificate used to sign the CRL is located on the same server. So if dirmngr doesn't add that new server to list, it will often not be able to verify the signature of the CRL unless the --add-servers option is used.

Caveat emptor: Using this option may enable denial-of-service attacks and leak search requests to unknown third parties. This is because arbitrary servers are added to the internal list of LDAP servers which in turn is used for all unspecific LDAP queries as well as a fallback for queries which did not return a result.

--allow-ocsp

This option enables OCSP support if requested by the client. OCSP requests are rejected by default because they may violate the privacy of the user; for example it is possible to track the time when a user is reading a mail.

--ocsp-responder url

Use url as the default OCSP Responder if the certificate does not contain information about an assigned responder. Note, that --ocsp-signer must also be set to a valid certificate.

--ocsp-signer fpr|file

Use the certificate with the fingerprint fpr to check the responses of the default OCSP Responder. Alternatively a filename can be given in which case the response is expected to be signed by one of the certificates described in that file. Any argument which contains a slash, dot or tilde is considered a filename. Usual filename expansion takes place: A tilde at the start followed by a slash is replaced by the content of ‘HOME’, no slash at start describes a relative filename which will be searched at the home directory. To make sure that the file is searched in the home directory, either prepend the name with "./" or use a name which contains a dot. If a response has been signed by a certificate described by these fingerprints no further check upon the validity of this certificate is done.

The format of the FILE is a list of SHA-1 fingerprint, one per line with optional colons between the bytes. Empty lines and lines prefix with a hash mark are ignored.

--ocsp-max-clock-skew n

The number of seconds a skew between the OCSP responder and them local clock is accepted. Default is 600 (10 minutes).

--ocsp-max-period n

Seconds a response is at maximum considered valid after the time given in the thisUpdate field. Default is 7776000 (90 days).

--ocsp-current-period n

The number of seconds an OCSP response is considered valid after the time given in the NEXT_UPDATE datum. Default is 10800 (3 hours).

--max-replies n

Do not return more that n items in one query. The default is 10.

--ignore-cert-extension oid

Add oid to the list of ignored certificate extensions. The oid is expected to be in dotted decimal form, like 2.5.29.3. This option may be used more than once. Critical flagged certificate extensions matching one of the OIDs in the list are treated as if they are actually handled and thus the certificate won't be rejected due to an unknown critical extension. Use this option with care because extensions are usually flagged as critical for a reason.

--ignore-crl-extension oid

Add oid to the list of ignored CRL extensions. The oid is expected to be in dotted decimal form. Critical flagged CRL extensions matching one of the OIDs in the list are treated as if they are actually handled and thus the certificate won't be rejected due to an unknown critical extension. Use this option with care because extensions are usually flagged as critical for a reason.

--ignore-cert fpr|file

Entirely ignore certificates with the fingerprint fpr. As an alternative to the fingerprint a filename can be given in which case all certificates described in that file are ignored. Any argument which contains a slash, dot or tilde is considered a filename. Usual filename expansion takes place: A tilde at the start followed by a slash is replaced by the content of ‘HOME’, no slash at start describes a relative filename which will be searched at the home directory. To make sure that the file is searched in the home directory, either prepend the name with "./" or use a name which contains a dot. The format of such a file is a list of SHA-1 fingerprint, one per line with optional colons between the bytes. Empty lines and lines prefixed with a hash mark are ignored. This option is useful as a quick workaround to exclude certain certificates from the system store.

--hkp-cacert file

Use the root certificates in file for verification of the TLS certificates used with hkps (keyserver access over TLS). If the file is in PEM format a suffix of .pem is expected for file. This option may be given multiple times to add more root certificates. Tilde expansion is supported. If no hkp-cacert directive is present, dirmngr will use the system CAs.

## EXAMPLES
Here is an example on how to show dirmngr's internal table of OpenPGP keyserver addresses. The output is intended for debugging purposes and not part of a defined API.

```
  gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye
```

To inhibit the use of a particular host you have noticed in one of the keyserver pools, you may use

```
 gpg-connect-agent --dirmngr 'keyserver --dead pgpkeys.bnd.de' /bye
```

The description of the keyserver command can be printed using

```
 gpg-connect-agent --dirmngr 'help keyserver' /bye
```

## FILES
Dirmngr makes use of several directories when running in daemon mode: There are a few configuration files to control the operation of dirmngr. By default they may all be found in the current home directory (see: [option --homedir]).

dirmngr.conf

This is the standard configuration file read by dirmngr on startup. It may contain any valid long option; the leading two dashes may not be entered and the option may not be abbreviated. This file is also read after a SIGHUP however not all options will actually have an effect. This default name may be changed on the command line (see: [option --options]). You should backup this file.

/etc/gnupg/trusted-certs

This directory should be filled with certificates of Root CAs you are trusting in checking the CRLs and signing OCSP Responses. Usually these are the same certificates you use with the applications making use of dirmngr. It is expected that each of these certificate files contain exactly one DER encoded certificate in a file with the suffix ‘.crt’ or ‘.der’. dirmngr reads those certificates on startup and when given a SIGHUP. Certificates which are not readable or do not make up a proper X.509 certificate are ignored; see the log file for details.

Applications using dirmngr (e.g. gpgsm) can request these certificates to complete a trust chain in the same way as with the extra-certs directory (see below).

Note that for OCSP responses the certificate specified using the option --ocsp-signer is always considered valid to sign OCSP requests.

/etc/gnupg/extra-certs

This directory may contain extra certificates which are preloaded into the internal cache on startup. Applications using dirmngr (e.g. gpgsm) can request cached certificates to complete a trust chain. This is convenient in cases you have a couple intermediate CA certificates or certificates usually used to sign OCSP responses. These certificates are first tried before going out to the net to look for them. These certificates must also be DER encoded and suffixed with ‘.crt’ or ‘.der’.

~/.gnupg/crls.d

This directory is used to store cached CRLs. The ‘crls.d’ part will be created by dirmngr if it does not exists but you need to make sure that the upper directory exists.

Several options control the use of trusted certificates for TLS and CRLs. Here is an Overview on the use and origin of those Root CA certificates:

System

These System root certificates are used by: FIXME

The origin of the system provided certificates depends on the platform. On Windows all certificates from the Windows System Stores ROOT and CA are used.

On other platforms the certificates are read from the first file found form this list: ‘/etc/ssl/ca-bundle.pem’, ‘/etc/ssl/certs/ca-certificates.crt’, ‘/etc/pki/tls/cert.pem’, ‘/usr/local/share/certs/ca-root-nss.crt’, ‘/etc/ssl/cert.pem’.

GnuPG

The GnuPG specific certificates stored in the directory ‘/etc/gnupg/trusted-certs’ are only used to validate CRLs.

OpenPGP keyserver

For accessing the OpenPGP keyservers the only certificates used are those set with the configuration option hkp-cacert.

OpenPGP keyserver pool

This is usually only one certificate read from the file ‘/usr/share/gnupg/gnupg/sks-keyservers.netCA.pem’. If this certificate exists it is used to access the special keyservers hkps.pool.sks-keyservers.net (or ‘hkps://keys.gnupg.net’).

Please note that gpgsm accepts Root CA certificates for its own purposes only if they are listed in its file ‘trustlist.txt’. dirmngr does not make use of this list - except FIXME.

## NOTES
To be able to see diagnostics it is often useful to put at least the following lines into the configuration file ‘~/gnupg/dirmngr.conf’:

```
log-file ~/dirmngr.log
verbose
```

You may want to check the log file to see whether all desired root CA certificates are correctly loaded.

To be able to perform OCSP requests you probably want to add the line:

```
allow-ocsp
```

To make sure that new options are read or that after the installation of a new GnuPG versions the right dirmngr version is running, you should kill an existing dirmngr so that a new instance is started as needed by the other components:

```
gpgconf --kill dirmngr
```

Direct interfaction with the dirmngr is possible by using the command

```
gpg-connect-agent --dirmngr
```

Enter HELP at the prompt to see a list of commands and enter HELP followed by a command name to get help on that command.

## SIGNALS
A running dirmngr may be controlled by signals, i.e. using the kill command to send a signal to the process.

Here is a list of supported signals:

SIGHUP

This signal flushes all internally cached CRLs as well as any cached certificates. Then the certificate cache is reinitialized as on startup. Options are re-read from the configuration file. Instead of sending this signal it is better to use

```
gpgconf --reload dirmngr
```

SIGTERM

Shuts down the process but waits until all current requests are fulfilled. If the process has received 3 of these signals and requests are still pending, a shutdown is forced. You may also use

```
gpgconf --kill dirmngr
```

instead of this signal

SIGINT

Shuts down the process immediately.

SIGUSR1

This prints some caching statistics to the log file.

## SEE ALSO
gpgsm(1), dirmngr-client(1)

The full documentation for this tool is maintained as a Texinfo manual. If GnuPG and the info program are properly installed at your site, the command

```
info gnupg
```

should give you access to the complete manual including a menu structure and an index.


gdomap

package: gnustep-base

title: gdomap(8)

summary: GNUstep Distributed Objects name server

text:
# gdomap(8)

## NAME
gdomap - GNUstep Distributed Objects name server

## SYNOPSIS
gdomap [-C|-H] [-I pidfile] [-L name] [-M name] [-N] [-P number] [-R name] [-S] [-T type] [-U name] [-a file] [-c file] [-d] [-f] [-i seconds] [-j path] [-p]

## DESCRIPTION
gdomap The gdomap daemon is used by GNUstep programs to look up distributed objects of processes running across the network (and between different user accounts on a single machine). The daemon is NOT used for lookup where two processes belonging to the same user are using a host-local connection. This manual page explains the usage of gdomap. For design and implementation information (and special notes for packagers), please see the HTML documentation installed in $GNUSTEP_SYSTEM_DOC, under Command-line Tools.

Usually the gdomap daemon is started at system boot time and binds itself to port 538. See the GNUstep Build Guide for a sample startup script.

By default gdomap probes every machine on the local network to see if there is a copy of gdomap running on it. This is done for class-C networks and subnets of class-C networks. If your host is on a class-B or class-A net then the default behaviour is to treat it as a class-C net and probe only the hosts that would be expected on a class-C network of the same number.

If you are running on a class-A or class-B network, or if your net has a large number of hosts which will not have gdomap on them - you may want to supply a configuration file listing the hosts to be probed explicitly, rather than getting gdomap to probe all hosts on the local net.

You may also want to supply the configuration file so that hosts which are not actually on your local network can still be found when your code tries to connect to a host using @"*" as the host name. NB. this functionality does not exist in OpenStep.

A configuration file consists of a list of IP addresses to be probed. The IP addresses should be in standard 'dot' notation, one per line. Empty lines are permitted in the configuration file. Anything on a line after a hash ('#') is ignored. You tell gdomap about the config file with the '-c' command line option.

gdomap uses the SIOCGIFCONF ioctl to build a list of IP addresses and netmasks for the network interface cards on your machine. On some operating systems, this facility is not available (or is broken), so you must tell gdomap the addresses and masks of the interfaces using the '-a' command line option. The file named with '-a' should contain a series of lines with space separated pairs of addresses and masks in 'dot' notation. You must NOT include loopback interfaces in this list. If you want to support broadcasting of probe information on a network, you may supply the broadcast address as a third item on the line. If your operating system has some other method of giving you a list of network interfaces and masks, please send me example code so that I can implement it in gdomap.

## OPTIONS
-C

help about configuration

-H

general help

-I

pid file to write pid

-L name

perform lookup for name then quit.

-M name

machine name for -L and -N

-N

list all names registered on host

-P number

port number required for -R option.

-R name

register name locally then quit. -S

-S

list the addresses of all gdomap servers known to host

-T type

port type for -L , -R and -U options - tcp_gdo, udp_gdo, tcp_foreign, udp_foreign.

-U name

unregister name locally then quit.

-a file

use config file for interface list.

-c file

use config file for probe.

-d

extra debug logging (normally via syslog).

-f

avoid fork() to make debugging easy

-i seconds

re-probe at this interval (roughly), min 60

-j path

place the process in a chroot jail at this path rather than in /tmp

-p

disable probing for other servers

## FILES
Use the -c option to specify a configuration file for gdomap. See under DESCRIPTION for possible configurations.

## DIAGNOSTICS
Kill with SIGUSR1 to obtain a dump of all known peers in /tmp/gdomap.dump

gdomap -N lists all registered names on the local host.

## SEE ALSO
gdomap -C gives above instructions on how to set up gdomap.

gdnc(1), GNUstep(7), gpbs(1)

The GNUstep Build Guide example rc script: <http://gnustep.made-it.com/BuildGuide/index.html#GNUSTEP.SERVICES>

## HISTORY
Work on gdomap started in October 1996.

This manual page first appeared in gnustep-base 1.7.1 (June 2003).

## AUTHORS
gdomap was written by Richard Frith-Macdonald <rfm@gnu.org>

This manual page was put together by Martin Brecher <martin@mb-itconsulting.com>.


nss-cache-oslogin

package: google-guest-oslogin

title: nss-cache-oslogin(8)

text:
# nss-cache-oslogin(8)

## NAME
nss-cache-oslogin, libnss_cache_oslogin.so.2 - UNIX implementation for OS Login Users and Groups with local caching.

## SYNOPSIS
libnss_cache_oslogin.so.2

## DESCRIPTION
nss-cache-oslogin is a plug-in module for the GNU Name Service Switch (NSS) functionality of the GNU C Library (glibc). This module provides UNIX name resolution from a local cache of users and groups configured in the Google Cloud OS Login system. The "passwd" and "group" services are supported by this module.

To use the NSS module, add "cache_oslogin" to the appropriate service lines in nsswitch.conf. It is recommended to place "cache_oslogin" after any system provided modules and before the "oslogin" module, as it is a pass-through cache.

## FILES
/etc/oslogin_passwd.cache

user cache file

/etc/oslogin_group.cache

group cache file

## NOTES
Documentation for the Google Cloud OS Login service is available online at https://cloud.google.com/compute/docs/oslogin

## SEE ALSO
nss-oslogin(5), nsswitch.conf(5), nss(5), getent(1), initgroups(3)


nss-oslogin

title: nss-oslogin(8)

text:
# nss-oslogin(8)

## NAME
nss-oslogin, libnss_oslogin.so.2 - UNIX implementation for OS Login Users and Groups.

## SYNOPSIS
libnss_oslogin.so.2

## DESCRIPTION
nss-oslogin is a plug-in module for the GNU Name Service Switch (NSS) functionality of the GNU C Library (glibc). This module provides UNIX name resolution for users and groups configured through the Google Cloud OS Login system. The "passwd", "group", and "initgroups" services are supported by this module.

To use the NSS module, add "oslogin" to the appropriate service lines in nsswitch.conf. It is recommended to place "oslogin" as the last entry for each service.

## NOTES
Documentation for the Google Cloud OS Login service is available online at https://cloud.google.com/compute/docs/oslogin

## SEE ALSO
nss-cache-oslogin(8), nsswitch.conf(5), nss(5), getent(1), initgroups(3)


gpart

package: gpart

title: gpart(8)

summary: guess PC-type hard disk partitions

text:
# gpart(8)

## NAME
gpart - guess PC-type hard disk partitions

## SYNOPSIS
gpart [options] device

Options: [-b <backup MBR>][-C c,h,s][-c][-d][-E][-e][-f] [-g][-h][-i][-K <last-sector>][-k <# of sectors>] [-L] [-l <log file>][-n <increment>] [-q][-s <sector-size>] [-t <module-name>][-V][-v] [-W <device>][-w <module-name, weight>]

## DESCRIPTION
gpart tries to guess which partitions are on a hard disk. If the primary partition table has been lost, overwritten or destroyed the partitions still exist on the disk but the operating system cannot access them.

gpart ignores the primary partition table and scans the disk (or disk image, file) sector after sector for several filesystem/partition types. It does so by "asking" filesystem recognition modules if they think a given sequence of sectors resembles the beginning of a filesystem or partition type. Currently the following filesystem types are known to gpart (listed by module names) :

beos

BeOS filesystem type.

bsddl

FreeBSD/NetBSD/386BSD disklabel sub-partitioning scheme used on Intel platforms.

ext2

Linux second extended filesystem.

fat

MS-DOS FAT12/16/32 "filesystems".

hpfs

IBM OS/2 High Performance filesystem.

hmlvm

Linux LVM physical volumes (LVM by Heinz Mauelshagen).

lswap

Linux swap partitions (versions 0 and 1).

minix

The Minix operating system filesystem type.

ntfs

MS Windows NT/2000 filesystem.

qnx4

QNX 4.x filesystem.

reiserfs

The Reiser filesystem (version 3.5.X, X > 11, 3.6.X).

s86dl

Sun Solaris on Intel platforms uses a sub-partitioning scheme on PC hard disks similar to the BSD disklabels.

xfs

Silicon Graphic's journalling filesystem for Linux.

More filesystem guessing modules can be added at runtime (see the -t option). Please consult the gpart README file for detailed explanations on how to create guessing modules. All modules are accompanied by a guessing weight factor which denotes how "educated" their guesses are compared to other modules. This weight can be changed if a certain module keeps on mis-identifying a partition.

Naturally only partitions which have been formatted in some way can be recognized. If the type of a partition entry in the primary partition table is changed from x to y while the filesystem is still of type x, gpart will also still guess a type x.

No checks are performed whether a found filesystem is clean or even consistent/mountable, so it is quite possible that gpart may identify partitions which existed prior to the current partitioning scheme of the disk. Especially on large disks old file system headers/superblocks may be present a long time until they are finally overwritten with user data.

It should be stressed that gpart does a very heuristic job, never believe its output without any plausability checks. It can be easily right in its guesswork but it can also be terribly wrong. You have been warned.

After having found a list of possible partition types, the list is checked for consistency. For example, a partition which overlaps with the previous one will be discarded. All remaining partitions are labelled with one of the following attributes: "primary", "logical", "orphaned" or "invalid".

A partition labelled "orphaned" is a logical partition which seems ok but is missed in the chain of logical partitions. This may occur if a logical partition is deleted from the extended partition table without overwriting the actual disk space.

An "invalid" partition is one that cannot be accepted because of various reasons. If a consistent primary partition table was created in this process it is printed and can be written to a file or device.

## EXTENDED PARTITIONS
If the disk/file to be examined consists of primary partitions only, gpart has quite a good chance to identify them. Extended partitions on the other hand can result in a lot of problems.

Extended partitions are realized as a linked list of extended partition tables, each of which include an entry pointing to a logical partition. The size of an extended partition depends on where the last logical partition ends. This means that extended partitions may include "holes", unallocated disk space which should only be assigned to logical, not primary partitions.

gpart tries to do its best to check a found chain of logical partitions but there are very many possible points of failure. If "good" fdisk programs are used to create extended partitions, the resulting tables consist of a zeroed boot record and the four partition entries of which at least two should be marked unused. Unfortunately e.g. the fdisk program shipped with Windows NT does not seem to zero out the boot record area so gpart has to be overly tolerant in recognizing extended partition tables. This tolerance may result in quite stupid guesses.

## DISK TRANSFERS
If you want to investigate hard disks from other systems you should note down the geometry (number of cylinders, heads per cylinder and sectors per head) used for that disk, and tell gpart about this geometry.

Investigating disks from machines with a different endianness than the scanning one has not been tested at all, and is currently not recommended.

## LARGE DISKS
gpart relies on the OS reporting the correct disk geometry. Unfortunately sometimes the OS may report a geometry smaller the the actual one (e.g. disks with more than 1024 or 16384 cylinder).

gpart checks if guessed partitions extend beyond the disk size and marks those "invalid", but may be mistaken in case the disk size is calculated from an incorrect geometry. For instance if a disk with the geometry 1028/255/63 should be scanned, and the OS reports 1024/255/63 gpart should be called like

gpart -C 1028,255,63 <other options> <device>

## PRECAUTIONS
gpart may be of some help when the primary partition table was lost or destroyed but it can under no circumstances replace proper disk/partition table backups. To save the master boot record (MBR) including the primary partition table to a file type

dd if=/dev/hda of=mbr bs=512 count=1

exchanging /dev/hda with the block device name of the disk in question. This should be done for all disks in the system. To restore the primary partition table without overwriting the MBR type

dd if=mbr of=/dev/hda bs=1 count=64 skip=446 seek=446

Warning: make sure that all parameters are typed as shown and that the disk device is correct. Failing to do so may result in severe filesystem corruption. The saved file should be stored in a safe place like a floppy disk.

## OPTIONS
-b backupfile

If the guessed primary partition table seems consistent and should be written (see the -W option) backup the current MBR into the specified file.

-C c,h,s

Set the disk geometry (cylinders, heads, sectors) for the scan. This is useful if a disk should be scanned which was partitioned using a different geometry, if the device is a disk-image or if the disk geometry cannot be retrieved through the PCs BIOS. No spaces are allowed between the numbers, unless all three are enclosed in quotes.

-c

Check/compare mode (implies the -q quiet option). After the scan is done, the resulting primary partition table is compared to the existing one. The return code of gpart then contains the number of differences (0 if they are identical except for the boot/active flag which cannot be guessed). This option has no effect if -d is given on the command line.

-d

Do not start the guessing loop. Useful if the partition table should be printed (in combination with the -v option) without actually scanning for partitions.

-E

Do not try to identify extended partition tables. If there are extended partitions on the given device gpart will most certainly complain about too many primary partitions because there can be only four primary partitions. Existing logical partitions will be listed as primary ones.

-e

Do not skip disk read errors. If this option is given, and short disk reads or general disk read errors (EIO) are encountered, gpart will exit. If not given, the program tries to continue.

-f

Full scan. When a possible partition is found, gpart normally skips all sectors this entry seems to occupy and continues the scan from the end of the last possible partition. The disk scan can take quite a while if this option is given, be patient.

-g

Do not try to get the disk geometry from the OS. If the device is no block or character device but a plain file this option should be supplied. If the file to be scanned is an image of a disk, the geometry can be given by the -C option.

-h

Show some help.

-i

Run interactively. Each time a possible partition is identified the user is asked for confirmation.

-K last sector

Scan only up to the given sector or the end of the file or device whichever comes first.

-k sectors

Skip given number of sectors before the scan. Potentially useful if a partition is looked for at the end of a large disk.

-L

List available filesystem/partition type modules and their weights, then exit.

-l logfile

Log output to the given file (even if -q was supplied).

-n increment

Scan increment: number of sectors or "s" for single sector increment, "h" for an increment of sectors per head (depends on geometry) or "c" for cylinder increment. The increment also influences the condition where extended partition tables are searched: if the scan increment is "s" (i.e. 1) extended partition tables are required to be on a head boundary, otherwise they must be on a cylinder boundary.

If the disk geometry could not be retrieved and no geometry was given on the command line, the default increment is one sector.

-q

Quiet/no output mode. However if a logfile was specified (see -l option) all output is written to that file. This option overrides the -i interactive mode.

-s sector size

Preset medium sector size. gpart tries to find out the sector size but may fail in doing so. Probed sector sizes are 2^i, i=9..14 (512 to 16384 bytes). The default medium sector size is 512 bytes.

-V

Show version number.

-v

Be verbose. This option can be given more than once resulting in quite a lot of information.

-W device

Write partition table. If a consistent primary partition table has been guessed it can be written to the specified file or device. The supplied device can be the same as the scanned one. Additionally the guessed partition entries can be edited. No checks are performed on the entered values, thus the resulting table is allowed to be highly inconsistent. Please beware.

Warning: The guessed partition table should be checked very carefully before writing it back. You can always write the guessed partition table into a plain file and write this into sector 0 using dd(1) (see section PRECAUTIONS above).

-w module name,weight

Put the given module at the head of the module chain and assign a new weight to that module. All modules are given an initial weight of 1.0. A weight of 0 deactivates the filesystem recognition module. Again no spaces are allowed.

Default settings are "-n h".

## EXAMPLES
- To scan the first IDE hard disk under Linux using default settings type

gpart /dev/hda

- To print the primary partition table of the third IDE drive without starting the scan loop in FreeBSD type

gpart -vvd /dev/wd2

- If lilo(8) was installed in the master boot record (MBR) of a hard disk it saves the contents of the first sector in a file called /boot/boot.<major/minor>. To list the partitions contained in such a file type e.g.

gpart -vdg /boot/boot.0300

If the partition table contains an extended partition, gpart will complain about invalid extended partition tables because the extended entry points to sectors not within that file.

- Usually the first primary partition starts on the second head. If gpart cannot identify the first partition properly this may not be the case. gpart can be told to start the scan directly from sector one of the disk, using the sector-wise scan mode:

gpart -k 1 -n s /dev/hdb

- Suppose gpart identifies an NTFS partition as FAT on a certain disk. In this situation the "ntfs" module should be made the first module to be probed and given a weight higher than the usual weight of 1.0:

gpart -w ntfs,1.5 /dev/hdb

To list the available modules and their weights use the -L option.

- Suppose the hard disk contains a lot of virtual machines and the filesystems inside the VMs isn't used outside. Thereby deactivating the guessing of those filesystems reduces the noise and false positives during the scan process.

Set the module weight to 0 to deactivate guessing it.

For example: The hard disk is formatted with XFS and EXT3 filesystems only and there are a lot of Windows VMs on these filesystems. Thereby deactivating of FAT and NTFS guesses reduce the noise during the scan process and produces a more accurate guess.

gpart -w fat,0 -w ntfs,0 /dev/hdb

- After having checked the output of gpart at least thrice, the primary partition table can be written back to the device this way:

gpart -W /dev/sdc /dev/sdc

This of course may be extremely dangerous to your health and social security, so beware.

- A hard disk with 63 sectors per head is scanned in steps of 63 sectors. To perform the scan on every second head while skipping the first 1008 sectors type

gpart -k 1008 -n 126 /dev/sda

- If you want to see how easily gpart can be mislead, and how many probable partition starts are on a disk, search the whole disk really sector by sector, writing all output to a logfile:

gpart -vvfn s -ql /tmp/gpart.log /dev/sd2 &

Usually gpart will not be able to produce an educated guess of the primary partition table in this mode. The logfile however may contain enough hints to manually reconstruct the partition table.

## FILES
/dev/*

Hard disk block devices. The naming scheme of hard disk block devices is OS dependent, consult your system manuals for more information.

## DIAGNOSTICS
There are many error message types, all of them should be self-explanatory. Complain if they are not.

## BUGS
gpart is beta software, so expect buggy behaviour.

- gpart only accepts extended partition links with one logical partition. There may be fdisk variants out there creating links with up to three logical partition entries but these are not accepted.

## TO DO
- Support big-endian architectures.

- Test on 64-bit architectures.

- Look for boot manager partitions (e.g. OS/2 BM).

- Think about reconstructing logical partition chains.

## AUTHOR
Please send bug reports, suggestions, comments etc. to

Michail Brzitwa <michail@brzitwa.de>

## SEE ALSO
fdisk(8).


gparted

package: gparted

title: gparted(8)

text:
# gparted(8)

## NAME
gparted - GNOME Partition Editor for manipulating disk partitions.

## SYNOPSIS
gparted [device]...

## DESCRIPTION
The gparted application is the GNOME partition editor for creating, reorganizing, and deleting disk partitions.

A disk device can be subdivided into one or more partitions. The gparted application enables you to change the partition organization on a disk device while preserving the contents of the partition.

With gparted you can accomplish the following tasks:

- Create a partition table on a disk device.

- Enable and disable partition flags such as boot and hidden.

- Perform actions with partitions such as create, delete, resize, move, check, label, copy, and paste.

More documentation can be found in the application help manual, and online at:

https://gparted.org

## EXAMPLES
You can run gparted from a command line and specify one or more disk devices.

For example, to start gparted with the devices /dev/sda and /dev/sdc you would use the following command:

gparted /dev/sda /dev/sdc

## NOTES
Editing partitions has the potential to cause LOSS of DATA.

The gparted application is designed to enable you to edit partitions while reducing the risk of data loss. The application is carefully tested and is used by the GParted project team. However, loss of data might occur due to software bugs, hardware problems, or power failure.

You can help to reduce the risk of data loss by not mounting or unmounting partitions outside of the gparted application while gparted is running.

You are advised to BACKUP your DATA before using the gparted application.

## REPORTING BUGS
Report bugs at:

https://gparted.org/bugs.php

## AUTHOR
Manual page written by Curtis Gedak <gedakc@users.sf.net>

## SEE ALSO
parted(8), fdisk(8), mkfs(8), ntfsprogs(8)