Difference between revisions of "/sbin/"
From GhostBSD Wiki
(→Content) |
(→Content) |
||
Line 102: | Line 102: | ||
|/sbin/ggatec||The [https://www.freebsd.org/cgi/man.cgi?query=ggatec&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ggatec] utility is a network client for the [https://en.wikipedia.org/wiki/GEOM GEOM] Gate class. It is responsible for the creation of ggate devices and forwarding I/O requests between the GEOM Gate kernel subsystem and the [https://www.freebsd.org/cgi/man.cgi?query=ggated&sektion=8&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports ggated(8)] network daemon. | |/sbin/ggatec||The [https://www.freebsd.org/cgi/man.cgi?query=ggatec&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ggatec] utility is a network client for the [https://en.wikipedia.org/wiki/GEOM GEOM] Gate class. It is responsible for the creation of ggate devices and forwarding I/O requests between the GEOM Gate kernel subsystem and the [https://www.freebsd.org/cgi/man.cgi?query=ggated&sektion=8&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports ggated(8)] network daemon. | ||
|- | |- | ||
− | |/sbin/ggated||[https://www.freebsd.org/cgi/man.cgi?query=ggated&sektion=8&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports The ggated] utility is a network server for the GEOM Gate class. It runs on a server machine to service [https://en.wikipedia.org/wiki/GEOM GEOM] Gate requests from workers placed on | + | |/sbin/ggated||[https://www.freebsd.org/cgi/man.cgi?query=ggated&sektion=8&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports The ggated] utility is a network server for the GEOM Gate class. It runs on a server machine to service [https://en.wikipedia.org/wiki/GEOM GEOM] Gate requests from workers placed on a client machine. Keep in mind, that connections between [https://www.freebsd.org/cgi/man.cgi?query=ggatec&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ggatec(8)] and ggated are not encrypted. |
− | a client machine. Keep in mind, that connections between [https://www.freebsd.org/cgi/man.cgi?query=ggatec&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ggatec(8)] and ggated are not encrypted. | + | |
|- | |- | ||
|/sbin/ggatel||The [https://www.freebsd.org/cgi/man.cgi?query=ggatel&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ggatel] utility is a local [https://en.wikipedia.org/wiki/GEOM GEOM] Gate class consumer. It can be used as a replacement for [https://www.freebsd.org/cgi/man.cgi?query=md&sektion=4&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports md(4) memory disk] devices or as a "GEOMificator" for non GEOMaware devices, but it was mainly created as an example on how to use and how to communicate with the [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html GEOM] Gate kernel subsystem. | |/sbin/ggatel||The [https://www.freebsd.org/cgi/man.cgi?query=ggatel&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ggatel] utility is a local [https://en.wikipedia.org/wiki/GEOM GEOM] Gate class consumer. It can be used as a replacement for [https://www.freebsd.org/cgi/man.cgi?query=md&sektion=4&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports md(4) memory disk] devices or as a "GEOMificator" for non GEOMaware devices, but it was mainly created as an example on how to use and how to communicate with the [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html GEOM] Gate kernel subsystem. | ||
Line 114: | Line 113: | ||
|/sbin/gmirror||The [https://www.freebsd.org/cgi/man.cgi?query=gmirror&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gmirror] utility is used for mirror (RAID1) configurations. After a mirror's creation, all components are detected and configured automatically. All operations like failure detection, stale component detection, rebuild of stale components, etc. are also done automatically. | |/sbin/gmirror||The [https://www.freebsd.org/cgi/man.cgi?query=gmirror&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gmirror] utility is used for mirror (RAID1) configurations. After a mirror's creation, all components are detected and configured automatically. All operations like failure detection, stale component detection, rebuild of stale components, etc. are also done automatically. | ||
|- | |- | ||
− | |/sbin/gmountver|| | + | |/sbin/gmountver||The [https://www.freebsd.org/cgi/man.cgi?query=gmountver&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gmountver] utility is used to control the mount verification GEOM class. When configured, it passes all the I/O requests to the underlying provider. When the underlying provider disappears - for example because the disk device got disconnected - it queues all the I/O requests and waits for the provider to reappear. When that happens, it attaches to it and sends the queued requests. |
|- | |- | ||
− | |/sbin/gmultipath|| | + | |/sbin/gmultipath||The [https://www.freebsd.org/cgi/man.cgi?query=gmultipath&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gmultipath] utility is used for device multipath configuration. |
|- | |- | ||
− | |/sbin/gnop|| | + | |/sbin/gnop||The [https://www.freebsd.org/cgi/man.cgi?query=gnop&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gnop] utility is used for setting up transparent providers on existing ones. Its main purpose is testing other GEOM classes, as it allows forced provider removal and I/O error simulation with a given probability. It also gathers statistics on the number of read, write, delete, getattr, flush, and other requests, and the number of bytes read and written. |
|- | |- | ||
− | |/sbin/gpart|| | + | |/sbin/gpart||The [https://www.freebsd.org/cgi/man.cgi?query=gpart&sektion=8&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports gpart] utility is used to partition GEOM providers, normally disks. |
|- | |- | ||
− | |/sbin/graid|| | + | |/sbin/graid||The [https://www.freebsd.org/cgi/man.cgi?query=graid&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html graid] utility is used to manage software RAID configurations, sup ported by the GEOM RAID class. |
|- | |- | ||
− | |/sbin/graid3|| | + | |/sbin/graid3|| The [https://www.freebsd.org/cgi/man.cgi?query=graid3&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html graid3 ] utility is used for RAID3 array configuration. After a device is created, all components are detected and configured automatically. |
|- | |- | ||
− | |/sbin/growfs|| | + | |/sbin/growfs||The [https://www.freebsd.org/cgi/man.cgi?query=growfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html growfs] utility makes it possible to expand an UFS file system. Before running growfs the partition or slice containing the file system must be extended using [https://www.freebsd.org/cgi/man.cgi?query=gpart&sektion=8&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports gpart(8)]. |
|- | |- | ||
− | |/sbin/gsched|| | + | |/sbin/gsched||The [https://www.freebsd.org/cgi/man.cgi?query=gsched&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gsched] utility (also callable as geom sched ...) changes the scheduling policy of the requests going to a provider. |
|- | |- | ||
− | |/sbin/gshsec|| | + | |/sbin/gshsec||The [https://www.freebsd.org/cgi/man.cgi?query=gshsec&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gshsec] utility is used for setting up a device which contains a shared secret. The secret is shared between the given providers. To collect the secret, all providers are needed. |
|- | |- | ||
− | |/sbin/gstripe|| | + | |/sbin/gstripe||The [https://www.freebsd.org/cgi/man.cgi?query=gstripe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gstripe] utility is used for setting up a stripe on two or more disks. The striped device can be configured using two different methods: "manual" or "automatic". When using the "manual" method, no metadata are stored on the devices, so the striped device has to be configured by hand every time it is needed. The "automatic" method uses on-disk metadata to detect devices. Once devices are labeled, they will be automatically detected and configured. |
+ | |||
|- | |- | ||
− | |/sbin/gvinum|| | + | |/sbin/gvinum||The [https://www.freebsd.org/cgi/man.cgi?query=gvinum&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gvinum] utility is a Logical Volume Manager control program. |
|- | |- | ||
− | |/sbin/gvirstor|| | + | |/sbin/gvirstor||The [https://www.freebsd.org/cgi/man.cgi?query=gvirstor&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gvirstor] utility is used for setting up a virtual storage device of arbitrary large size (for example, several TB), consisting of an arbitrary number of physical storage devices with the total size which is equal to or smaller than the virtual size. |
|- | |- | ||
− | |/sbin/halt|| | + | |/sbin/halt||The [https://www.freebsd.org/cgi/man.cgi?query=halt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html halt and reboot] utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and, respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database |
|- | |- | ||
− | |/sbin/hastctl|| | + | |/sbin/hastctl|| The [https://www.freebsd.org/cgi/man.cgi?query=hastctl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hastctl] utility is used to control the behaviour of the [https://www.freebsd.org/cgi/man.cgi?query=hastd&sektion=8&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports hastd(8)] daemon. |
|- | |- | ||
− | |/sbin/hastd|| | + | |/sbin/hastd||The [https://www.freebsd.org/cgi/man.cgi?query=hastd&sektion=8&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports hastd] daemon is responsible for managing highly available GEOM providers. hastd allows the transpaent storage of data on two physically separated machines connected over a TCP/IP network. Only one machine (cluster node) can actively use storage provided by hastd. This machine is called primary. The hastd daemon operates on block level, which makes it transparent to file systems and applications. |
|- | |- | ||
|/sbin/ifconfig|| | |/sbin/ifconfig|| | ||
Line 245: | Line 245: | ||
|/sbin/rdump|| | |/sbin/rdump|| | ||
|- | |- | ||
− | |/sbin/reboot|| | + | |/sbin/reboot||The [https://www.freebsd.org/cgi/man.cgi?query=halt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html halt and reboot] utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and, respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database |
|- | |- | ||
|/sbin/recoverdisk|| | |/sbin/recoverdisk|| |
Revision as of 06:40, 11 February 2020
Welcome to /sbin/. |
This page is in maintenance! Please do not change this page without to contact the author or use Discussion! |
Introduction
System programs and administration utilities fundamental to both single-user and multi-user environments. With other words: What works on your system.
Content
Directory | Description |
---|---|
/sbin/adjkerntz | The adjkerntz utility maintains the proper relationship between the kernel clock, which is always set to UTC and the CMOS clock, which may be set to local time. |
/sbin/bectl | Utility to manage boot environments on ZFS |
/sbin/bsdlabel | read and write BSD label |
/sbin/camcontrol | CAM control program The camcontrol utility is designed to provide a way for users to access and control the FreeBSD CAM subsystem. |
/sbin/ccdconfig | The ccdconfig utility is used to dynamically configure and unconfigure concatenated disk devices, or ccds. For more information about the ccd, see ccd(4). |
/sbin/clri | The clri utility is obsoleted for normal file system repair work by fsck(8). |
/sbin/comcontrol | The comcontrol utility is used to examine and modify some of the special characteristics of the specified tty device. |
/sbin/conscontrol | The conscontrol utility is used to examine and modify the physical devices which back the virtual console devices. If no arguments (or only the list command) are specified, the current console settings are shown. |
/sbin/ddb | The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily via sysctl(8) MIB entries. |
/sbin/decryptcore | The decryptcore utility first decrypts keyfile using privatekeyfile and then uses the resulting key to decrypt encryptedcore saved by savecore(8). The result is saved in core. |
/sbin/devd | The devd daemon provides a way to have userland programs run when certain kernel events happen. |
/sbin/devfs | The devfs utility provides an interface to manipulate properties of
devfs(5) mounts. |
/sbin/devmatch | The devmatch utility, without any arguments, prints all the kernel modules it has found for all the unattached, enabled devices in the system. |
/sbin/dhclient | The dhclient utility provides a means for configuring network interfaces using DHCP, BOOTP, or if these protocols fail, by statically assigning an address. |
/sbin/dhclient-script | The DHCP client network configuration script is invoked from time to time by dhclient(8). This script is used by the DHCP client to set each interface's initial configuration prior to requesting an address, to test the address once it has been offered, and to set the interface's final configuration once a lease has been acquired. If no lease is acquired, the script is used to test predefined leases, if any, and also called once if no valid lease can be identified. |
/sbin/dhcpcd | dhcpcd is an implementation of the DHCP client specified in RFC 2131. dhcpcd gets the host information (IP address, routes, etc) from a DHCP server and configures the network interface of the machine on which it is running. |
/sbin/disklabel | The bsdlabel utility installs, examines or modifies the BSD label on a disk partition, or on a file containing a partition image. In addition, bsdlabel can install bootstrap code. |
/sbin/dmesg | The dmesg utility displays the contents of the system message buffer. If the -M option is not specified, the buffer is read from the currently running kernel via the sysctl(3) interface. Otherwise, the buffer is read from the specified core file, using the name list from the specified kernel image (or from the default image). |
/sbin/dump | The dump utility examines files on a file system and determines which files need to be backed up. These files are copied to the given disk, tape or other storage medium for safe keeping (see the -f option below for doing remote backups). A dump that is larger than the output medium is broken into multiple volumes. On most media the size is determined by writing until an end-of-media indication is returned. This can be enforced by using the -a option. |
/sbin/dumpfs | The dumpfs utility prints out the UFS super block and cylinder group in formation for the file system or special device specified, unless the -f, -l or -m flag is specified. The listing is very long and detailed. This command is useful mostly for finding out certain file system information
such as the file system block size and minimum free space percentage. |
/sbin/dumpon | The dumpon utility is used to configure where the kernel can save a crash dump in the case of a panic.
System administrators should typically configure dumpon in a persistent fashion using the rc.conf(5) variables dumpdev and dumpon_flags. For more information on this usage, see rc.conf(5). |
/sbin/e2fsck | e2fsck is used to check the ext2/ext3/ext4 family of file systems. For ext3 and ext4 filesystems that use a journal, if the system has been shut down uncleanly without any errors, normally, after replaying the committed transactions in the journal, the file system should be marked as clean. Hence, for filesystems that use journalling, e2fsck will normally replay the journal and exit, unless its superblock indicates that further checking is required. |
/sbin/etherswitchcfg | The etherswitchcfg utility is used to configure an Ethernet switch built into the system. |
/sbin/fastboot | fastboot is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. |
/sbin/fasthalt | The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and, respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database. |
/sbin/fdisk | fdisk is a PC slice table maintenance utility |
/sbin/ffsinfo | ffsinfo dumps all meta information of an existing ufs file system. |
/sbin/fsck | The fsck utility invokes file system-specific programs to check the special devices listed in the fstab(5) file or in the command line for consistency. |
/sbin/fsck_4.2bsd | man; GitHub |
/sbin/fsck_ext2fs | fsck_ext2fs maps the traditional FreeBSD fsck_ffs options to options with the same functionality for e2fsck, runs e2fsck and then maps its exit status to values that FreeBSD understands. e2fsck is a utility to check and repair ext2 and ext3 file systems. |
/sbin/fsck_ffs | man; GitHub |
/sbin/fsck_msdosfs | The fsck_msdosfs utility verifies and repairs FAT file systems (more commonly known as DOS file systems). See also mount_msdosfs |
/sbin/fsck_ufs | man; GitHub |
/sbin/fsdb | The fsdb utility opens fsname (usually a raw disk partition) and runs a command loop allowing manipulation of the file system's inode data. |
/sbin/fsirand | The fsirand utility installs random generation numbers on all the inodes for each file system specified on the command line by special. This in creases the security of NFS-exported file systems by making it difficult
to ``guess filehandles. |
/sbin/gbde | gbde is an operation and management utility for Geom Based Disk Encryption |
/sbin/gcache | The gcache utility is used to control GEOM cache, which can speed up read performance by sending fixed size read requests to its consumer. It has been developed to address the problem of a horrible read performance of a 64k blocksize FS residing on a RAID3 array with 8 data components, where a single disk component would only get 8k read requests, thus effectively killing disk performance under high load. |
/sbin/gconcat | The gconcat utility is used for device concatenation configuration. The concatenation can be configured using two different methods: ``manual or ``automatic. When using the ``manual method, no metadata are stored on the devices, so the concatenated device has to be configured by hand every time it is needed. The ``automatic method uses on-disk metadata to detect devices. Once devices are labeled, they will be automatically detected and configured. |
/sbin/geli | geli is a control utility for the cryptographic GEOM class |
/sbin/geom | The geom utility is used to control various GEOM classes. |
/sbin/ggatec | The ggatec utility is a network client for the GEOM Gate class. It is responsible for the creation of ggate devices and forwarding I/O requests between the GEOM Gate kernel subsystem and the ggated(8) network daemon. |
/sbin/ggated | The ggated utility is a network server for the GEOM Gate class. It runs on a server machine to service GEOM Gate requests from workers placed on a client machine. Keep in mind, that connections between ggatec(8) and ggated are not encrypted. |
/sbin/ggatel | The ggatel utility is a local GEOM Gate class consumer. It can be used as a replacement for md(4) memory disk devices or as a "GEOMificator" for non GEOMaware devices, but it was mainly created as an example on how to use and how to communicate with the GEOM Gate kernel subsystem. |
/sbin/gjournal | The gjournal utility is used for journal configuration on the given GEOM provider. |
/sbin/glabel | The glabel utility is used for GEOM provider labelization. A label can be set up on a GEOM provider in two ways: "manual" or "automatic". When using the "manual" method, no metadata are stored on the devices, so a
label has to be configured by hand every time it is needed. The "automatic" method uses on-disk metadata to store the label and detect it automatically in the future. |
/sbin/gmirror | The gmirror utility is used for mirror (RAID1) configurations. After a mirror's creation, all components are detected and configured automatically. All operations like failure detection, stale component detection, rebuild of stale components, etc. are also done automatically. |
/sbin/gmountver | The gmountver utility is used to control the mount verification GEOM class. When configured, it passes all the I/O requests to the underlying provider. When the underlying provider disappears - for example because the disk device got disconnected - it queues all the I/O requests and waits for the provider to reappear. When that happens, it attaches to it and sends the queued requests. |
/sbin/gmultipath | The gmultipath utility is used for device multipath configuration. |
/sbin/gnop | The gnop utility is used for setting up transparent providers on existing ones. Its main purpose is testing other GEOM classes, as it allows forced provider removal and I/O error simulation with a given probability. It also gathers statistics on the number of read, write, delete, getattr, flush, and other requests, and the number of bytes read and written. |
/sbin/gpart | The gpart utility is used to partition GEOM providers, normally disks. |
/sbin/graid | The graid utility is used to manage software RAID configurations, sup ported by the GEOM RAID class. |
/sbin/graid3 | The graid3 utility is used for RAID3 array configuration. After a device is created, all components are detected and configured automatically. |
/sbin/growfs | The growfs utility makes it possible to expand an UFS file system. Before running growfs the partition or slice containing the file system must be extended using gpart(8). |
/sbin/gsched | The gsched utility (also callable as geom sched ...) changes the scheduling policy of the requests going to a provider. |
/sbin/gshsec | The gshsec utility is used for setting up a device which contains a shared secret. The secret is shared between the given providers. To collect the secret, all providers are needed. |
/sbin/gstripe | The gstripe utility is used for setting up a stripe on two or more disks. The striped device can be configured using two different methods: "manual" or "automatic". When using the "manual" method, no metadata are stored on the devices, so the striped device has to be configured by hand every time it is needed. The "automatic" method uses on-disk metadata to detect devices. Once devices are labeled, they will be automatically detected and configured. |
/sbin/gvinum | The gvinum utility is a Logical Volume Manager control program. |
/sbin/gvirstor | The gvirstor utility is used for setting up a virtual storage device of arbitrary large size (for example, several TB), consisting of an arbitrary number of physical storage devices with the total size which is equal to or smaller than the virtual size. |
/sbin/halt | The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and, respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database |
/sbin/hastctl | The hastctl utility is used to control the behaviour of the hastd(8) daemon. |
/sbin/hastd | The hastd daemon is responsible for managing highly available GEOM providers. hastd allows the transpaent storage of data on two physically separated machines connected over a TCP/IP network. Only one machine (cluster node) can actively use storage provided by hastd. This machine is called primary. The hastd daemon operates on block level, which makes it transparent to file systems and applications. |
/sbin/ifconfig | |
/sbin/init | |
/sbin/ipf | |
/sbin/ipfs | |
/sbin/ipfstat | |
/sbin/ipfw | |
/sbin/ipmon | |
/sbin/ipnat | |
/sbin/ippool | |
/sbin/iscontrol | |
/sbin/kldconfig | |
/sbin/kldload | |
/sbin/kldstat|| | |
/sbin/kldunload | |
/sbin/ldconfig | |
/sbin/md5 | |
/sbin/mdconfig | |
/sbin/mdmfs | |
/sbin/mknod | |
/sbin/mksnap_ffs | |
/sbin/mount | |
/sbin/mount_cd9660 | |
/sbin/mount_fusefs | |
/sbin/mount_mfs | |
/sbin/mount_msdosfs | |
/sbin/mount_nfs | |
/sbin/mount_nullfs | |
/sbin/mount_udf | |
/sbin/mount_unionfs | |
/sbin/natd | |
/sbin/newfs | |
/sbin/newfs_msdos | |
/sbin/nextboot | |
/sbin/nfsiod | |
/sbin/nologin | |
/sbin/nos-tun | |
/sbin/nvmecontrol | |
/sbin/openrc | |
/sbin/openrc-run | |
/sbin/pfctl | |
/sbin/pflogd | |
/sbin/ping | |
/sbin/ping6 | |
/sbin/poweroff | |
/sbin/quotacheck | |
/sbin/rc | |
/sbin/rc-service | |
/sbin/rc-update | |
/sbin/rcorder | |
/sbin/rdump | |
/sbin/reboot | The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and, respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database |
/sbin/recoverdisk | |
/sbin/resolvconf | |
/sbin/restore | |
/sbin/rmd160 | |
/sbin/route | |
/sbin/routed | |
/sbin/rrestore | |
/sbin/rtquery | |
/sbin/rtsol | |
/sbin/runscript | |
/sbin/savecore | |
/sbin/setkey | |
/sbin/sha1 | |
/sbin/sha224 | |
/sbin/sha256 | |
/sbin/sha384 | |
/sbin/sha512 | |
/sbin/sha512t256 | |
/sbin/shutdown | |
/sbin/skein256 | |
/sbin/skein512 | |
/sbin/skein1024 | |
/sbin/spppcontrol | |
/sbin/start-stop-daemon | |
/sbin/supervise-daemon | |
/sbin/swapctl | |
/sbin/swapoff | |
/sbin/swapon | |
/sbin/sysctl | The sysctl utility retrieves kernel state and allows processes with appropriate privilege to set kernel state. The state to be retrieved or set is described using a "Management Information Base" ("MIB") style name, described as a dotted set of components. Example:sysctl kern.osreldate gives you the last kernel modification and the same result as uname -U . It is related to the FreeBSD release as a numerical output. See kern.osreldate
|
/sbin/tunefs | |
/sbin/umount | |
/sbin/zfs | |
/sbin/zfsbootcfg | |
/sbin/zpool | |
Back to Directory Structure |