command
stringlengths 1
42
| description
stringlengths 29
182k
⌀ | name
stringlengths 7
64.9k
⌀ | synopsis
stringlengths 4
85.3k
⌀ | options
stringclasses 593
values | examples
stringclasses 455
values |
|---|---|---|---|---|---|
cron
|
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in /usr/lib/cron/tabs. There should be no need to start it manually. See /System/Library/LaunchDaemons/com.vix.cron.plist for details. The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. The cron utility also searches for /etc/crontab which is in a different format (see crontab(5)). The cron utility then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if such exists). Additionally, cron checks each minute to see if its spool directory's modification time (or the modification time on /etc/crontab) has changed, and if it has, cron will then examine the modification time on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab file is modified. Note that the crontab(1) command updates the modification time of the spool directory whenever it changes a crontab. Available options: -s Enable special handling of situations when the GMT offset of the local timezone changes, such as the switches between the standard time and daylight saving time. The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a time interval that disappears (for example, during the switch from standard time) to daylight saving time or is duplicated (for example, during the reverse switch), then it is handled in one of two ways: The first case is for the jobs that run every at hour of a time interval overlapping with the disappearing or duplicated interval. In other words, if the job had run within one hour before the GMT offset change (and cron was not restarted nor the crontab(5) changed after that) or would run after the change at the next hour. They work as always, skip the skipped time or run in the added time as usual. The second case is for the jobs that run less frequently. They are executed exactly once, they are not skipped nor executed twice (unless cron is restarted or the user's crontab(5) is changed during such a time interval). If an interval disappears due to the GMT offset change, such jobs are executed at the same absolute point of time as they would be in the old time zone. For example, if exactly one hour disappears, this point would be during the next hour at the first minute that is specified for them in crontab(5). -o Disable the special handling of situations when the GMT offset of the local timezone changes, to be compatible with the old (default) behavior. If both options -o and -s are specified, the option specified last wins. -x debugflag[,...] Enable writing of debugging information to standard output. One or more of the following comma separated debugflag identifiers must be specified: bit currently not used ext make the other debug flags more verbose load be verbose when loading crontab files misc be verbose about miscellaneous one-off events pars be verbose about parsing individual crontab lines proc be verbose about the state of the process, including all of its offspring sch be verbose when iterating through the scheduling algorithms test trace through the execution, but do not perform any actions FILES /usr/lib/cron/tabs Directory for personal crontab files SEE ALSO crontab(1), launchctl(1), crontab(5), launchd.plist(5), launchd(8) AUTHORS Paul Vixie ⟨paul@vix.com⟩ macOS 14.5 June 17, 2007 macOS 14.5
|
cron – daemon to execute scheduled commands (Vixie Cron)
|
cron [-s] [-o] [-x debugflag[,...]]
| null | null |
systemstats
|
The systemstats command shows a selection of statistics about system power usage. Run systemstats ---help to see a summary of command-line options. SEE ALSO systemstats_boot(8) macOS 14.5 November 5, 2012 macOS 14.5
|
systemstats – summarize system stats
|
systemstats
| null | null |
kextstat
|
The kextstat utility displays the status of any kexts currently loaded in the kernel. The following information is shown for each loaded kext: Index The load index of the kext (used to track linkage references). Gaps in the list indicate kexts that have been unloaded. Refs The number of references to this kext by others. If nonzero, the kext cannot be unloaded. Address The address in kernel space where the kext has been loaded. Size The number of bytes of kernel memory that the kext occupies. If this is zero, the kext is a built-in part of the kernel that has a record as a kext for resolving dependencies among kexts. Wired The number of wired bytes of kernel memory that the kext occupies. Architecture (if the -a option is used) The architecture of the kext. Name The CFBundleIdentifier of the kext. (Version) The CFBundleVersion of the kext. <Linked Against> The index numbers of all other kexts that this kext has a reference to.
|
kextstat – display status of loaded kernel extensions (kexts)
|
kextstat [-a] [-h] [-k] [-l] [-b identifier] ... DEPRECATED The kextstat utility has been deprecated. Please use the kmutil(8) equivalent: kmutil showloaded.
|
These options are available: -a, -arch Print the architecture of the kext. -b identifier, -bundle-id identifier Display the status of only the kext with the given bundle identifier. This option trumps the -no-kernel option; if both are given and a kernel component is specified, its information is shown. -h, -help Print a help message describing each option flag and exit with a success result, regardless of any other options on the command line. -k, -no-kernel Don't show information for built-in components of the kernel. -l, -list-only Print the list of loaded kexts only and omit the header (useful for running output through text-analysis tools). -s, -sort Sort the list by load address. DIAGNOSTICS The kextstat utility exits with a status of 0 on success and with a nonzero status if an error occurs. SEE ALSO kmutil(8), kernelmanagerd(8), kextcache(8), kextd(8), kextload(8), kextunload(8), kextutil(8) Darwin March 13, 2014 Darwin
| null |
snquota
|
The snquota command manipulates the quota system in the Xsan volume. The quota system provides a means for limiting the amount of disk storage consumed on a per user or per group basis across an entire file system or within a designated directory hierarchy. Quota limits apply to the space consumed by disk-block allocations for a user or group, which is not equal to the sum of their file sizes. Disk-block allocations can be less than the file size if the file is sparse, or more if the file system has allocated extra sequential blocks for the efficiency of anticipated future writes. There are three types of quotas: user quotas, group quotas, and directory quotas. User and group quotas limit the number of volume blocks that can be allocated by the user or group on which the limit is placed. When quotas are on, the total allocated volume space of all users and groups that own files in the volume are automatically kept. Directory quotas are a little different. The system does not automatically keep track of the usage for each directory. The snquota command allows directories to be turned into the root of a Directory Quota Name Space (DQNS). Then, the number and size of all files in the directory and all its subdirectories are tracked and (optionally) limited. For all quota types, limits and usage values only apply to regular files, not directories, symlinks, or special device files Each quota entity has two limits associated with it. These are the hard limit and the soft limit. The hard limit is the absolute limit which volume space usage should not exceed. Any time the total allocated space is at or over the hard limit, all further allocations or write requests by the offending user or group will be denied. The soft limit is a lesser limit. When the user exceeds this limit (but not the hard limit), allocations are still permitted for a while, but a warning message will be written to the logs. (View the messages with Console.app or the dmesg command.) When the soft limit has been overrun for longer than the grace period, the soft limit becomes a hard limit and any further allocations or write requests are denied. When the usage again falls below the soft limit, allocation requests will again be serviced. Previous versions of snquota required all three of the limit values (hard, soft, and grace) to be set or all three to be unset. This version relaxes that somewhat. It is now possible to specify just a hard limit without a soft and grace limit. It's also possible to set a soft limit and grace period without a hard limit. It's also possible to specify a soft limit without any grace period (such a limit warns periodically, but never prevents allocation). It's still not possible to specify a grace period without a soft limit. Although all three values (-h, -s, -t) still need to be on the command line, you can set the limits that should not be enforced to zero. For performance reasons related to the distributed nature of Xsan, quota overruns are not only possible but likely. The overrun size depends upon a number of factors including the size of the allocation request(s) at the time of the quota overrun. Some versions of snquota support setting default limits for the various types of quotas. For example, you can set a default hard limit, soft limit, and grace period for all users. After doing that, any new user created will inherit those limits. Note that setting default limits will not change the limits of existing quota entities. Use the -0 option and either "-u default", "-g default", "-d default", or "-fd default". See the examples section. When working with Directory Quotas, the specified volume must be mounted on the node running snquota. Limits are not enforced against super-user accounts. DIRECTORY QUOTA NAME SPACES DQNSs are created by either of two actions, -C or -M. They have different performance trade-offs and which one to use depends on the situation at hand. The -C action creates a DQNS whose usage values (the amount of disk space and the number of files) are already initialized to the correct value. In order to initialize them, snquota must walk the directory tree under the root of the DQNS and tally up how much disk space is used. For big directory trees, this process can take a long time. Any modifications to the files and directories in the DQNS will be stalled until this walk is complete. The -M action quickly creates a DQNS whose usage values are zero. As files are created in the DQNS, the usage value will increase, but will never count the files that were present in the directory when it was created. In order to initialize the DQNS so the values are correct, the quota database must be rebuild using the -R action. A rebuild runs much faster than a file-tree walk on a per-inode basis, but it must look at all of the inodes in the volume. When the rebuild is running, modifications to the volume will be stalled until the rebuild is complete. So, when creating a DQNS that is believed to contain only a small percentage of the inodes in the volume, use -C. When creating a DQNS (or many DQNSs) that use a large percentage of the files, use -M. A typical situation where -M would be useful is converting an existing volume to use directory quotas. First every directory which needs to be a DQNS root is marked with a call to "snquota -M". Then, all of the DQNSs are initialized with one call to "snquota -R". When in doubt, use -C. Nesting of DQNSs is not allowed. This means that a DQNS may not be a subdirectory of another DQNS. Directories can not be renamed across DQNS boundaries. Also, all hard links to an inode must be within the same DQNS. Attempts to rename directories/files or create hard links that would violate this rule will result in a EXDEV being returned. If a directory tree contains inodes with hard links outside of the tree, an attempt to convert the tree into a DQNS via the -C action on the tree will result in an error. An attempt to convert the tree into a DQNS via the -M and -R actions will result in an error during the -R action. QUOTAS IN MIXED OS ENVIRONMENTS The user and groups names specified in -u and -g represent underlying identifiers that are determined by the OS type of the MDC. On a Linux or Xsan MDC, those identifiers are the classic UNIX User IDentifier (UID) and Group IDentifier (GID). When a UNIX client (Linux, MacOS, Solaris, etc) creates a file, it passes the user's UID and GID to the MDC. Those IDs are attached to the file and are used by the quota subsystem. When a Windows client creates a file, it passes a UID and GID it gets from one of three places: 1. If the Active Directory entry for the user has UNIX IDs associated with it, those are used. The behavior at this point is just like UNIX client. The administrator can set the IDs for a user via the AD configuration tool under the "UNIX Attributes" tab. This tab is part of the "Identity Management for UNIX" subsystem. 2. If the user doesn't have UNIX attributes, then the user and group "nobody" IDs from the file system configuration file are used. 3. If the process's SID is a special "Root SID", the UID/GID passed will be 0/0 (i.e. root). The "root SID" is S-1-5-18. The Windows client can associate a NTSD with a file, but it's ignored by the quota subsystem. (It's only used for access control by the client at that point.) On a Windows MDC, the favored identifiers are user and group SIDs derived from the NTSD which owns the file. If there is no NTSD associated with the file, the UID/GID values associated with the inode are used. So, when a Windows client creates a file, it passes in a NTSD. That NTSD broken into SIDs and used as file's owner identifiers as far as the quota subsystem is concerned. When a UNIX client creates a file, it passes the usual UID/GID pair, not a NTSD. This is used by the quota system. If that file is accessed from a on Windows client, it gets assigned an NTSD. At that point the quota will be wrong. Subsequent allocations of that file will be charged to the SD and not the UID/GID. So, the preferred method of running quotas with a mixture of UNIX and Windows clients is to run with a Linux MDC with UNIX user/group mappings for Active Directory users. That way, a user who logs into clients of either OS will have a single quota (which will be based on the UID). Another option is to just use Directory Quotas. They are much more straight-forward to share between OS types. UNITS Usage and Limits are printed in a human-readable form, suffixed with "K", "M", "G", "T","P", or "E" for kibibytes, mebibyte, gibibyte, tebibyte, pebibytes, or exbibytes, respectively. These are base-2 values (i.e. 1K = 1024). A value without a suffix is in bytes. File count values are also printed with these suffixes, but they are base-10 values (i.e. 1K = 1000). Time values are printed with the suffixes "m", "h", "d", "w", "M" and "y" for minutes, hours, days, weeks, months, and years, respectively. If the -e option is used, the suffixes are disabled and exact values are printed. Time units are in minutes. These suffixes can also be used when specifying limits with the -h, -s, and -t options. Decimal values may be used (e.g -h 1.5g). For the most part, the case of the suffix doesn't matter. The only exception to that is the time suffixes "m" and "M", meaning "minutes" and "months", respectively. FILE SYSTEM SPECIFICATION -F VolumeName Specify VolumeName as the volume to manipulate. VolumeName may be qualified with cluster and administrative domain, if other than the default cluster in which the command is being run. The syntax is VolumeName@<cluster>[/<addom>]. -P Path Specify the volume containing Path as the volume to manipulate. ACTIONS -C This action creates an initialized DQNS on the directory specified by the -d argument. After this command is run, disk space usage and file counts will be tracked in the directory and all its subdirectories. Later, limits may be set on the DQNS using the -S action. Note that since this operation creates and initializes the DQNS, the directory tree contained by the new DQNS will be walked to total up the current usage values. This may take some time. Modifications to the files and directories in the DQNS will be stalled until this walk is complete. -D This action destroys the DQNS specified by the -d argument. Disk space and file count usage values will no longer be tracked. Limits will no longer be enforced. Note that this does not modify or destroy the files and directories in the DQNS in any way. -G This action returns the quota limits and values for the user, group, or directory specified by the -u, -g, or -d option, respectively. -L This action lists the current quota limits and values for all user, group, and directory quotas. -M This action creates (marks) an uninitialized DQNS on the directory specified by the -d argument. After this command is run, disk space usage and file counts will be tracked in the directory and all its subdirectories. Later, limits may be set on the DQNS using the -S option. Note that since this operation creates (but does not initialize) the DQNS, the usage values for the DQNS will start out at zero. The user should later use the -R action to initialize the usage values. See the DIRECTORY QUOTA NAME SPACES section above for a discussion on when to use -M and when to use -C. When in doubt, don't use this action. Use -C instead. -R This action rebuilds the quota database. It is most useful when used after snquota has been used a number of times with the -M action. See the DIRECTORY QUOTA NAME SPACES section above. Note that this action can take a long time. The volume will be unresponsive during this time. The action cannot be canceled after it is started. A prompt will be displayed confirming the intent to run the action unless the -Y option is specified. A rebuild preserves limits and DQNSs. -S This action sets the quota limits for the user, group, or directory specified by the -u, -g, or -d option, respectively. The limits must be specified by the -h, -s, and -t, options. All three must be present, but some/all may be zero. -X This action generates quota reports for all users and groups. There are three files placed in /Library/Logs/Xsan/data/<volume_name>: 1. quota_report.txt - a "pretty" text file report. 2. quota_report.csv - a comma delimited report suitable for Excel spreadsheets. Fields that can have commas, newlines, and other strange characters are escaped with double quotes. This is the case with DQNSs path fields. 3. quota_regen.in - a list of snquota commands that can be used to set up an identical quota database on another Xsan volume. Passing this file to the shell executes it as a script. -Z This action completely destroys all quota configuration and then rebuilds the quota database as in the -R option above. Unlike the -R action, -Z clears the limits and directory quota name spaces. It is recommended that the quota_regen.in file be generated using the -X option to save the quota configuration prior to using -Z.
|
snquota - Xsan Quota Configuration Utility
|
snquota {-F_volume_name|-P_path} action [options]
|
-0 List, read, and set default limits. When specified with the -L action, the default limits are included in the list (if they are non-zero). When specified with the -G or -S actions, the default limits for the specified type of quota are read or written. When using -0, the argument for -u, -g, -d, or -fd should be "default". -a When this option is used, directory quota paths printed by the -L and -G options will be absolute paths. Paths supplied to the -d option are also absolute paths (or relative to the CWD). When this option is absent, all paths are relative to the root of the specified volume. -d Directory This option specifies a DQNS on a Xsan volume to be used with the -C, -D, -G, -M, or -S options. The directory supplied is the root directory of the DQNS. The directory path is relative to the root of the specified volume, unless the -a option is used. -e When used with the -G or -L actions, numbers will be printed as exact values. Usage and Limits which represent disk space are printed in bytes. Times are printed in minutes. For example, with this option, a one megabyte hard limit will be printed as "1048576", not "1M". A one day grace period will be printed as "1440", not "1d". -f The -f option is only useful with the -G and -S actions and the -d option. When the -f option is present, limits and values represent the number of regular files contained in the DQNS. If the -f option is not present, limits and values represent the disk space contained in the DQNS. -g GroupName This option specifies the name of a group to get or set with the -G or -S action. The group name may also be of the form "G:id", where "id" is a number that represents a group's GID. -H HostName Use a hostname in a Xsan cluster that is different from the cluster the command is being run on. This option in rarely needed. -h HardLimit This option specifies a hard limit to set when used with the -S action. See the UNITS section above. The maximum hard limit value is 16 exbibytes - 1 fsBlockSize (the file system configured block size.) If the fsBlockSize is 4096, the maximum hard limit value is 18,446,744,073,709,547,520 bytes. (Note: commas were added for readability; commas are not allowed in values.) -h This option causes snquota to print a friendly help message and exit. It only works when used by itself. If there are other options present, it is assumed that a hard limit is being specified. -o {text|xml|json} Print output in text, xml, or json. The default is text. -s SoftLimit This option specifies a soft limit to set when used with the -S action. See the UNITS section above. The maximum soft limit value is 16 exbibytes - 1 fsBlockSize (the file system configured block size.) If the fsBlockSize is 4096, the maximum soft limit value is 18,446,744,073,709,547,520 bytes. (Note: commas were added for readability; commas are not allowed in values.) -t GracePeriod This option specifies a grace period to set when used with the -S action. See the UNITS section above. -u UserName This option specifies the name of a user to get or set with the -G or -S action. The user name may also be of the form "U:id", where "id" is a number that represents a user's UID. -Y When used with the -R or -Z actions, this option prevents snquota from asking for confirmation. -z This option is the same as specifying "-h 0 -s 0 -t 0". It's only useful with the -S action. EXIT VALUES snquota will return 0 on success and non-zero on failure.
|
List all the quota limits and values on a volume named "data". snquota -F data -L List all the quota limits and values on a volume named "data", but in cluster "cluster1". snquota -F data@cluster1 -L Specify a hard limit of ten gigabytes, a soft limit of nine gigabytes, and a grace period of one week on user "lisa" in a volume named "data". snquota -F data -S -u lisa -h 10g -s 9g -t 1w Turn off quota limits for user "lisa" in a volume named "data". snquota -F data -S -u lisa -z Get the quota values for a group named "simpsons" on a volume mounted on "/stornext/data". snquota -P /stornext/data -G -g simpsons Create a DQNS on the directory "/lisa/saxophone_music" in a volume mounted on "/stornext/data". snquota -P /stornext/data -C -d /lisa/saxophone_music Specify a hard limit of one gigabyte, a soft limit of nine hundred megabytes, and a grace period of one day on pre-existing DQNS "/lisa/saxophone_music" in a volume named "data". snquota -F data -S -d /lisa/saxophone_music -h 1g -s 900m -t 1d Create a number of DQNSs using -M and -R. This is faster than using -C if these directories take up most of the space in the volume. snquota -F data -M -d /bart/comics snquota -F data -M -d /bart/pranks snquota -F data -M -d /bart/itchy_and_scratchy snquota -F data -R Create the same DQNSs using -C. This is faster than using -M and -R if the directories are small. snquota -F data -C -d /bart/comics snquota -F data -C -d /bart/pranks snquota -F data -C -d /bart/itchy_and_scratchy Specify a hard limit of one thousand files, a soft limit of nine hundred files, and a grace period of one week on pre-existing DQNS "/bart/pranks" in a volume named "data". snquota -F data -S -d /bart/pranks -f -h 1k -s 900 -t 1w Set default hard limits limits for all newly created DQNSs. The first line set defaults for disk space and the second line sets defaults for files. snquota -F data -S -0d default -h 1t -s 0 -t 0 snquota -F data -S -0fd default -h 1m -s 0 -t 0 SEE ALSO snfs_config(5), snfs_rest_config.json(4) Xsan File System March 2020 SNQUOTA(1)
|
cvlabel
|
cvlabel is used when configuring the Xsan File System disks. One host that has visibility to all the storage area network disk devices must create a list of disk labels, their associated device names and optionally the sectors to use. The mount_acfs(8) process uses the volume labels to determine which disk drive is to be used for Xsan storage pool nodes. The label name that is written to a disk device must match the [Disk ...] name in the File System Manager (FSM) configuration. See snfs_config(5) for details of the FSM configuration file. It is recommended to first use cvlabel with the -l or -L option. This option will present all of the usable disk devices found on the system. It will try to identify the volume label and display the results. This will help determine what disk drives are visible to the client. The next step is to create the label_list file. Use /System/Library/Filesystems/acfs.fs/Contents/examples/cvlabels.example as a template for your file. Or, use cvlabel with the -c option, in which case cvlabel will write on stdout the list of all devices found in a format compatible with a label_list file. Once a label_list file has been generated it must be edited to match the desired Xsan label updates. All LUNs included in the label_list file that are not allocated to the Xsan File System should be removed from the label_list file to prevent accidental overwriting of existing data. Once all updates to the label_list are complete cvlabel should be run using this file to apply label changes to the indicated LUNs. A final option for creating a label file is to use the -C option with a format string. This behaves the same as the -c option, except the format string is used to build template labels. The format string uses a printf like syntax where % followed by a letter is replaced by information obtained from the storage. The available format strings are %B size in sectors, %L lun number, %C controller id and %S serial number. Care should be taken to use a format which generates unique names for devices before using the output to label them. Certain RAID devices require special handling. Cvlabel uses the raid strings inquiry table to determine which devices require special handling. The default table (displayed with the -R option), can be overridden by a user supplied file /Library/Preferences/Xsan/raid-strings. Note: the -R option is not intended for general use and may be deprecated in the future. Only use when recommended by Apple Support.
|
cvlabel - Label Xsan Disk Devices (LUNs)
|
cvlabel -l [-agsv] [-F filter] cvlabel -L [-agv] [-F filter] cvlabel -j [-av] [-F filter] cvlabel -c [-T] [-F filter] cvlabel -C_format [-F filter] cvlabel -x cvlabel [-frRvw] [-q tag_q_depth] label_list cvlabel [-fw] -u_VolumeName cvlabel [-fw] -U_DeviceName cvlabel -D_VolumeName
|
-l, -L Use the -l option (short format) or the -L option (long format) to list usable disk devices on the system. -j Use the -j option (JSON format) to list usable disk devices on the system in a machine and human readable format. -u VolumeName Use the -u VolumeName option to unlabel the specified volume. -U DeviceName The -U DeviceName option is similar to the -u option, except that the path to the device special file is used instead of the label name. -s When used in conjunction with the -l option, the -s option prints the disk device serial #, which can be used to distinguish the difference between duplicate labels and multiple paths. -g When used in conjunction with the -l or -L options, the -g option also prints GUID information for EFI-labeled disks. The GUID includes a timestamp and the MAC address of the node that created the label. -a When used in conjunction with the -l or -L options, the -a option also prints unusable disk devices, along with a description of why they are unusable. This is usually due to a lack of OS support for large LUNs or an unsupported disk label format. -F filter When used in conjunction with the -c, -C, -l or -L options, the -F filter option will only list devices whose inquiry string contains the filter string. -v The -v option prints more information about the labeling process. Multiple -v options accumulate, providing more information often used for debugging the label process. -q The -q option can be used during labeling to set the Command Tag Queue Depth. By default, the Depth is set to 16. -f The -f option forces labeling and you will not be asked for confirmation before labeling (or unlabeling) a disk device. WARNING: errors in the Xsan label_list file can cause data loss. -c The -c option outputs a cvlabel format template file to stdout. This template file will reflect all disk devices visible to the local system. Use this template to build a cvlabel file. WARNING: Be sure to edit the template file to remove all devices which you do not want labeled. -T The -T option can be used in conjunction with the -c option to facilitate conversion of labels from the old VTOC format to the new EFI format. The output will be similar to the ordinary -c output, but devices that do not need conversion or cannot be safely converted will be output as comment lines, along with explanatory text. Only convertible devices are output normally. -D VolumeName The -D VolumeName option can be used to dump the label for VolumeName in ascii to stdout. Examining this output is useful when debugging labels. -r The -r option can be used to force a disk to be relabeled, even if there are no changes to the label information. Normally such disks are skipped. -R The -R option can be used to display the default raid strings inquiry table. Note that EFI labels are not supported on IRIX systems for older releases of the Xsan File System. -i The -i option is no longer supported. Labels should be in EFI format. -w The -w option tells cvlabel to wait for the completion of the disk scan that is requested after a disk label has been written or a volume has been unlabeled. The disk scan requests that the file system server update its internal device tables and the -w option ensures that the operation has been completed. Note that a disk scan may take a number of seconds on a large SAN or a SAN that is experiencing device errors. *WARNING* Use this program with extreme caution! Modifying a system disk's volume label may result in irreparable harm to your system. It may render the system inoperable and force you to repair the volume using the boot maintenance program. Only label disk devices which you are sure are to be used for the Xsan File System's storage area network. FILE FORMAT You may use the /System/Library/Filesystems/acfs.fs/Contents/examples/cvlabels.example file as a template. A label entry consists of two or three parameters on a single line. White space and comment lines are allowed. Comment lines are designated by using a pound sign (#) as the first non-white space character of the line. The label_list file format is as follows: <Xsan_label_name> <operating_system_device_name> [<sectors> [<type>]] Where: <Xsan_label_name> The <Xsan_label_name> parameter is the name of the disk as described in the FSM configuration file. The parameter must match a [Disk <Xsan_label_name>] entry. <operating_system_device_name> The <operating_system_device_name> is the device name of the complete disk device. NOTE: operating system device names may change after reboots and will differ per system. Always configure Xsan label files, and label devices in the same session. On Windows systems, the devices start as PhysicalDrive0 and increment up to the number of drives configured. <sectors> The <sectors> parameter is the number in 512-byte sectors that matches the [DiskType ...] configuration in the FSM configuration file. This is required for disks that must be configured smaller than their actual size. For example, MPIRE video disks must be under-configured to eliminate using the last zone of the disk. If <sectors> is not specified or is specified as -, then the cvlabel(8) program will use the entire available volume. <type> .sp .in +0.3i The <type> parameter is used to override the default label type, or to change the label type for a disk that already has a label. The value must be EFI for changing a VTOC label to an EFI label.
|
List all the disk devices in a system. rock # cvlabel -L /dev/sda [ATA ST500NM0011 PA08] MBR Controller 'default', Serial '5000C5004FDC5C85', Sector Size 512, Sectors Max 976754703 (500.1GB) /dev/mapper/mpathai [Quantum StorNext QX H205] SNFS-EFI "dexter1d1" Controller '208000C0FF193C0F', Serial '600C0FF00014658335219B5801000000', Sector Size 512, Sectors 39030873055 (20.0TB), Stripebreadth 0 [...] /dev/mapper/mpathap [DotHill DH4730 H205] unknown Controller '208000C0FF155519', Serial '600C0FF00019B6162739A65801000000', Sector Size 512, Sectors 18554669023 (9.5TB) [...] /dev/mapper/mpathan [Quantum QXS G22x] SNFS-EFI "snfs_data_bh-5600-1_L5" Controller '208000C0FF25E3DB', Serial '600C0FF0001BE2E0C9D94E5701000000', Sector Size 512, Sectors 140511467487 (71.9TB), Stripebreadth 3145728 Then create a template label file: rock # cvlabel -c >label_list The output file will include an entry for the 'unknown' disk: CvfsDisk_UNKNOWN /dev/mapper/mpathao # host 0 lun 3 sectors 18554669023 sector_size 512 inquiry [DotHill DH4730 H205] serial 600C0FF00019B6165E39A65801000000 Edit the label_list file, changing CvfsDisk_UNKNOWN to the desired label name: CvfsDisk_39 /dev/mapper/mpathao Now label the disk devices. Your label_list file must be specified on the command line. rock # cvlabel label_list *WARNING* This program will over-write volume labels on the devices specified in the file label_list. After execution, the devices will only be usable by the Xsan File System. You will have to re-partition the devices to use them on a different file system. Do you want to proceed? (Y / N) -> y /dev/mapper/mpathap [DotHill DH4730 H205] unknown Controller '208000C0FF155519', Serial '600C0FF00019B6162739A65801000000', Sector Size 512, Sectors 18554669023 (9.5TB) Do you want to label it SNFS-EFI - Name: CvfsDisk_39 Sectors: 18554669023 (Y / N) -> y New Volume Label -Device: /dev/mapper/mpathap SNFS Label: CvfsDisk_39 Sectors: 18554669023. Done. 1 source lines. 1 labels. The labels are done. List the disk devices again. rock # cvlabel -L /dev/sda [ATA ST500NM0011 PA08] MBR Controller 'default', Serial '5000C5004FDC5C85', Sector Size 512, Sectors Max 976754703 (500.1GB) /dev/mapper/mpathai [Quantum StorNext QX H205] SNFS-EFI "dexter1d1" Controller '208000C0FF193C0F', Serial '600C0FF00014658335219B5801000000', Sector Size 512, Sectors 39030873055 (20.0TB), Stripebreadth 0 [...] /dev/mapper/mpathap [DotHill DH4730 H205] SNFS-EFI "CvfsDisk_39" Controller '208000C0FF155519', Serial '600C0FF00019B6162739A65801000000', Sector Size 512, Sectors 18554669023 (9.5TB) [...] /dev/mapper/mpathan [Quantum QXS G22x] SNFS-EFI "snfs_data_bh-5600-1_L5" Controller '208000C0FF25E3DB', Serial '600C0FF0001BE2E0C9D94E5701000000', Sector Size 512, Sectors 140511467487 (71.9TB), Stripebreadth 3145728 Generate a label file of all LSI storage which uses the controller serial number and lun numbers as components of the labels. rock # cvlabel -C CVFS_%S_%L -F LSI > label_list Display to stdout the default raid strings inquiry table. rock # cvlabel -R # Raid inquiry string table # Controls interpretation of raid mode pages based on inquiry strings # # Allowed types: # LSI LSI (Engenio) Raid in AVT mode # Clariion Clariion (EMC) Raid in Auto trespass mode # Seagate Dual port Seagate JBODs # JBOD No special handling (Real JBOD or RDAC driver) # Quantum StorNext QX # Quantum QXS # String 1 String 2 Raid Type "DGC" "" Clariion "ENGENIO" "" LSI "IBM" "1722-600" LSI "IBM" "1742-900" LSI "IBM" "1814" LSI "IBM" "Universal Xport" LSI "LSI" "VirtualDisk" JBOD "LSI" "MegaRAID" JBOD "LSI" "ProFibre" JBOD "LSI" "Universal Xport" LSI "NETAPP" "Universal Xport" LSI "ENGENIO" "Universal Xport" LSI "LSI" "" LSI "SGI" "TP9300" LSI "SGI" "TP9400" LSI "SGI" "TP9500" LSI "SGI" "TP9700" LSI "SGI" "IS600" LSI "SGI" "IS500" LSI "SGI" "IS400" LSI "SGI" "IS300" LSI "STK" "FLEXLINE" LSI "STK" "OPENstorage" LSI "STK" "Universal Xport" LSI "STK" "BladeCtlr" LSI "Quantum StorNext QX" "" QX "Quantum QXS" "" QX "SEAGATE" "" Seagate Use the default raid strings inquiry table to seed a user-defined table. rock # cvlabel -R > /Library/Preferences/Xsan/raid-strings NOTES Some operating systems require a reboot after a disk is labeled or relabeled. It is recommended that Xsan nodes are rebooted after new labels are written or existing labels are updated. FILES /System/Library/Filesystems/acfs.fs/Contents/examples/cvlabels.example /System/Library/Filesystems/acfs.fs/Contents/examples/example.cfgx /Library/Preferences/Xsan/raid-strings SEE ALSO cvfs(8), snfs_config(5), mount_acfs(8) Xsan File System June 2019 CVLABEL(8)
|
BlueTool
| null | null | null | null | null |
sendmail
|
The Postfix sendmail(1) command implements the Postfix to Sendmail compatibility interface. For the sake of compatibility with existing applications, some Sendmail command-line options are recognized but silently ignored. By default, Postfix sendmail(1) reads a message from standard input until EOF or until it reads a line with only a . character, and arranges for delivery. Postfix sendmail(1) relies on the postdrop(1) command to create a queue file in the maildrop directory. Specific command aliases are provided for other common modes of operation: mailq List the mail queue. Each entry shows the queue file ID, message size, arrival time, sender, and the recipients that still need to be delivered. If mail could not be delivered upon the last attempt, the reason for failure is shown. The queue ID string is followed by an optional status character: * The message is in the active queue, i.e. the message is selected for delivery. ! The message is in the hold queue, i.e. no further delivery attempt will be made until the mail is taken off hold. This mode of operation is implemented by executing the postqueue(1) command. newaliases Initialize the alias database. If no input file is specified (with the -oA option, see below), the program processes the file(s) specified with the alias_database configuration parameter. If no alias database type is specified, the program uses the type specified with the default_database_type configuration parameter. This mode of operation is implemented by running the postalias(1) command. Note: it may take a minute or so before an alias database update becomes visible. Use the "postfix reload" command to eliminate this delay. These and other features can be selected by specifying the appropriate combination of command-line options. Some features are controlled by parameters in the main.cf configuration file. The following options are recognized: -Am (ignored) -Ac (ignored) Postfix sendmail uses the same configuration file regardless of whether or not a message is an initial submission. -B body_type The message body MIME type: 7BIT or 8BITMIME. -bd Go into daemon mode. This mode of operation is implemented by executing the "postfix start" command. -bh (ignored) -bH (ignored) Postfix has no persistent host status database. -bi Initialize alias database. See the newaliases command above. -bl Go into daemon mode. To accept only local connections as with Sendmail´s -bl option, specify "inet_interfaces = loopback" in the Postfix main.cf configuration file. -bm Read mail from standard input and arrange for delivery. This is the default mode of operation. -bp List the mail queue. See the mailq command above. -bs Stand-alone SMTP server mode. Read SMTP commands from standard input, and write responses to standard output. In stand-alone SMTP server mode, mail relaying and other access controls are disabled by default. To enable them, run the process as the mail_owner user. This mode of operation is implemented by running the smtpd(8) daemon. -bv Do not collect or deliver a message. Instead, send an email report after verifying each recipient address. This is useful for testing address rewriting and routing configurations. This feature is available in Postfix version 2.1 and later. -C config_file -C config_dir The path name of the Postfix main.cf file, or of its parent directory. This information is ignored with Postfix versions before 2.3. With Postfix version 3.2 and later, a non-default directory must be authorized in the default main.cf file, through the alternate_config_directories or multi_instance_directories parameters. With all Postfix versions, you can specify a directory pathname with the MAIL_CONFIG environment variable to override the location of configuration files. -F full_name Set the sender full name. This overrides the NAME environment variable, and is used only with messages that have no From: message header. -f sender Set the envelope sender address. This is the address where delivery problems are sent to. With Postfix versions before 2.1, the Errors-To: message header overrides the error return address. -G Gateway (relay) submission, as opposed to initial user submission. Either do not rewrite addresses at all, or update incomplete addresses with the domain information specified with remote_header_rewrite_domain. This option is ignored before Postfix version 2.3. -h hop_count (ignored) Hop count limit. Use the hopcount_limit configuration parameter instead. -I Initialize alias database. See the newaliases command above. -i When reading a message from standard input, don´t treat a line with only a . character as the end of input. -L label (ignored) The logging label. Use the syslog_name configuration parameter instead. -m (ignored) Backwards compatibility. -N dsn (default: 'delay, failure') Delivery status notification control. Specify either a comma-separated list with one or more of failure (send notification when delivery fails), delay (send notification when delivery is delayed), or success (send notification when the message is delivered); or specify never (don't send any notifications at all). This feature is available in Postfix 2.3 and later. -n (ignored) Backwards compatibility. -oAalias_database Non-default alias database. Specify pathname or type:pathname. See postalias(1) for details. -O option=value (ignored) Set the named option to value. Use the equivalent configuration parameter in main.cf instead. -o7 (ignored) -o8 (ignored) To send 8-bit or binary content, use an appropriate MIME encapsulation and specify the appropriate -B command-line option. -oi When reading a message from standard input, don´t treat a line with only a . character as the end of input. -om (ignored) The sender is never eliminated from alias etc. expansions. -o x value (ignored) Set option x to value. Use the equivalent configuration parameter in main.cf instead. -r sender Set the envelope sender address. This is the address where delivery problems are sent to. With Postfix versions before 2.1, the Errors-To: message header overrides the error return address. -R return Delivery status notification control. Specify "hdrs" to return only the header when a message bounces, "full" to return a full copy (the default behavior). The -R option specifies an upper bound; Postfix will return only the header, when a full copy would exceed the bounce_size_limit setting. This option is ignored before Postfix version 2.10. -q Attempt to deliver all queued mail. This is implemented by executing the postqueue(1) command. Warning: flushing undeliverable mail frequently will result in poor delivery performance of all other mail. -qinterval (ignored) The interval between queue runs. Use the queue_run_delay configuration parameter instead. -qIqueueid Schedule immediate delivery of mail with the specified queue ID. This option is implemented by executing the postqueue(1) command, and is available with Postfix version 2.4 and later. -qRsite Schedule immediate delivery of all mail that is queued for the named site. This option accepts only site names that are eligible for the "fast flush" service, and is implemented by executing the postqueue(1) command. See flush(8) for more information about the "fast flush" service. -qSsite This command is not implemented. Use the slower "sendmail -q" command instead. -t Extract recipients from message headers. These are added to any recipients specified on the command line. With Postfix versions prior to 2.1, this option requires that no recipient addresses are specified on the command line. -U (ignored) Initial user submission. -V envid Specify the envelope ID for notification by servers that support DSN. This feature is available in Postfix 2.3 and later. -XV (Postfix 2.2 and earlier: -V) Variable Envelope Return Path. Given an envelope sender address of the form owner-listname@origin, each recipient user@domain receives mail with a personalized envelope sender address. By default, the personalized envelope sender address is owner-listname+user=domain@origin. The default + and = characters are configurable with the default_verp_delimiters configuration parameter. -XVxy (Postfix 2.2 and earlier: -Vxy) As -XV, but uses x and y as the VERP delimiter characters, instead of the characters specified with the default_verp_delimiters configuration parameter. -v Send an email report of the first delivery attempt (Postfix versions 2.1 and later). Mail delivery always happens in the background. When multiple -v options are given, enable verbose logging for debugging purposes. -X log_file (ignored) Log mailer traffic. Use the debug_peer_list and debug_peer_level configuration parameters instead. SECURITY By design, this program is not set-user (or group) id. However, it must handle data from untrusted, possibly remote, users. Thus, the usual precautions need to be taken against malicious inputs. DIAGNOSTICS Problems are logged to syslogd(8) and to the standard error stream. ENVIRONMENT MAIL_CONFIG Directory with Postfix configuration files. MAIL_VERBOSE (value does not matter) Enable verbose logging for debugging purposes. MAIL_DEBUG (value does not matter) Enable debugging with an external command, as specified with the debugger_command configuration parameter. NAME The sender full name. This is used only with messages that have no From: message header. See also the -F option above. CONFIGURATION PARAMETERS The following main.cf parameters are especially relevant to this program. The text below provides only a parameter summary. See postconf(5) for more details including examples. COMPATIBILITY CONTROLS Available with Postfix 2.9 and later: sendmail_fix_line_endings (always) Controls how the Postfix sendmail command converts email message line endings from <CR><LF> into UNIX format (<LF>). TROUBLE SHOOTING CONTROLS The DEBUG_README file gives examples of how to trouble shoot a Postfix system. debugger_command (empty) The external command to execute when a Postfix daemon program is invoked with the -D option. debug_peer_level (2) The increment in verbose logging level when a remote client or server matches a pattern in the debug_peer_list parameter. debug_peer_list (empty) Optional list of remote client or server hostname or network address patterns that cause the verbose logging level to increase by the amount specified in $debug_peer_level. ACCESS CONTROLS Available in Postfix version 2.2 and later: authorized_flush_users (static:anyone) List of users who are authorized to flush the queue. authorized_mailq_users (static:anyone) List of users who are authorized to view the queue. authorized_submit_users (static:anyone) List of users who are authorized to submit mail with the sendmail(1) command (and with the privileged postdrop(1) helper command). RESOURCE AND RATE CONTROLS bounce_size_limit (50000) The maximal amount of original message text that is sent in a non-delivery notification. fork_attempts (5) The maximal number of attempts to fork() a child process. fork_delay (1s) The delay between attempts to fork() a child process. hopcount_limit (50) The maximal number of Received: message headers that is allowed in the primary message headers. queue_run_delay (300s) The time between deferred queue scans by the queue manager; prior to Postfix 2.4 the default value was 1000s. FAST FLUSH CONTROLS The ETRN_README file describes configuration and operation details for the Postfix "fast flush" service. fast_flush_domains ($relay_domains) Optional list of destinations that are eligible for per-destination logfiles with mail that is queued to those destinations. VERP CONTROLS The VERP_README file describes configuration and operation details of Postfix support for variable envelope return path addresses. default_verp_delimiters (+=) The two default VERP delimiter characters. verp_delimiter_filter (-=+) The characters Postfix accepts as VERP delimiter characters on the Postfix sendmail(1) command line and in SMTP commands. MISCELLANEOUS CONTROLS alias_database (see 'postconf -d' output) The alias databases for local(8) delivery that are updated with "newaliases" or with "sendmail -bi". command_directory (see 'postconf -d' output) The location of all postfix administrative commands. config_directory (see 'postconf -d' output) The default location of the Postfix main.cf and master.cf configuration files. daemon_directory (see 'postconf -d' output) The directory with Postfix support programs and daemon programs. default_database_type (see 'postconf -d' output) The default database type for use in newaliases(1), postalias(1) and postmap(1) commands. delay_warning_time (0h) The time after which the sender receives a copy of the message headers of mail that is still queued. import_environment (see 'postconf -d' output) The list of environment parameters that a privileged Postfix process will import from a non-Postfix parent process, or name=value environment overrides. mail_owner (postfix) The UNIX system account that owns the Postfix queue and most Postfix daemon processes. queue_directory (see 'postconf -d' output) The location of the Postfix top-level queue directory. remote_header_rewrite_domain (empty) Don't rewrite message headers from remote clients at all when this parameter is empty; otherwise, rewrite message headers and append the specified domain name to incomplete addresses. syslog_facility (mail) The syslog facility of Postfix logging. syslog_name (see 'postconf -d' output) A prefix that is prepended to the process name in syslog records, so that, for example, "smtpd" becomes "prefix/smtpd". Postfix 3.2 and later: alternate_config_directories (empty) A list of non-default Postfix configuration directories that may be specified with "-c config_directory" on the command line (in the case of sendmail(1), with "-C config_directory"), or via the MAIL_CONFIG environment parameter. multi_instance_directories (empty) An optional list of non-default Postfix configuration directories; these directories belong to additional Postfix instances that share the Postfix executable files and documentation with the default Postfix instance, and that are started, stopped, etc., together with the default Postfix instance. FILES /var/spool/postfix, mail queue /etc/postfix, configuration files SEE ALSO pickup(8), mail pickup daemon qmgr(8), queue manager smtpd(8), SMTP server flush(8), fast flush service postsuper(1), queue maintenance postalias(1), create/update/query alias database postdrop(1), mail posting utility postfix(1), mail system control postqueue(1), mail queue control syslogd(8), system logging README_FILES Use "postconf readme_directory" or "postconf html_directory" to locate this information. DEBUG_README, Postfix debugging howto ETRN_README, Postfix ETRN howto VERP_README, Postfix VERP howto LICENSE The Secure Mailer license must be distributed with this software. AUTHOR(S) Wietse Venema IBM T.J. Watson Research P.O. Box 704 Yorktown Heights, NY 10598, USA Wietse Venema Google, Inc. 111 8th Avenue New York, NY 10011, USA SENDMAIL(1)
|
sendmail - Postfix to Sendmail compatibility interface
|
sendmail [option ...] [recipient ...] mailq sendmail -bp newaliases sendmail -I
| null | null |
systemkeychain
|
The systemkeychain can be used to create a system keychain, make it possible for a keychain to unlock another keychain, or test unlocking a keychain. The options are as follows: -C Create a keychain and establish it in the system as the primary system keychain whose unlocking is automatically handled by the system. The new keychain is empty. If the optional password argument is given, the keychain can be also be unlocked with that; otherwise, the keychain has no password and can only be unlocked by the system. The optional password option is generally used for testing purposes, and using it is not recommended. -s Extract the master secret from source keychain(s) and install them in a destination keychain to allow unlocking. -t Test unlocking the system keychain. -k systemKeychain Use a keychain other than the default as the destination system keychain. -c Create the target keychain if necessary. -f Force creation of a system keychain or overwriting of an existing key for keychain unlocking keychain operations. -v Turn on verbose mode. By default, systemkeychain works with the keychain file stored at /Library/Keychains/System.keychain . Use of the -k option can specify a different target file. Use of the -s option allows keychains to be setup to unlock other keychains. Chains of keychain unlocks can be setup in this manner to make a series of keychains unlock while only needing to manually unlock the first one. This functionality can be verified with the -t (test unlock) option. FILES /Library/Keychains/System.keychain DIAGNOSTICS The systemkeychain utility exits 0 on success, and >0 if an error occurs. HISTORY The systemkeychain command appeared in Mac OS 10.2.0 . macOS 14.5 March 14, 2006 macOS 14.5
|
systemkeychain – creates system keychains and allows keychains to unlock keychains
|
systemkeychain [-fv] [-k filename] [-C] [password] systemkeychain [-fvc] [-k filename] [-s] [file ...] systemkeychain [-v] [-k filename] [-t]
| null | null |
kcditto
|
kcditto is a helper tool for the staging of kext collection files. It looks for kext collection files on volume where the kcditto binary exists, and copies all the boot kext collections into the preboot volume where efiboot can find them. FILES /usr/local/sbin/kcidtto SEE ALSO kmutil(8), kernelmanagerd(8), kextcache(8) macOS 14.5 February 23, 2020 macOS 14.5
|
kcditto – macOS kernel management helper tool DEPRECATED Please use bless.
| null | null | null |
slapcat
|
Slapcat is used to generate an LDAP Directory Interchange Format (LDIF) output based upon the contents of a slapd(8) database. It opens the given database determined by the database number or suffix and writes the corresponding LDIF to standard output or the specified file. Databases configured as subordinate of this one are also output, unless -g is specified. The entry records are presented in database order, not superior first order. The entry records will include all (user and operational) attributes stored in the database. The entry records will not include dynamically generated attributes (such as subschemaSubentry). The output of slapcat is intended to be used as input to slapadd(8). The output of slapcat cannot generally be used as input to ldapadd(1) or other LDAP clients without first editing the output. This editing would normally include reordering the records into superior first order and removing no-user-modification operational attributes.
|
slapcat - SLAPD database to LDIF utility
|
/usr/sbin/slapcat [-afilter] [-bsuffix] [-c] [-ddebug-level] [-fslapd.conf] [-Fconfdir] [-g] [-HURI] [-lldif-file] [-ndbnum] [-ooption[=value]] [-ssubtree-dn] [-v]
|
-a_filter Only dump entries matching the asserted filter. For example slapcat -a \ "(!(entryDN:dnSubtreeMatch:=ou=People,dc=example,dc=com))" will dump all but the "ou=People,dc=example,dc=com" subtree of the "dc=example,dc=com" database. Deprecated; use -H ldap:///???(filter) instead. -b_suffix Use the specified suffix to determine which database to generate output for. The -b cannot be used in conjunction with the -n option. -c Enable continue (ignore errors) mode. Multiple occorrences of -c make slapcat(8) try harder. -d_debug-level Enable debugging messages as defined by the specified debug-level; see slapd(8) for details. -f_slapd.conf Specify an alternative slapd.conf(5) file. -F_confdir specify a config directory. If both -f and -F are specified, the config file will be read and converted to config directory format and written to the specified directory. If neither option is specified, an attempt to read the default config directory will be made before trying to use the default config file. If a valid config directory exists then the default config file is ignored. -g disable subordinate gluing. Only the specified database will be processed, and not its glued subordinates (if any). -H URI use dn, scope and filter from URI to only handle matching entries. -l_ldif-file Write LDIF to specified file instead of standard output. -n_dbnum Generate output for the dbnum-th database listed in the configuration file. The config database slapd-config(5), is always the first database, so use -n 0 to select it. The -n cannot be used in conjunction with the -b option. -o_option[=value] Specify an option with a(n optional) value. Possible generic options/values are: syslog=<subsystems> (see `-s' in slapd(8)) syslog-level=<level> (see `-S' in slapd(8)) syslog-user=<user> (see `-l' in slapd(8)) ldif-wrap={no|<n>} n is the number of columns allowed for the LDIF output (n equal to 0 uses the default, corresponding to 76). Use no for no wrap. -s_subtree-dn Only dump entries in the subtree specified by this DN. Implies -b subtree-dn if no -b or -n option is given. Deprecated; use -H ldap:///subtree-dn instead. -v Enable verbose mode. LIMITATIONS For some backend types, your slapd(8) should not be running (at least, not in read-write mode) when you do this to ensure consistency of the database. It is always safe to run slapcat with the slapd-bdb(5), slapd-hdb(5), and slapd-null(5) backends.
|
To make a text backup of your SLAPD database and put it in a file called ldif, give the command: /usr/sbin/slapcat -l ldif SEE ALSO ldap(3), ldif(5), slapadd(8), ldapadd(1), slapd(8) "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/) ACKNOWLEDGEMENTS OpenLDAP Software is developed and maintained by The OpenLDAP Project <http://www.openldap.org/>. OpenLDAP Software is derived from University of Michigan LDAP 3.3 Release. OpenLDAP 2.4.28 2011/11/24 SLAPCAT(8C)
|
ipconfig
|
ipconfig is a utility that communicates with the IPConfiguration agent to retrieve and set IP configuration parameters. It should only be used in a test and debug context. Using it for any other purpose is strongly discouraged. Public API's in the SystemConfiguration framework are currently the only supported way to access and control the state of IPConfiguration. The IPConfiguration agent is responsible for configuring and managing the IPv4 and IPv6 addresses on direct, connectionless interfaces such as ethernet and Wi-Fi. The IPConfiguration agent is a program bundle that is loaded and executed by the configd(8) process. The IPConfiguration agent implements the client side of the DHCP and BOOTP protocols described in RFC951, RFC1542, RFC2131, and RFC2132. It also assigns and maintains static IP addresses. It may also allocate and assign a link-local IP address if DHCP fails to acquire an IP address. The IPConfiguration agent enables and controls the IPv6 SLAAC (RFC 4862) state in the kernel, and also handles statically configured IPv6 addresses. The agent implements the client side of the DHCPv6 protocol (RFC 3315) and supports both stateless and stateful operation. In all cases, the IPConfiguration agent performs IP address conflict detection before assigning an IP address to an interface. COMMANDS The ipconfig utility provides several commands: waitall Blocks until all network services have completed configuring, or have timed out in the process of configuring. This is only useful for initial system start-up time synchronization for legacy network services that are incapable of dealing with dynamic network configuration changes. getifaddr interface-name Prints to standard output the IP address for the first network service associated with the given interface. The output will be empty if no service is currently configured or active on the interface. ifcount Prints the number of interfaces that IPConfiguration is capable of configuring. The value that's printed will not change unless relevant network interfaces are either added to or removed from the system. getoption interface-name (option-name | option-code) Prints the BOOTP/DHCP option with the given name or option code integer value. See bootpd(8) for option code names. If an option has multiple values e.g. domain_name_server, only the first value is printed. getpacket interface-name Prints to standard output the DHCP/BOOTP packet that the client accepted from the DHCP/BOOTP server. This command is useful to check what the server provided, and whether the values are sensible. This command outputs nothing if DHCP/BOOTP is not active on the interface, or the attempt to acquire an IP address was unsuccessful. getv6packet interface-name Prints to standard output the latest DHCPv6 packet that the client accepted from the DHCPv6 server. In the case of stateful DHCPv6, it corresponds to the last packet from the server that contained addressing information. This command is useful to check what the server provided, and whether the values are sensible. This command outputs nothing if DHCPv6 is not active on the interface. getra interface-name Prints to standard output the latest IPv6 Router Advertisement packet that the client accepted from an advertising router. This command outputs nothing if no router is present. getsummary interface-name Prints to standard output a summary of the current IPConfiguration state over the specific interface. getdhcpduid Prints to standard output the DHCP DUID, if one has been established. getdhcpiaid interface-name Prints to standard output the DHCP IA_ID for the specific interface, if the interface is configured for IPv6 and the DHCP DUID has been established. set interface-name NONE set interface-name (DHCP | BOOTP) set interface-name (MANUAL | INFORM) ip-address subnet-mask set interface-name NONE-V6 set interface-name AUTOMATIC-V6 set interface-name MANUAL-V6 ipv6-address prefix-length set interface-name 6TO4 Sets the interface to have a new temporary network service of the given type. Any existing services on the interface for the particular protocol (IPv4 or IPv6) are first de-configured before the new service is instantiated. If NONE is specified, all existing IPv4 services are de- configured. If NONE-V6 is specified, all existing IPv6 services are de-configured. DHCP and BOOTP require no additional arguments. The IP address, subnet mask, router, and DNS information are retrieved automatically. Both MANUAL and INFORM require the specification of an IP address ip-address and a subnet mask subnet-mask. The INFORM service configures the IP address statically like MANUAL, but then broadcasts DHCP INFORM packets to retrieve DHCP option information. If the DHCP server responds and supplies a subnet mask, that subnet mask is used instead of the specified subnet-mask. AUTOMATIC-V6 requires no additional arguments. The IPv6 address, prefix length and router are retrieved automatically. MANUAL-V6 requires the specification of the IPv6 address ipv6-address and a prefix length prefix-length. 6TO4 only works on Six To Four (IFT_STF) interfaces e.g. stf0. If it is specified on a non-IFT_STF interface, it has the same effect as specifying NONE-V6. The set command requires root privileges. Note: The set command is very useful for debugging, but it can't be used to configure a persistent service. The temporary services that are created only remain until the next network configuration change occurs. See scselect(8). setverbose level Enables or disables verbose mode logging in the IPConfiguration agent. Specify a level value of 0 to disable verbose logging, the default. Specify a value of 1 to enable verbose logging. This setting is persistent across boots of the operating system. All logging generated by the IPConfiguration agent can be filtered using the "com.apple.IPConfiguration" subsystem identifier. The setverbose command requires root privileges.
|
ipconfig – view and control IP configuration state
|
ipconfig waitall ipconfig getifaddr interface-name ipconfig ifcount ipconfig getoption interface-name (option-name | option-code) ipconfig getpacket interface-name ipconfig getv6packet interface-name ipconfig getra interface-name ipconfig getsummary interface-name ipconfig getsummary interface-name ipconfig getdhcpduid ipconfig getdhcpiaid interface-name ipconfig setverbose level ipconfig set interface-name NONE ipconfig set interface-name (DHCP | BOOTP) ipconfig set interface-name (MANUAL | INFORM) ip-address subnet-mask ipconfig set interface-name NONE-V6 ipconfig set interface-name AUTOMATIC-V6 ipconfig set interface-name MANUAL-V6 ipv6-address prefix-length ipconfig set interface-name 6TO4
| null |
# ipconfig getpacket en0 op = BOOTREPLY htype = 1 dp_flags = 0 hlen = 6 hops = 0 xid = 1956115059 secs = 0 ciaddr = 0.0.0.0 yiaddr = 192.168.4.10 siaddr = 192.168.4.1 giaddr = 0.0.0.0 chaddr = 0:3:93:7a:d7:5c sname = dhcp.mycompany.net file = options: Options count is 10 dhcp_message_type (uint8): ACK 0x5 server_identifier (ip): 192.168.4.1 lease_time (uint32): 0x164a subnet_mask (ip): 255.255.255.0 router (ip_mult): {192.168.4.1} domain_name_server (ip_mult): {192.168.4.1} domain_name (string): mycompany.net end (none): # ipconfig getoption en0 router 192.168.4.1 SEE ALSO configd(8), bootpd(8), scselect(8) HISTORY The ipconfig command first appeared in Mac OS X Version 10.0 Public Beta. Mac OS X August 1, 2022 Mac OS X
|
auditreduce
|
The auditreduce utility selects records from the audit trail files based on the specified criteria. Matching audit records are printed to the standard output in their raw binary form. If no file argument is specified, the standard input is used by default. Use the praudit(1) utility to print the selected audit records in human-readable form. The options are as follows: -A Select all records. -a YYYYMMDD[HH[MM[SS]]] Select records that occurred after or on the given datetime. -b YYYYMMDD[HH[MM[SS]]] Select records that occurred before the given datetime. -c flags Select records matching the given audit classes specified as a comma separated list of audit flags. See audit_control(5) for a description of audit flags. -d YYYYMMDD Select records that occurred on a given date. This option cannot be used with -a or -b. -e euid Select records with the given effective user ID or name. -f egid Select records with the given effective group ID or name. -g rgid Select records with the given real group ID or name. -j id Select records having a subject token with matching ID. -m event Select records with the given event name or number. This option can be used more then once to select records of multiple event types. See audit_event(5) for a description of audit event names and numbers. -o object=value file Select records containing path tokens, where the pathname matches one of the comma delimited extended regular expression contained in given specification. Regular expressions which are prefixed with a tilde (‘~’) are excluded from the search results. These extended regular expressions are processed from left to right, and a path will either be selected or deslected based on the first match. Since commas are used to delimit the regular expressions, a backslash (‘\’) character should be used to escape the comma if it is a part of the search pattern. msgqid Select records containing the given message queue ID. pid Select records containing the given process ID. semid Select records containing the given semaphore ID. shmid Select records containing the given shared memory ID. -r ruid Select records with the given real user ID or name. -U Use unbuffered output. This option is automatically set when the input file is a character device (e.g. /dev/auditpipe), allowing records to be fully processed as they are generated. -u auid Select records with the given audit ID. -v Invert sense of matching, to select records that do not match.
|
auditreduce – select records from audit trail files SYNOPSIS (NOW DEPRECATED) auditreduce [-A] [-a YYYYMMDD[HH[MM[SS]]]] [-b YYYYMMDD[HH[MM[SS]]]] [-c flags] [-d YYYYMMDD] [-e euid] [-f egid] [-g rgid] [-j id] [-m event] [-o object=value] [-r ruid] [-U] [-u auid] [-v] [file ...]
| null | null |
To select all records associated with effective user ID root from the audit log /var/audit/20031016184719.20031017122634: auditreduce -e root \ /var/audit/20031016184719.20031017122634 To select all setlogin(2) events from that log: auditreduce -m AUE_SETLOGIN \ /var/audit/20031016184719.20031017122634 Output from the above command lines will typically be piped to a new trail file, or via standard output to the praudit(1) command. Select all records containing a path token where the pathname contains /etc/master.passwd: auditreduce -o file="/etc/master.passwd" \ /var/audit/20031016184719.20031017122634 Select all records containing path tokens, where the pathname is a TTY device: auditreduce -o file="/dev/tty[a-zA-Z][0-9]+" \ /var/audit/20031016184719.20031017122634 Select all records containing path tokens, where the pathname is a TTY except for /dev/ttyp2: auditreduce -o file="~/dev/ttyp2,/dev/tty[a-zA-Z][0-9]+" \ /var/audit/20031016184719.20031017122634 SEE ALSO praudit(1), audit_control(5), audit_event(5) HISTORY The OpenBSM implementation was created by McAfee Research, the security division of McAfee Inc., under contract to Apple Computer Inc. in 2004. It was subsequently adopted by the TrustedBSD Project as the foundation for the OpenBSM distribution. AUTHORS This software was created by McAfee Research, the security research division of McAfee, Inc., under contract to Apple Computer Inc. Additional authors include Wayne Salamon, Robert Watson, and SPARTA Inc. The Basic Security Module (BSM) interface to audit records and audit event stream format were defined by Sun Microsystems. macOS 14.5 January 24, 2004 macOS 14.5
|
cvadmin
|
cvadmin is an interactive command used for general purpose administration of an Xsan volume including: 1. displaying file system and client status 2. activating a file system currently in stand-by mode 3. viewing storage pool attributes 4. enabling File System Manager (FSM) tracing 5. displaying disk and path information for the local system 6. forcing FSM failover 7. fetching FSM usage and performance statistics 8. temporarily enabling or disabling global file locking 9. generating a report of open files 10. listing currently held file locks 11. starting, restarting and stopping of daemon processes 12. resetting RPL information
|
cvadmin - Administer an Xsan File System
|
cvadmin [-H FSMHostName] [-F VolumeName] [-M] [-n] [-x] [-f filename] [-e command1 -e command2...]
|
Invoke cvadmin to start the interactive session and list the running File System Managers (FSMs). (Note: Xsan system services must be started prior to running cvadmin. In particular, the local fsmpm(8) process must be active.) The initial output shows the running FSMs grouped by the cluster in which they are located. The hostnames or IP addresses are those that are advertised to clients. When more than one location is listed, one or more these will be marked as preferred. This means that this address is on the metadata network and should be used, if possible, by a client to make a connection to the FSM. The remaining addresses can be used if a connection can not be made using a preferred address. Note: An administrator can filter out addresses that are not to be advertised by using the snfs_metadata_network_filter.json(5) configuration file. Then (optionally) use the select command described below to pick an FSM to connect to. Once connected, the command will display basic information about the selected volume and prompt for further commands. Note that a few commands such as paths, disks, start, and stop require information obtained from the local fsmpm(8) only, so there is is no need to select an FSM prior to using them. USAGE -H FSMHostName Connect to the FSM located on the machine FSMHostName. By default cvadmin will attempt to connect to an FSM located on the local machine. -F VolumeName Automatically set the volume VolumeName as the active volume in cvadmin. -M When listing file systems with the select command, display [managed] next to each file system with DataMigration enabled. This option is currently only intended for use by support personnel. -f filename Read commands from filename -e command Execute command(s) and exit -n Show numerical addresses instead of trying to determine symbolic host -x Enable extended commands. COMMANDS The cvadmin commands can be used to display and modify the Xsan active configuration. When a modification is made, it exists only as long as the FSM is running. More permanent changes can be made in the configuration file. Refer to the snfs_config(5) man page for details. The following commands are supported. The syntax for volume_name is: name[@cluster[/addom]] activate volume_name [hostname_or_IP_address] Activate a volume volume_name. This command may cause an FSM to activate. If the FSM is already active, no action is taken. activate volume_name number_of_votes Apple Internal only. Bypass the election system and attempt to activate the fsm on this node. cluster select [N|[+]cluster_name] Select a cluster to be used by other commands when the cluster name isn't explicitly given with the FSM name. Normally only a known cluster name can be selected, but preceding it with a '+' will force an unknown cluster name to be used. A cluster name of none or 0 will de-select the currently selected cluster name. Using no arguments or just select will show all known clusters. Cluster_name is [@]cluster[/addom]. cluster filter [N|cluster_name] Set a filter for the output of the select command. When a cluster filter is set, only FSMs in that cluster will be displayed by select. The filter can be set to all the clusters in an administrative domain by using A cluster name of none or 0 will disable the filter. Using no arguments or just filter will show all known clusters. Cluster_name is [@]cluster[/addom]. coord [[on] hostname_or_IP_address] Display the list of NSS coordinators on the local host or on the specified host. clientunmount gentle_time_in_seconds clientunmount hard gentle_time_in_seconds force_time_in_seconds Instruct clients of the selected volume to unmount. The first form of the command waits gentle_time_in_seconds seconds for clients to unmount the volume. Clients receive a message from the fsm directing them to normally unmount the volume. During this time, no new client connections are permitted. If all clients unmount within that time, the fsm continues with new connections forbidden. In the second form of the command, the fsm moves to a second stage if any clients fail to unmount. In this stage, clients are instructed to unmount the volume forcibly. The fsm waits force_time_in_seconds seconds, and then completes the operation. Client connections remain forbidden at the end of this operation. After completing this command, the administrator should stop the volume. debug [[+|-] flag [ ... ]] View or set the File System Manager's debugging flags. Entering the command with no flag will return current settings, the location of the FSM log file and a legend describing what each setting does. By entering the command with a flag list, the FSM Debugging Flags will be set accordingly. Each flag can be either a name or numeric value. Names will be mapped to their numeric value, and may be abbreviated as long as they remain unique. Numeric values are specified using a standard decimal or hexadecimal (0x) value of up to 32 bits. Using '+' or '-' enables ('+') or disables ('-') only the selected flags, leaving all other flags unchanged. NOTE - Setting Debugging Flags will severely impact the FSM's performance! Do this only when directed by a Apple specialist. discon Forcefully disconnect a client from the FSM. With no arguments, discon displays the list of connected clients. When supplied an index, discon will immediately disconnect the specified client. Only use when recommended by Technical Support. Also see the "repblocked" command. disks [refresh] Display the Xsan disk volumes local to the system that cvadmin is attached to. Using the optional refresh argument will force the fsmpm to re-scan all volumes before responding. If the fsmpm's view of the disks in any file system changes compared with the FSM's view of that client's disks as a result of the refresh, a disconnect and reconnect to the FSM will take place to resynchronise the file system state. disks [refresh] fsm Display the Xsan meta-data disk volumes in use by the fsm. If the optional refresh argument is used, additional paths to these volumes may be added by the fsm. fail [volume_name|index_number] Initiate an FSM Failover of volume volume_name. This command may cause a stand-by FSM to activate. If an FSM is already active, the FSM will shut down. A stand-by FSM will then take over. If a stand-by FSM is not available the primary FSM will re-activate after failover processing is complete. files Report counts of files, directories, symlinks and other objects which are anchored by a user type inode. These include named streams, block and character device files, fifos or pipes and named sockets. If the file system is undergoing conversion to StorNext 5.0, conversion progress is displayed and counters reflect the count of converted objects. fsmlist [volume_name] [ on hostname_or_IP_address] Display the state of FSM processes, running or not. Optionally specify a single volume_name to display. Optionally specify the host name or IP address of the system on which to list the FSM processes. filelocks Query cluster-wide file/record lock enforcement. Currently cluster-wide file locks are automatically used on Unix. Windows file/record locks are optional. If enabled, byte-range file locks are coordinated through the FSM, allowing a lock set by one client to block overlapping locks by other clients. If disabled, then byte-range locks are local to a client and do not prevent other clients from getting byte-range locks on a file, however they do prevent overlapping lock attempts on the same client. help (?) The help or ? command will display a command usage summary. latency-test [index_number|all] [seconds] Run an I/O latency test between the FSM process and one client or all clients. The default test duration is 2 seconds. metadata Report metadata usage. Also provide an estimate on the value of bufferCacheSize that will allow all metadata to be cached. mdarchive [status|backup|rebuild|prune] Run commands targeting the metadata archive associated with the selected FSM. Running mdarchive without command arguments will display the full path location of the metadata archive. mdarchive status The status command prints the progress of the current metadata archive activity, if any. If generating a new metadata archive or restoring an existing one, the percentage complete will be displayed. Otherwise, the current update backlog is displayed. mdarchive rebuild [new] If metadataArchiveDays is set to zero then the rebuild command will force the FSM to discard the existing metadata archive and generate a new one, otherwise the FSM will rebuild the existing metadata archive in a way that will preserve history across the rebuild. Rebuilds can be performed online while clients are active in the file system. When metadataArchiveDays is set to a value greater than zero, requesting a new rebuild will cause the FSM to delete the current metadata archive before starting the rebuild. All metadata history that existed prior to the new rebuild will be lost but the rebuild will shrink the mdarchive down to its minimum size. Requesting a new rebuild has no effect when metadataArchiveDays is set to zero because the existing metadata archive is always deleted before starting the rebuild in that case. WARNING: When using the new argument to the rebuild command, all metadata history that existed prior to the rebuild will be lost. This will prevent external applications like snaudit and snhistory from reporting events that occurred prior to the rebuild and will prevent snrecover from recovering files that were deleted prior to the rebuild. mdarchive rebuild wait Wait for an ongoing rebuild to complete and report status periodically. mdarchive backup [full|partial] pathname For an FSM with a current mdarchive, request a backup copy be generated as a compressed tar file. The pathname must specify an existing directory on the FSM node and include the file name to be created. A full dump contains all the content, a partial dump contains all the content changed since the last backup. mdarchive backup wait Wait for an ongoing mdarchive backup to complete and report progress periodically. mdarchive prune The prune command will force the removal of expired historical data from the metadata archive. This command is ignored and a message is written to the system log file if metadataArchiveDays is set to zero in the configuration file or if it is issued while an mdarchive build, file recovery, or metadata restore is in progress. mdarchive throttle set <threshold> <delay> Set the threshold (number of bundles) and delay (milliseconds) for throttling incoming metadata changes to allow an update backlog to dissipate. Throttling is disabled when delay is equal to 0 which is the default. In addition to using the cvadmin mdarchive command, throttling can be set at FSM startup using the MDARCHIVE_THROTTLE_THRESHOLD and MDARCHIVE_THROTTLE_DELAY environment variables. Note: this option is not intended for general use. Only enable throttling when recommended by Technical Support. Note: the throttling capability may change or be removed in a future release. mdarchive throttle show Display current mdarchive throttle settings. See "mdarchive throttle set" above. paths Display the Xsan disk volumes visible to the local system. The display is grouped by <controller> identity, and will indicate the "Active" or "Passive" nature of the path if the Raid Controller has been recognized as configured in Active/Active mode with AVAT enabled. proxy [long] Display Disk Proxy servers and optionally display the disks they serve for this volume. proxy who hostname The "who" option displays all proxy connections for the specified host. qbm trace [clientid] Create a QBM internal trace file on the MDC. If clientid is specified (where clientid is the client's login id), a client trace is also also generated. This command creates an SNQBM_xxx file in the debug directory. Currently, only Windows clients generate internal traces. This command is for Quantum use only. qbm show stripe-group-num Show the QBM allocation table for a stripe group given the stripe-group index. All bandwidth (BW) is in MB/sec. The display includes the following sub-tables: Stripe Group (SG) Table: SG max (capacity), BW currently free, the total BW in the reserve pools, and the total over- subscripted (over capacity) amount. Priority (Pri) Table: table class name, count of clients in the priority, total bandwidth allocated at this priority, minimum BW, maximum BW, extra (over min) BW, reserved BW used/total reserve allocated to this priority, and current BW used. Client Entry: list number, IP address, client login number, bandwidth information - minimum, maximum and current BW, restore BW, flag (l - client asked for less, m - client asked for more, g - client given more BW over minimum BW). qbm newconfig Re-read the <_file_system_name_>_qbm.conf file and update the clients. qos Display per-stripe group QOS statistics. Per-client QoS statistics are also displayed under each qos-configured stripe group. quit This command will disconnect cvadmin from the FSM and exit. ras enq [ nomerge ] event "detail string" Generate an SNFS RAS event. If "nomerge" is specified, multiple instances of the RAS event are not merged into a single ticket. For internal use only. ras enq [ nomerge ] event reporting_FRU violating_FRU "detail string" Generate a generic RAS event. If "nomerge" is specified, multiple instances of the RAS event are not merged into a single ticket. For internal use only. regapigw Register the filesystem with the fsmpm to enable registration with an api gateway. To be used when the fsmpm is not aware of this filesystem for api gateway registration purposes. This can be confirmed using the 'snrest gateway status -d' command and noting the absence of the filesystem. The fsmpm performs the api gateway registration on behalf of the filesystem. This situation should not occur, but if it does this command allows recovery from the situation without requiring a restart of the filesystem. repblocked Generate a report of files that may be causing open operations to block due to an unresponsive client that is slow to acknowledge a request to change state. Such clients should be inspected to determine whether there is a reason for their lack of response. One common cause of unresponsiveness is that Xsan clients have entered sleep mode. The settings on these clients should be adjusted so they never sleep. If the client is known to be hung, the connection to the FSM can be reset using the discon command. repfl Generate a report that displays the file locks currently held. Note: this command is only intended for debugging purposes by support personnel. In future releases, the format of the report may change or the command may be removed entirely. Running the repfl command will write out a report file and display the output filename. repof Generate a report that displays all files that are currently open on each Xsan client. Running the repof command will write out a report file and display the output filename containing that report. The information displayed for each file is: the pathname, inode number, the number of "writers" (which is the # of times this client has opened the file for write -- usually 1 or 0), and stat information. Next a line is printed showing the open state across all clients. The open state contains: the count of different clients with this file open, the # of those clients that are writers, and which client, if non-zero, has the file open exclusively or that owns the ioToken. The open state flags are displayed followed by a set of strings indicating the meaning of some of the bits in the flags field. Some examples: flags 0x2000: shared_read flags 0x5000: I/O token shared_excl flags 0x5009: revoking I/O token shared_excl flags 0x9: revoking OLD Exclusive If revoking is indicated, that means the client(s) has been sent a message and a response is being awaited. If client is zero with revoking, a message was sent to one or more clients in shared_read. See also the repblocked command. In future releases, the format of the report may change. resetrpl [clear] Repopulate Reverse Path Lookup (RPL) information. The optional clear argument causes existing RPL data to be cleared before starting repopulation. Note: resetrpl is only available when cvadmin is invoked with the -x option. Running resetrpl may significantly delay FSM activation. This command is not intended for general use. Only run resetrpl when recommended by Technical Support. restartd daemon [once] Restart the daemon process. For internal use only. select [volume_name|N] Select an active FSM to view and modify. If no argument is specified, a numbered list of FSMs and running utilities will be displayed. If there is only one active volume in the list, it will automatically be selected. When a running utility is displayed by the select command, it will show the following information. First the name of the file system is displayed. Following that, in brackets "[]", is the name of the utility that is running. Third, a letter indicating the access type of the operation. The options here are (W) for read-write access, (R) for read-only access and (U) for unique access. Finally, the location and process id of the running utility is displayed. If volume_name is specified, then cvadmin will connect to the current active FSM for that volume. If N (a number) is specified, cvadmin will connect to the Nth FSM in the list. However, only active FSMs may be selected in this form. show [poolname] [long] Display information about the storage pools associated with the selected volume. If a storage pool name poolname is given only that storage pool's information will be given. Omitting the poolname argument will display all storage pools associated with the active file system. Using the long modifier will additionally display detailed information about the disk units associated with displayed storage pools. start volume_name [on hostname_or_IP_address] Start a File System Manager for the volume volume_name. When the command is running on an MDC of an HA cluster, the local FSM is started, and then an attempt is made to start the FSM on the peer MDC as identified by the /Library/Preferences/Xsan/ha_peer file. When the optional hostname_or_IP_address is specified, the FSM is started on that MDC only. The volume's configuration file must be operational and placed in /Library/Preferences/Xsan/<volume_name>.cfg before invoking this command. See snfs_config(5) for information on how to create a configuration file for an Xsan volume. startd daemon [once] Start the daemon process. For internal use only. stat Display the general status of the volume. The output will show the number of clients connected to the volume. This count includes any administrative programs, such as cvadmin. Also shown are some of the static file-system-wide values such as the block size, number of storage pools, number of mirrored storage pools and number of disk devices. The output also shows total blocks and free blocks for the entire volume. stats client_IP_address [clear] Display read/write statistics for the selected file system. This command connects to the host FSMPM who then collects statistics from the file system client. The ten most active files by bytes read and written and by the number of read/write requests are displayed. If clear is specified, zero the stats after printing. stop volume_name [on hostname_or_IP_address] Stop the File System Manager for volume_name. This will shut down the FSM for the specified volume on every MDC. When the optional hostname or IP address is specified, the FSM is stopped on that MDC only. Further operations to the volume will be blocked in clients until an FSM for the volume is activated. stopd daemon Start the daemon process. For internal use only. winidmap __username__ Show the MDC-mapped user id and group information for the username. who Query client list for the active volume. The output will show the following information for each client. Type - Type of connection. The client types are: FSM - File System Manager(FSM) process ADM - Administrative(cvadmin) connection CLI - Volume client connection. May be followed by a CLI type character: S - Disk Proxy Server C - Disk Proxy Client H - Disk Proxy Hybrid Client. This is a client that has been configured as a proxy client but is operating as a SAN client. Location - The client's hostname or IP address that was used by this client to connect to the FSM. Up Time - The time since the client connection was initiated
|
Invoke the cvadmin command for volume named snfs1. [root@dev-snc-daiquiri-n1 debug]# cvadmin -F snfs1 StorNext Administrator Enter command(s) For command help, enter "help" or "?". List FSS File System Services (* indicates service is in control of FS): Selected Cluster: _cluster0/_addom0 Cluster: _cluster0/_addom0 1>*fs1-man[0] located on dev-snc-daiquiri-n1.mdh.quantum.com:52006 (pid 31711) located on Qnode1:52006 located on 169.254.21.1:52006 located on 192.168.21.11:52006 [preferred] 2> fs1-man[0] located on dev-snc-daiquiri-n2.mdh.quantum.com:52004 (pid 42977) located on 172.18.0.1:52004 located on 172.17.0.1:52004 located on Qnode2:52004 located on 169.254.21.2:52004 located on 192.168.21.12:52004 [preferred] 3>*shared-SV1535CKH00012[0] located on dev-snc-daiquiri-n1.mdh.quantum.com:52003 (pid 23220) located on Qnode1:52003 located on 169.254.21.1:52003 located on 192.168.21.11:52003 [preferred] 4> shared-SV1535CKH00012[0] located on dev-snc-daiquiri-n2.mdh.quantum.com:52003 (pid 42382) located on 172.18.0.1:52003 located on 172.17.0.1:52003 located on Qnode2:52003 located on 169.254.21.2:52003 located on 192.168.21.12:52003 [preferred] Cluster: cluster1/_addom0 5>*shared[0] located on jk-rh6sp6-1.mdh.quantum.com:52003 (pid 8650) 6> shared[0] located on jk-rh6sp6-2.mdh.quantum.com:52003 (pid 19417) 7>*snfs1[0] located on jk-rh6sp6-1.mdh.quantum.com:52004 (pid 8651) 8> snfs1[0] located on jk-rh6sp6-2.mdh.quantum.com:52004 (pid 19431) Select FSM "snfs1" Created : Wed Sep 26 12:27:43 2018 Active Connections: 2 Fs Block Size : 4K Msg Buffer Size : 8K Disk Devices : 6 Stripe Groups : 3 Fs Blocks : 2684342720 (10.00 TB) Fs Blocks Free : 2679776316 (9.98 TB) (99%) snadmin (snfs1@cluster1/_addom0) > Show all the storage pools in the volume; snadmin (snfs1@cluster1/_addom0) > show Show stripe groups (File System "snfs1@cluster1/_addom0") Stripe Group 0 [sg0] Status:Up,MetaData,Journal,Exclusive Total Blocks:536868544 (2.00 TB) Reserved:0 (0.00 B) Free:536841775 (2.00 TB) (99%) MultiPath Method:Rotate Primary Stripe [sg0] Read:Enabled Write:Enabled Stripe Group 1 [sg1] Status:Up Total Blocks:1610605632 (6.00 TB) Reserved:1082880 (4.13 GB) Free:1607753562 (5.99 TB) (99%) MultiPath Method:Rotate Primary Stripe [sg1] Read:Enabled Write:Enabled Stripe Group 2 [sg2] Status:Up Total Blocks:1073737088 (4.00 TB) Reserved:1082880 (4.13 GB) Free:1072022754 (3.99 TB) (99%) MultiPath Method:Rotate Primary Stripe [sg2] Read:Enabled Write:Enabled snadmin (snfs1@cluster1/_addom0) > Display the long version of the sg2 storage pool; snadmin (snfs1@cluster1/_addom0) > show sg2 long Show stripe group "sg2" (File System "snfs1@cluster1/_addom0") Stripe Group 2 [sg2] Status:Up Total Blocks:1073737088 (4.00 TB) Reserved:1082880 (4.13 GB) Free:1072022754 (3.99 TB) (99%) MultiPath Method:Rotate Stripe Depth:2 Stripe Breadth:64 blocks (256.00 KB) Affinity Key:af1 Realtime limit IO/sec:0 (~0 mb/sec) Non-Realtime reserve IO/sec:0 Committed RTIO/sec:0 Non-RTIO clients:0 Non-RTIO hint IO/sec:0 Disk stripes: Primary Stripe [sg2] Read:Enabled Write:Enabled Node 0 [t1_0008] Node 1 [t1_0009] snadmin (snfs1@cluster1/_addom0) > FILES /Library/Preferences/Xsan/*.cfg SEE ALSO cvfs(8), snfs_config(5), snfs_metadata_network_filter.json(5), fsmpm(8), fsm(8), mount_acfs(8), sgmanage(8) Xsan File System October 2022 CVADMIN(8)
|
WirelessRadioManagerd
|
WirelessRadioManagerd manages multiple radio coexistence policy. WirelessRadioManagerd should not be invoked directly. macOS 14.5 7/31/2019 macOS 14.5
|
WirelessRadioManagerd – Wireless Radio Manager daemon
|
WirelessRadioManagerd
| null | null |
apachectl
| null |
apachectl - Apache HTTP Server Control Interface
|
When acting in pass-through mode, apachectl can take all the arguments available for the httpd binary. apachectl [ httpd-argument ] When acting in SysV init mode, apachectl takes simple, one-word commands, defined below. apachectl command SUMMARY apachectl is a front end to the Apache HyperText Transfer Protocol (HTTP) server. It is designed to help the administrator control the functioning of the Apache httpd daemon. The apachectl script can operate in two modes. First, it can act as a simple front-end to the httpd command that simply sets any necessary environment variables and then invokes httpd, passing through any command line arguments. Second, apachectl can act as a SysV init script, taking simple one-word arguments like start, restart, and stop, and translating them into appropriate signals to httpd. If your Apache installation uses non-standard paths, you will need to edit the apachectl script to set the appropriate paths to the httpd binary. You can also specify any necessary httpd command line arguments. See the comments in the script for details. The apachectl script returns a 0 exit value on success, and >0 if an error occurs. For more details, view the comments in the script.
|
Only the SysV init-style options are defined here. Other arguments are defined on the httpd manual page. start Loads the org.apache.httpd launchd job. stop, graceful-stop Unloads the org.apache.httpd launchd job. restart, graceful Unloads, then loads the org.apache.httpd launchd job. fullstatus Displays a full status report from mod_status. For this to work, you need to have mod_status enabled on your server and a text- based browser such as lynx available on your system. The URL used to access the status report can be set by editing the STATUSURL variable in the script. status Displays a brief status report. Similar to the fullstatus option, except that the list of requests currently being served is omitted. configtest Run a configuration file syntax test. It parses the configuration files and either reports Syntax Ok or detailed information about the particular syntax error. This is equivalent to apachectl -t. The following option was available in earlier versions but has been removed. startssl To start httpd with SSL support, you should edit your configuration file to include the relevant directives and then use the normal apachectl start. Apache HTTP Server 2018-07-06 APACHECTL(8)
| null |
htcacheclean
| null |
htcacheclean - Clean up the disk cache
|
htcacheclean [ -D ] [ -v ] [ -t ] [ -r ] [ -n ] [ -Rround ] -ppath [ -llimit ] [ -Llimit ] htcacheclean [ -n ] [ -t ] [ -i ] [ -Ppidfile ] [ -Rround ] -dinterval -ppath [ -llimit ] [ -Llimit ] htcacheclean [ -v ] [ -Rround ] -ppath [ -a ] [ -A ] htcacheclean [ -D ] [ -v ] [ -t ] [ -Rround ] -ppath url SUMMARY htcacheclean is used to keep the size of mod_cache_disk's storage within a given size limit, or limit on inodes in use. This tool can run either manually or in daemon mode. When running in daemon mode, it sleeps in the background and checks the cache directory at regular intervals for cached content to be removed. You can stop the daemon cleanly by sending it a TERM or INT signal. When run manually, a once off check of the cache directory is made for cached content to be removed. If one or more URLs are specified, each URL will be deleted from the cache, if present.
|
-dinterval Daemonize and repeat cache cleaning every interval minutes. This option is mutually exclusive with the -D, -v and -r options. To shutdown the daemon cleanly, just send it a SIGTERM or SIGINT. -D Do a dry run and don't delete anything. This option is mutually exclusive with the -d option. When doing a dry run and deleting directories with -t, the inodes reported deleted in the stats cannot take into account the directories deleted, and will be marked as an estimate. -v Be verbose and print statistics. This option is mutually exclusive with the -d option. -r Clean thoroughly. This assumes that the Apache web server is not running (otherwise you may get garbage in the cache). This option is mutually exclusive with the -d option and implies the -t option. -n Be nice. This causes slower processing in favour of other processes. htcacheclean will sleep from time to time so that (a) the disk IO will be delayed and (b) the kernel can schedule other processes in the meantime. -t Delete all empty directories. By default only cache files are removed, however with some configurations the large number of directories created may require attention. If your configuration requires a very large number of directories, to the point that inode or file allocation table exhaustion may become an issue, use of this option is advised. -ppath Specify path as the root directory of the disk cache. This should be the same value as specified with the CacheRoot directive. -Ppidfile Specify pidfile as the name of the file to write the process ID to when daemonized. -Rround Specify round as the amount to round sizes up to, to compensate for disk block sizes. Set to the block size of the cache partition. -llimit Specify limit as the total disk cache size limit. The value is expressed in bytes by default (or attaching B to the number). Attach K for Kbytes, M for MBytes or G for Gbytes. -Llimit Specify limit as the total disk cache inode limit. K, M or G suffix can also be used. -i Be intelligent and run only when there was a modification of the disk cache. This option is only possible together with the -d option. -a List the URLs currently stored in the cache. Variants of the same URL will be listed once for each variant. -A List the URLs currently stored in the cache, along with their attributes in the following order: url, header size, body size, status, entity version, date, expiry, request time, response time, body present, head request. DELETING A SPECIFIC URL If htcacheclean is passed one or more URLs, each URL will be deleted from the cache. If multiple variants of an URL exists, all variants would be deleted. When a reverse proxied URL is to be deleted, the effective URL is constructed from the Host header, the port, the path and the query. Note the '?' in the URL must always be specified explicitly, whether a query string is present or not. For example, an attempt to delete the path / from the server localhost, the URL to delete would be http://localhost:80/?. LISTING URLS IN THE CACHE By passing the -a or -A options to htcacheclean, the URLs within the cache will be listed as they are found, one URL per line. The -A option dumps the full cache entry after the URL, with fields in the following order: url The URL of the entry. header size The size of the header in bytes. body size The size of the body in bytes. status Status of the cached response. entity version The number of times this entry has been revalidated without being deleted. date Date of the response. expiry Expiry date of the response. request time Time of the start of the request. response time Time of the end of the request. body present If 0, no body is stored with this request, 1 otherwise. head request If 1, the entry contains a cached HEAD request with no body, 0 otherwise. EXIT STATUS htcacheclean returns a zero status ("true") if all operations were successful, 1 otherwise. If an URL is specified, and the URL was cached and successfully removed, 0 is returned, 2 otherwise. If an error occurred during URL removal, 1 is returned. Apache HTTP Server 2019-08-09 HTCACHECLEAN(8)
| null |
mount_hfs
|
The mount_hfs command attaches the HFS file system residing on the device special to the global file system namespace at the location indicated by directory. This command is normally executed by mount(8) at boot time. The options are as follows: -u user Set the owner of the files in the file system to user. The default owner is the owner of the directory on which the file system is being mounted. The user may be a user-name, or a numeric value. -g group Set the group of the files in the file system to group. The default group is the group of the directory on which the file system is being mounted. The group may be a group-name, or a numeric value. -m mask Specify the maximum file permissions for files in the file system. (For example, a mask of 755 specifies that, by default, the owner should have read, write, and execute permissions for files, but others should only have read and execute permissions. See chmod(1) for more information about octal file modes.) Only the nine low-order bits of mask are used. The default mask is taken from the directory on which the file system is being mounted. -o Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. -j Ignore the journal for this mount. -c Disable group commit for journaling. SEE ALSO mount(2), unmount(2), fstab(5), mount(8) BUGS Some HFS file systems with highly fragmented catalog files may not mount. HISTORY The mount_hfs utility first appeared in Mac OS X Server 1.0. As of Mac OS X 10.15, this utility will no longer mount HFS standard file systems. Mac OS X October 27, 2020 Mac OS X
|
mount_hfs – mount an HFS+ file system
|
mount_hfs [-e encoding] [-u user] [-g group] [-m mask] [-o options] [-j] [-c] [-w] [-x] special directory
| null | null |
mount_apfs
|
The mount_apfs command attaches the APFS volume indicated by the device special to the global file system namespace at the location indicated by directory. This command is normally executed by diskarbitrationd(8) or mount(8) at boot time. The special parameter should be the path to an APFS pseudo disk device node, such as /dev/disk0s2s1 (which is a volume inside the container /dev/disk0s2), which can also be specified as simply disk0s2s1. The options are as follows: -o options Options passed to mount(2) are specified with the -o option followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. All listed options are currently supported except for the ``force, sync and [no]async'' options. -u user Set the owner of the files in the file system to user. The default owner is the owner of the directory on which the file system is being mounted. The user may be a user-name, or a numeric value. -g group Set the group of the files in the file system to group. The default group is the group of the directory on which the file system is being mounted. The group may be a group-name, or a numeric value. -s snapshot The name of the snapshot to mount. In this usage pathname is the mounted root directory of the base volume containing the snapshot. EXIT STATUS The mount_apfs utility exits 0 on success, and >0 if an error occurs. SEE ALSO mount(2), unmount(2), fstab(5), mount(8), umount(8) HISTORY The mount_apfs utility first appeared in OS X 10.12. Mac OS X September 16, 2015 Mac OS X
|
mount_apfs – mount an APFS volume
|
mount_apfs [-o options] [-u user] [-g group] special directory mount_apfs [-o options] -s snapshot pathname directory
| null | null |
md5
|
The md5 utility takes as input a message of arbitrary length and produces as output a “fingerprint” or “message digest” of the input. It is conjectured that it is computationally infeasible to produce two messages having the same message digest, or to produce any message having a given prespecified target message digest. The MD5 algorithm is intended for digital signature applications, where a large file must be “compressed” in a secure manner before being encrypted with a private (secret) key under a public-key cryptosystem such as RSA. MD5's designer Ron Rivest has stated "md5 and sha1 are both clearly broken (in terms of collision-resistance)". So MD5 should be avoided when creating new protocols, or implementing protocols with better options. SHA256 and SHA512 are better options as they have been more resilient to attacks (as of 2009). The following options may be used in any combination and must precede any files named on the command line. The hexadecimal checksum of each file listed on the command line is printed after the options are processed. -s string Print a checksum of the given string. -p Echo stdin to stdout and append the checksum to stdout. -q Quiet mode - only the checksum is printed out. Overrides the -r option. -r Reverses the format of the output. This helps with visual diffs. Does nothing when combined with the -ptx options. -t Run a built-in time trial. -x Run a built-in test script. EXIT STATUS The md5 utility exits 0 on success, and 1 if at least one of the input files could not be read. SEE ALSO cksum(1), CC_SHA256_Init(3), md5(3), ripemd(3), sha(3) R. Rivest, The MD5 Message-Digest Algorithm, RFC1321. Vlastimil Klima, Finding MD5 Collisions - a Toy For a Notebook, Cryptology ePrint Archive: Report 2005/075. ACKNOWLEDGMENTS This program is placed in the public domain for free general use by RSA Data Security. macOS 14.5 June 6, 2004 macOS 14.5
|
md5 – calculate a message-digest fingerprint (checksum) for a file
|
md5 [-pqrtx] [-s string] [file ...]
| null | null |
fsck
|
The first form of fsck preens a standard set of filesystems or the specified filesystems. It is normally used in the script /etc/rc during automatic reboot. Here fsck reads the filesystem descriptor table (using getfsent(3)) to determine which filesystems to check. Only partitions that have ``rw,'' ``rq'' or ``ro'' as options, and that have non-zero pass number are checked. Filesystems with pass number 1 (normally just the root filesystem) are checked one at a time. When pass 1 completes, all remaining filesystems are checked, running one process per disk drive. The disk drive containing each filesystem is inferred from the shortest prefix of the device name that ends in one or more digits; the remaining characters are assumed to be the partition designator. In preening mode, filesystems that are marked clean are skipped. Filesystems are marked clean when they are unmounted, when they have been mounted read-only, or when fsck runs on them successfully. It should be noted that fsck is now essentially a wrapper that invokes other fsck_XXX utilities as needed. Currently, fsck can invoke fsck_hfs, fsck_apfs, fsck_msdos, fsck_exfat, and fsck_udf. If this underlying process that fsck invokes encounters serious inconsistencies or the filesystem type is not one of the above, it exits with an abnormal return status and an automatic reboot will then fail. For each corrected inconsistency one or more lines will be printed identifying the filesystem on which the correction will take place, and the nature of the correction. If sent a QUIT signal, fsck will finish the filesystem checks, then exit with an abnormal return status that causes an automatic reboot to fail. This is useful when you want to finish the filesystem checks during an automatic reboot, but do not want the machine to come up multiuser after the checks complete. Without the -p option, fsck audits and interactively repairs inconsistent conditions for filesystems. It should be noted that some of the corrective actions which are not correctable under the -p option will result in some loss of data. The amount and severity of data lost may be determined from the diagnostic output. If the operator does not have write permission on the filesystem fsck will default to a -n action. The following flags are interpreted by fsck and passed along to the underlying tool that it spawns. -f Force fsck to check `clean' filesystems when preening. -l Limit the number of parallel checks to the number specified in the following argument. By default, the limit is the number of disks, running one process per disk. If a smaller limit is given, the disks are checked round-robin, one filesystem at a time. -R Specify a particular passno number for which fsck is to check. You may only specify 1 or 2. Only those filesystems matching that particular passno entry (if using fstab) will be checked. For more information on the passno field, see fstab(5). -p "Preen" mode, described above. -q Do a quick check to determine if the filesystem was unmounted cleanly. -y Assume a yes response to all questions asked by fsck; this should be used with great caution as this is a free license to continue after essentially unlimited trouble has been encountered. -n Assume a no response to all questions asked by fsck except for ‘CONTINUE?’, which is assumed to be affirmative; do not open the filesystem for writing. If no filesystems are given to fsck then a default list of filesystems is read using getfsent(3). Because of inconsistencies between the block device and the buffer cache, the raw device should always be used. SEE ALSO fs(5), fsck_hfs(8), fsck_apfs(8), fsck_msdos(8), getfsent(3), fstab(5), reboot(8) BSD 4 May 18, 2010 BSD 4
|
fsck – filesystem consistency check and interactive repair
|
fsck -p [-f] fsck [-l maxparallel] [-q] [-y] [-n] [-d]
| null | null |
mount_udf
|
The mount_udf command attaches the UDF filesystem residing on the device devicePath to the global filesystem namespace at the location indicated by mountPath. This command is normally executed by mount(8) at boot time. The options are as follows: -o options Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. -v verificationPolicy This is an advanced option not useful for regular use. It controlls the verification policy when writing to RW type optical media. Its value can be "meta", "all", or "none". Policy "meta" means only the metadata are verified after they are written. This is the default policy. Policy "all" means to verify data written, which could be several times slower than policy "meta". Policy "none" does not verify any data. It is only slightly faster than "meta" in normal cases, but may result a corrupted UDF disc if the write of metadata fails. -s sessionStart This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the start Logical Block Address of the last session where UDF data structures (VRS and AVDP) resides. This value overrides the value obtained from the device. -n lastRecordedLBA This is an advanced option not useful for regular use. When manually mounting a UDF volume with Virtual Partition, it specifies the last recorded Logical Block Address where the UDF VAT ICB will be searched. This value overrides the value obtained from the device. -b blockSize This is an advanced option not useful for regular use. It specifies the block size in bytes used when mounting the UDF volume. This value overrides the value obtained from the device. -p packetSizeInBlocks This is an advanced option not useful for regular use. It specifies the packet size in blocks when manually mounting the UDF volume. This value overrides the value obtained from the device. -w This is an advanced option not useful for regular use. It forces to enable the experimental packet writing function on optical media that has not been fully supported, such as CD-R, CD-RW, DVD-R, DVD+R, HD DVD-R, and BD-R. Writing to these media does not work on some drives and may cause data corruption or data loss on some other drives. Therefore, this flag should be used only by file system developers when debugging the experimental write functions. The -s, -n, -b, and -p flags are not useful in normal use. They are mainly used for debugging and data recovery. Since the -s, -n, and -p flags are all specified in units of block size, when any of these flags are specified, it is strongly recommended that the -b flag is also specified. SEE ALSO mount(2), unmount(2), fstab(5), mount(8) BUGS Reading of all UDF revisions (1.02 - 2.60) on both block device (e.g., hard drives and USB drives) and most optical media is supported. Writing to block devices, DVD-RW and DVD+RW is supported with the following exceptions: (1) Cannot write Finder Info, Resource Fork, or other extended attributes in UDF volumes of revision 1.02 and 1.50; (2) Cannot write to mirrored metadata partition. HISTORY The mount_udf utility first appeared in Mac OS X. BSD 4 December 6, 2006 BSD 4
|
mount_udf – mount a UDF filesystem
|
mount_udf [-o options] [-s sessionStart] [-n lastRecordedLBA] [-b blockSize] [-p packetSizeInBlocks] [-v verificationPolicy] [-w] devicePath mountPath
| null | null |
quotacheck
|
Quotacheck examines each filesystem, builds a table of current disk usage, and compares this table against that recorded in the disk quota file for the filesystem. If any inconsistencies are detected, both the quota file and the current system copy of the incorrect quotas are updated (the latter only occurs if an active filesystem is checked). By default both user and group quotas are checked. Available options: -a If the -a flag is supplied in place of any filesystem names, quotacheck will check all the read-write filesystems with an existing mount option file at its root. The mount option file specifies the types of quotas that are to be checked. -g Only group quotas are checked. The mount option file, .quota.ops.group, must exist at the root of the filesystem. -u Only user quotas are checked. The mount option file, .quota.ops.user, must exist at the root of the filesystem. -v quotacheck reports discrepancies between the calculated and recorded disk quotas. Specifying both -g and -u is equivalent to the default. Parallel passes are run on the filesystems required, in an identical fashion to fsck(8). Normally quotacheck operates silently. Quotacheck expects each filesystem being checked to have quota data files named .quota.user and/or .quota.group located at the filesystem root. If a binary data file is not present, quotacheck will create it. The default filename and root location cannot be overridden. Quotacheck is normally run at fsck time. Quotacheck accesses the raw device in calculating the actual disk usage for each user. Thus, the filesystems checked should be quiescent while quotacheck is running. FILES Each of the following quota files is located at the root of the mounted filesystem. The mount option files are empty files whose existence indicates that quotas are to be enabled for that filesystem. The binary data files will be created by quotacheck, if they don't already exist. .quota.user data file containing user quotas .quota.group data file containing group quotas .quota.ops.user mount option file used to enable user quotas .quota.ops.group mount option file used to enable group quotas SEE ALSO quota(1), quotactl(2), edquota(8), fsck(8), quotaon(8), repquota(8) HISTORY The quotacheck command appeared in 4.2BSD. BSD 4.2 October 17, 2002 BSD 4.2
|
quotacheck – filesystem quota consistency checker
|
quotacheck [-g] [-u] [-v] filesystem ... quotacheck [-g] [-u] [-v] -a
| null | null |
mount_cd9660
|
The mount_cd9660 command attaches the ISO-9660 filesystem residing on the device special to the global filesystem namespace at the location indicated by node. This command is normally executed by mount(8) at boot time. The options are as follows: -e Enable the use of extended attributes. -g Do not strip version numbers on files. (By default, if there are files with different version numbers on the disk, only the last one will be listed.) In either case, files may be opened without explicitly stating a version number. -j Do not use any Joliet extensions included in the filesystem. -o Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. -r Do not use any Rockridge extensions included in the filesystem. -s startsector Start the filesystem at startsector. Normally, if the underlying device is a CD-ROM drive, mount_cd9660 will try to figure out the last track from the CD-ROM containing data, and start the filesystem there. If the device is not a CD-ROM, or the table of contents cannot be examined, the filesystem will be started at sector 0. This option can be used to override the behaviour. Note that startsector is measured in CD-ROM blocks, with 2048 bytes each. SEE ALSO mount(2), unmount(2), fstab(5), mount(8) BUGS POSIX device node mapping is currently not supported. Version numbers are not stripped if Rockridge extensions are in use. In this case, accessing files that don't have Rockridge names without version numbers gets the one with the lowest version number and not the one with the highest. There is no ECMA support. HISTORY The mount_cd9660 utility first appeared 4.4BSD. BSD 4 March 27, 1994 BSD 4
|
mount_cd9660 – mount an ISO-9660 filesystem
|
mount_cd9660 [-egjr] [-o options] [-s startsector] special node
| null | null |
ping
|
The ping utility uses the ICMP protocol's mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (“pings”) have an IP and ICMP header, followed by a “struct timeval” and then an arbitrary number of “pad” bytes used to fill out the packet. The options are as follows: -A Audible. Output a bell (ASCII 0x07) character when no packet is received before the next packet is transmitted. To cater for round-trip times that are longer than the interval between transmissions, further missing packets cause a bell only if the maximum number of unreceived packets has increased. -a Audible. Include a bell (ASCII 0x07) character in the output when any packet is received. This option is ignored if other format options are present. -b boundif Bind the socket to interface boundif for sending. This option is an Apple addition. -C Prohibit the socket from using the cellular network interface. This option is an Apple addition. -c count Stop after sending (and receiving) count ECHO_RESPONSE packets. If this option is not specified, ping will operate until interrupted. If this option is specified in conjunction with ping sweeps, each sweep will consist of count packets. -D Set the Don't Fragment bit. -d Set the SO_DEBUG option on the socket being used. -f Flood ping. Outputs packets as fast as they come back or one hundred times per second, whichever is more. For every ECHO_REQUEST sent a period “.” is printed, while for every ECHO_REPLY received a backspace is printed. This provides a rapid display of how many packets are being dropped. Only the super-user may use this option. This can be very hard on a network and should be used with caution. -G sweepmaxsize Specify the maximum size of ICMP payload when sending sweeping pings. This option is required for ping sweeps. -g sweepminsize Specify the size of ICMP payload to start with when sending sweeping pings. The default value is 0. -h sweepincrsize Specify the number of bytes to increment the size of ICMP payload after each sweep when sending sweeping pings. The default value is 1. -I iface Source multicast packets with the given interface address. This flag only applies if the ping destination is a multicast address. -i wait Wait wait seconds between sending each packet. The default is to wait for one second between each packet. The wait time may be fractional, but only the super-user may specify values less than 0.1 second. This option is incompatible with the -f option. -k trafficclass Specifies the traffic class to use for sending ICMP packets. The supported traffic classes are BK_SYS, BK, BE, RD, OAM, AV, RV, VI, VO and CTL. By default ping uses the control traffic class (CTL). This option is an Apple addition. -K netservicetype Specifies the network service type to use for sending ICMP packets. The supported network service type are BK_SYS, BK, BE, RV, AV, RD, OAM, VI, SIG and VO. Note this overrides the default traffic class (-k can still be specified after -K to use both). This option is an Apple addition. -L Suppress loopback of multicast packets. This flag only applies if the ping destination is a multicast address. -l preload If preload is specified, ping sends that many packets as fast as possible before falling into its normal mode of behavior. Only the super-user may use this option. -M mask | time Use ICMP_MASKREQ or ICMP_TSTAMP instead of ICMP_ECHO. For mask, print the netmask of the remote machine. Set the net.inet.icmp.maskrepl MIB variable to enable ICMP_MASKREPLY. For time, print the origination, reception and transmission timestamps. -m ttl Set the IP Time To Live for outgoing packets. If not specified, the kernel uses the value of the net.inet.ip.ttl MIB variable. -n Numeric output only. No attempt will be made to lookup symbolic names for host addresses. -o Exit successfully after receiving one reply packet. -P policy policy specifies IPsec policy for the ping session. For details please refer to ipsec(4) and ipsec_set_policy(3). -p pattern You may specify up to 16 “pad” bytes to fill out the packet you send. This is useful for diagnosing data-dependent problems in a network. For example, “-p ff” will cause the sent packet to be filled with all ones. -Q Somewhat quiet output. Don't display ICMP error messages that are in response to our query messages. Originally, the -v flag was required to display such errors, but -v displays all ICMP error messages. On a busy machine, this output can be overbearing. Without the -Q flag, ping prints out any ICMP error messages caused by its own ECHO_REQUEST messages. -q Quiet output. Nothing is displayed except the summary lines at startup time and when finished. -R Record route. Includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets. This option is deprecated and is now a no-op. -r Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-attached network, an error is returned. This option can be used to ping a local host through an interface that has no route through it (e.g., after the interface was dropped by routed(8)). -S src_addr Use the following IP address as the source address in outgoing packets. On hosts with more than one IP address, this option can be used to force the source address to be something other than the IP address of the interface the probe packet is sent on. If the IP address is not one of this machine's interface addresses, an error is returned and nothing is sent. -s packetsize Specify the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data. This option cannot be used with ping sweeps. -T ttl Set the IP Time To Live for multicasted packets. This flag only applies if the ping destination is a multicast address. -t timeout Specify a timeout, in seconds, before ping exits regardless of how many packets have been received. -v Verbose output. ICMP packets other than ECHO_RESPONSE that are received are listed. -W waittime Time in milliseconds to wait for a reply for each packet sent. If a reply arrives later, the packet is not printed as replied, but considered as replied when calculating statistics. -z tos Use the specified type of service. --apple-connect Connects the socket to the destination address. This option is an Apple addition. --apple-time Prints the time a packet was received. This option is an Apple addition. When using ping for fault isolation, it should first be run on the local host, to verify that the local network interface is up and running. Then, hosts and gateways further and further away should be “pinged”. Round-trip times and packet loss statistics are computed. If duplicate packets are received, they are not included in the packet loss calculation, although the round trip time of these packets is used in calculating the round-trip time statistics. When the specified number of packets have been sent (and received) or if the program is terminated with a SIGINT, a brief summary is displayed, showing the number of packets sent and received, and the minimum, mean, maximum, and standard deviation of the round-trip times. If ping receives a SIGINFO (see the status argument for stty(1)) signal, the current number of packets sent and received, and the minimum, mean, and maximum of the round-trip times will be written to the standard error output. This program is intended for use in network testing, measurement and management. Because of the load it can impose on the network, it is unwise to use ping during normal operations or from automated scripts. ICMP PACKET DETAILS An IP header without options is 20 bytes. An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth of ICMP header followed by an arbitrary amount of data. When a packetsize is given, this indicated the size of this extra piece of data (the default is 56). Thus the amount of data received inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes more than the requested data space (the ICMP header). If the data space is at least eight bytes large, ping uses the first eight bytes of this space to include a timestamp which it uses in the computation of round trip times. If less than eight bytes of pad are specified, no round trip times are given. DUPLICATE AND DAMAGED PACKETS The ping utility will report duplicate and damaged packets. Duplicate packets should never occur when pinging a unicast address, and seem to be caused by inappropriate link-level retransmissions. Duplicates may occur in many situations and are rarely (if ever) a good sign, although the presence of low levels of duplicates may not always be cause for alarm. Duplicates are expected when pinging a broadcast or multicast address, since they are not really duplicates but replies from different hosts to the same request. Damaged packets are obviously serious cause for alarm and often indicate broken hardware somewhere in the ping packet's path (in the network or in the hosts). TRYING DIFFERENT DATA PATTERNS The (inter)network layer should never treat packets differently depending on the data contained in the data portion. Unfortunately, data-dependent problems have been known to sneak into networks and remain undetected for long periods of time. In many cases the particular pattern that will have problems is something that does not have sufficient “transitions”, such as all ones or all zeros, or a pattern right at the edge, such as almost all zeros. It is not necessarily enough to specify a data pattern of all zeros (for example) on the command line because the pattern that is of interest is at the data link level, and the relationship between what you type and what the controllers transmit can be complicated. This means that if you have a data-dependent problem you will probably have to do a lot of testing to find it. If you are lucky, you may manage to find a file that either cannot be sent across your network or that takes much longer to transfer than other similar length files. You can then examine this file for repeated patterns that you can test using the -p option of ping. TTL DETAILS The TTL value of an IP packet represents the maximum number of IP routers that the packet can go through before being thrown away. In current practice you can expect each router in the Internet to decrement the TTL field by exactly one. The TCP/IP specification recommends setting the TTL field for IP packets to 64, but many systems use smaller values (4.3BSD uses 30, 4.2BSD used 15). The maximum possible value of this field is 255, and most UNIX systems set the TTL field of ICMP ECHO_REQUEST packets to 255. This is why you will find you can “ping” some hosts, but not reach them with telnet(1) or ftp(1). In normal operation ping prints the ttl value from the packet it receives. When a remote system receives a ping packet, it can do one of three things with the TTL field in its response: • Not change it; this is what BSD systems did before the 4.3BSD-Tahoe release. In this case the TTL value in the received packet will be 255 minus the number of routers in the round-trip path. • Set it to 255; this is what current BSD systems do. In this case the TTL value in the received packet will be 255 minus the number of routers in the path from the remote system to the pinging host. • Set it to some other value. Some machines use the same value for ICMP packets that they use for TCP packets, for example either 30 or 60. Others may use completely wild values. EXIT STATUS The ping utility exits with one of the following values: 0 At least one response was heard from the specified host. 2 The transmission was successful but no responses were received. any other value An error occurred. These values are defined in <sysexits.h>. SEE ALSO netstat(1), ifconfig(8), routed(8), traceroute(8), ping6(8) HISTORY The ping utility appeared in 4.3BSD. AUTHORS The original ping utility was written by Mike Muuss while at the US Army Ballistics Research Laboratory. BUGS Flood pinging is not recommended in general, and flood pinging the broadcast address should only be done under very controlled conditions. The -v option is not worth much on busy hosts. macOS 14.5 March 29, 2013 macOS 14.5
|
ping – send ICMP ECHO_REQUEST packets to network hosts
|
ping [-AaCDdfnoQqRrv] [-b boundif] [-c count] [-G sweepmaxsize] [-g sweepminsize] [-h sweepincrsize] [-i wait] [-k trafficclass] [-K netservicetype] [-l preload] [-M mask | time] [-m ttl] [-P policy] [-p pattern] [-S src_addr] [-s packetsize] [-t timeout] [-W waittime] [-z tos] [--apple-connect] [--apple-time] host ping [-AaDdfLnoQqRrv] [-b boundif] [-c count] [-I iface] [-i wait] [-k trafficclass] [-K netservicetype] [-l preload] [-M mask | time] [-m ttl] [-P policy] [-p pattern] [-S src_addr] [-s packetsize] [-T ttl] [-t timeout] [-W waittime] [-z tos] [--apple-connect] [--apple-time] mcast-group
| null | null |
fsck_exfat
|
The fsck_exfat utility verifies and repairs ExFAT file systems. The first form of fsck_exfat quickly checks the specified file systems to determine whether they were cleanly unmounted. The second form of fsck_exfat checks the specified file systems and tries to repair all detected problems, requesting confirmation before making any changes. The default behavior is to always ask for confirmation of each change. Use the -n or -y options to override this default behavior. The device parameter(s) should be a path to a "raw" disk device (a character special device), such as /dev/rdisk1s1. If you specify a "non- raw" path (a block special device) such as /dev/disk1s1, or just the disk name such as disk1s1, they will automatically be converted to the corresponding raw disk device (/dev/rdisk1s1). The options are as follows: -q Causes fsck_exfat to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message is printed to standard output describing whether the volume was clean or dirty. -f This option is ignored by fsck_exfat and is present only for compatibility with programs that check other file system types for consistency. -p Preen the specified file systems. This option is ignored by fsck_exfat and is present only for compatibility with programs that check other file system types for consistency. -y Causes fsck_exfat to assume yes as the answer to all questions. It will attempt to repair all problems that are found. -n Causes fsck_exfat to assume no as the answer to all questions. The device will be opened read-only, and no repairs will be made. -g Causes fsck_exfat to produce its output in GUI-compatible form. Each message is printed as a tuple containing the kind of message, the message string, and number of parameters to the message string. Any parameters to the message string are printed on subsequent lines. The message string uses NSLog-like substitutions. This output format is used by applications such as Disk Utility. -x Causes fsck_exfat to produce its output in an XML-like form. Each message is printed as a plist(5) containing a message type, verbosity, message number, and message string. The message string uses NSLog-like substitutions. For message strings that contain parameters, an array of dictionaries is output. This output format is used by applications such as Disk Utility. It may be used by other kinds of applications which wish to parse the output of fsck_exfat. -d Causes fsck_exfat to produce extra debugging output. This generally contains additional details about problems found. When writing bug reports for fsck_exfat, it is usually helpful to include the output generated from this option. -S path_prefix Causes fsck_exfat to create a shadow file containing all metadata read from the device. This functionality is intended for inclusion with bug reports regarding excpetional problems. One file is created for each checked device. A shadow file's name is created by taking path_prefix, appending a - character, and then appending the basename of the device being checked. For instance, given a path_prefix of ./metadata, a check of disk /dev/rdisk3s1 would create the shadow file ./metadata-rdisk3s1. Note that the shadow file captures all metadata as read from disk. In some cases with large volumes, fsck_exfat will limit its cache size and re-read metadata from disk at different phases of the repair process. If the repair process has repaired the metadata, the shadow file will capture its state as last read from disk. For optimal debug value, the shadow file should be captured in conjunction with the -n option. This file will be created as a sparse file, if it is on a file system supporting sparse files, such as APFS. The shadow file does not capture file contents. However be aware the shadow file includes details about all current and some past files. Extreme care should be taken before sharing the shadow file with others. SEE ALSO mount_exfat(8), fsck(8) HISTORY The fsck_exfat utility first appeared in Mac OS X 10.6.3. Darwin January 19, 2010 Darwin
|
fsck_exfat – Verify and repair ExFAT file systems.
|
fsck_exfat -q device ... fsck_exfat [-f] [-p] [-y | -n] [-g | -x] [-S -path_prefix] [-d] device ...
| null | null |
mount_exfat
|
The mount_exfat command mounts the ExFAT filesystem from the device device onto the directory given by directory. This command is normally invoked by diskarbitrationd(8) as the result of detecting a device with a file system recognized as ExFAT. It can also be invoked indirectly by executing the mount(8) command with the -t exfat option. The options are as follows: -o options Use the specified mount options, as described in mount(8). -u uid Set the owner of the files in the file system to uid. The default owner is the owner of the directory on which the file system is being mounted. -g gid Set the group of the files in the file system to gid. The default group is the group of the directory on which the file system is being mounted. -m mask Specify the maximum file permissions for files in the file system. (For example, a mask of 755 specifies that, by default, the owner should have read, write, and execute permissions for files, but others should only have read and execute permissions. See chmod(1) for more information about octal file modes.) Only the nine low-order bits of mask are used. The default mask is taken from the directory on which the file system is being mounted. If none of the -u, -g, or -m options are given, the volume will be mounted with the MNT_UNKNOWNPERMISSIONS flag (equivalent to the -o noowners option). If the device is internal and not removable, the volume will be mounted with the MNT_ASYNC flag (equivalent to the -o async option) by default. That default can be overridden with the -o noasync option. When mounted with the -o noasync option, metadata updates are synced to disk frequently (by default, 50ms after the system call that changed the metadata returns to its caller). SEE ALSO fsck_exfat(8), exfat.util(8), mount(2), unmount(2), fstab(5), mount(8) HISTORY The mount_exfat utility first appeared in Mac OS X 10.6.3. Darwin January 19, 2010 Darwin
|
mount_exfat – mount an ExFAT file system
|
mount_exfat [-o options] [-u uid] [-g gid] [-m mask] device directory
| null | null |
fsck_udf
|
The fsck_udf command examines a UDF filesystem residing on devicePath for correctness. SEE ALSO mount_udf(8) BUGS Currently does not perform any repairs. HISTORY The fsck_udf utility first appeared in Mac OS X. macOS 14.5 March 10, 2008 macOS 14.5
|
fsck_udf – check a UDF filesystem
|
fsck_udf [-b blocksize] [-L] [-p] [-D] devicePath
| null | null |
shutdown
|
The shutdown utility provides an automated shutdown procedure for super- users to nicely notify users when the system is shutting down, saving them from system administrators, hackers, and gurus, who would otherwise not bother with such niceties. The following options are available: -h The system is halted and powered off at the specified time. -p This flag is the equivalent of -h. -r The system is rebooted at the specified time. -s The system is put to sleep at the specified time. -k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all but super-user). -o If one of the -h or -r options are specified, shutdown will execute halt(8) or reboot(8) instead of sending a signal to launchd(8). -n If the -o option is specified, prevent the file system cache from being flushed by passing -n to halt(8) or reboot(8). The use of this option is discouraged as it can result in data loss. time Time is the time at which shutdown will bring the system down and may be the case-insensitive word now (indicating an immediate shutdown) or a future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current system values. The first form brings the system down in number minutes and the second at the absolute time specified. +number may be specified in units other than minutes by appending the corresponding suffix: “s”, “sec”, “m”, “min”, “h”, “hour”. If an absolute time is specified, but not a date, and that time today has already passed, shutdown will assume that the same time tomorrow was meant. (If a complete date is specified which has already passed, shutdown will print an error and exit without shutting the system down.) warning-message Any other arguments comprise the warning message that is broadcast to users currently logged into the system. - If ‘-’ is supplied as an option, the warning message is read from the standard input. At intervals, becoming more frequent as apocalypse approaches and starting at ten hours before shutdown, warning messages are displayed on the terminals of all users logged in. Five minutes before shutdown, or immediately if shutdown is in less than 5 minutes, logins are disabled by creating /var/run/nologin and copying the warning message there. If this file exists when a user attempts to log in, login(1) prints its contents and exits. The file is removed just before shutdown exits. At shutdown time a message is written to the system log, containing the time of shutdown, the person who initiated the shutdown and the reason. The corresponding signal is then sent to launchd(8) to respectively halt, reboot or bring the system down to single-user state (depending on the above options). The time of the shutdown and the warning message are placed in /var/run/nologin and should be used to inform the users about when the system will be back up and why it is going down (or anything else). A scheduled shutdown can be canceled by killing the shutdown process (a SIGTERM should suffice). The /var/run/nologin file that shutdown created will be removed automatically. When run without options, the shutdown utility will place the system into single user mode at the time specified. SIGTERM TO SIGKILL INTERVAL Upon shutdown, all running processes are sent a SIGTERM followed by a SIGKILL. The SIGKILL will follow the SIGTERM by an intentionally indeterminate period of time. Programs are expected to take only enough time to flush all dirty data and exit. Developers are encouraged to file a bug with the OS vendor, should they encounter an issue with this functionality. FILES /var/run/nologin tells login(1) not to let anyone log in
|
shutdown – close down the system at a given time
|
shutdown [-] [-h | -p | -r | -s | -k] [-o [-n]] time [warning-message ...]
| null |
Reboot the system in 30 minutes and display a warning message on the terminals of all users currently logged in: # shutdown -r +30 "System will reboot" COMPATIBILITY The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility. SEE ALSO kill(1), login(1), wall(1), nologin(5), halt(8), launchd(8), reboot(8) HISTORY A shutdown command was originally written by Ian Johnstone for UNSW's modified AT&T UNIX 6th Edn. It was modified and then incorporated in 4.1BSD. macOS 14.5 June 6, 2023 macOS 14.5
|
route
|
Route is a utility used to manually manipulate the network routing tables. It normally is not needed, as a system routing table management daemon such as routed(8), should tend to this task. The route utility supports a limited number of general options, but a rich command language, enabling the user to specify any arbitrary request that could be delivered via the programmatic interface discussed in route(4). The following options are available: -d Run in debug-only mode, i.e., do not actually modify the routing table. -n Bypass attempts to print host and network names symbolically when reporting actions. (The process of translating between symbolic names and numerical equivalents can be quite time consuming, and may require correct operation of the network; thus it may be expedient to forget this, especially when attempting to repair networking operations). -t Run in test-only mode. /dev/null is used instead of a socket. -v (verbose) Print additional details. -q Suppress all output. The route utility provides six commands: add Add a route. flush Remove all routes. delete Delete a specific route. change Change aspects of a route (such as its gateway). get Lookup and display the route for a destination. monitor Continuously report any changes to the routing information base, routing lookup misses, or suspected network partitionings. The monitor command has the syntax: route [-n] monitor The flush command has the syntax: route [-n] flush [family] If the flush command is specified, route will ``flush'' the routing tables of all gateway entries. When the address family may is specified by any of the -osi, -xns, -atalk, -inet6, or -inet modifiers, only routes having destinations with addresses in the delineated family will be deleted. The other commands have the following syntax: route [-n] command [-net | -host] [-ifscope boundif] destination gateway [netmask] where destination is the destination host or network, gateway is the next-hop intermediary via which packets should be routed. Routes to a particular host may be distinguished from those to a network by interpreting the Internet address specified as the destination argument. The optional modifiers -net and -host force the destination to be interpreted as a network or a host, respectively. Otherwise, if the destination has a “local address part” of INADDR_ANY (0.0.0.0), or if the destination is the symbolic name of a network, then the route is assumed to be to a network; otherwise, it is presumed to be a route to a host. Optionally, the destination could also be specified in the net/bits format. For example, 128.32 is interpreted as -host 128.0.0.32; 128.32.130 is interpreted as -host 128.32.0.130; -net 128.32 is interpreted as 128.32.0.0; -net 128.32.130 is interpreted as 128.32.130.0; and 192.168.64/20 is interpreted as -net 192.168.64 -netmask 255.255.240.0. A destination of default is a synonym for -net 0.0.0.0, which is the default route. If the destination is directly reachable via an interface requiring no intermediary system to act as a gateway, the -interface modifier should be specified; the gateway given is the address of this host on the common network, indicating the interface to be used for transmission. Alternately, if the interface is point to point the name of the interface itself may be given, in which case the route remains valid even if the local or remote addresses change. For AF_INET and AF_INET6, the -ifscope modifier specifies the additional property of the route related to the interface scope derived from interface boundif. Such property allows for the presence of multiple route entries with the same destination, where each route is associated with a unique interface. This modifier is required in order to manipulate route entries marked with the RTF_IFSCOPE flag. The optional modifier -link specify that all subsequent addresses are specified as link-level addresses, and the names must be numeric specifications rather than symbolic names. The optional -netmask modifier is intended to achieve the effect of an OSI ESIS redirect with the netmask option, or to manually add subnet routes with netmasks different from that of the implied network interface (as would otherwise be communicated using the OSPF or ISIS routing protocols). One specifies an additional ensuing address parameter (to be interpreted as a network mask). The implicit network mask generated in the AF_INET case can be overridden by making sure this option follows the destination parameter. For AF_INET6, the -prefixlen qualifier is available instead of the -mask qualifier because non-continuous masks are not allowed in IPv6. For example, -prefixlen 32 specifies network mask of ffff:ffff:0000:0000:0000:0000:0000:0000 to be used. The default value of prefixlen is 64 to get along with the aggregatable address. But 0 is assumed if default is specified. Note that the qualifier works only for AF_INET6 address family. Routes have associated flags which influence operation of the protocols when sending to destinations matched by the routes. These flags may be set (or sometimes cleared) by indicating the following corresponding modifiers: -cloning RTF_CLONING - generates a new route on use -xresolve RTF_XRESOLVE - emit mesg on use (for external lookup) -iface ~RTF_GATEWAY - destination is directly reachable -static RTF_STATIC - manually added route -nostatic ~RTF_STATIC - pretend route added by kernel or daemon -reject RTF_REJECT - emit an ICMP unreachable when matched -blackhole RTF_BLACKHOLE - silently discard pkts (during updates) -proto1 RTF_PROTO1 - set protocol specific routing flag #1 -proto2 RTF_PROTO2 - set protocol specific routing flag #2 -llinfo RTF_LLINFO - validly translates proto addr to link addr The optional modifiers -rtt, -rttvar, -sendpipe, -recvpipe, -mtu, -hopcount, -expire, and -ssthresh provide initial values to quantities maintained in the routing entry by transport level protocols, such as TCP or TP4. These may be individually locked by preceding each such modifier to be locked by the -lock meta-modifier, or one can specify that all ensuing metrics may be locked by the -lockrest meta-modifier. In a change or add command where the destination and gateway are not sufficient to specify the route (as in the ISO case where several interfaces may have the same address), the -ifp or -ifa modifiers may be used to determine the interface or interface address. The optional -proxy modifier specifies that the RTF_LLINFO routing table entry is the “published (proxy-only)” ARP entry, as reported by arp(8). All symbolic names specified for a destination or gateway are looked up first as a host name using gethostbyname(3). If this lookup fails, getnetbyname(3) is then used to interpret the name as that of a network. Route uses a routing socket and the new message types RTM_ADD, RTM_DELETE, RTM_GET, and RTM_CHANGE. As such, only the super-user may modify the routing tables. DIAGNOSTICS add [host | network ] %s: gateway %s flags %x The specified route is being added to the tables. The values printed are from the routing table entry supplied in the ioctl(2) call. If the gateway address used was not the primary address of the gateway (the first one returned by gethostbyname(3)), the gateway address is printed numerically as well as symbolically. delete [ host | network ] %s: gateway %s flags %x As above, but when deleting an entry. %s %s done When the flush command is specified, each routing table entry deleted is indicated with a message of this form. Network is unreachable An attempt to add a route failed because the gateway listed was not on a directly-connected network. The next-hop gateway must be given. not in table A delete operation was attempted for an entry which wasn't present in the tables. routing table overflow An add operation was attempted, but the system was low on resources and was unable to allocate memory to create the new entry. gateway uses the same route A change operation resulted in a route whose gateway uses the same route as the one being changed. The next-hop gateway should be reachable through a different route. The route utility exits 0 on success, and >0 if an error occurs. SEE ALSO netintro(4), route(4), arp(8), routed(8) HISTORY The route command appeared in 4.2BSD. BUGS The first paragraph may have slightly exaggerated routed(8)'s abilities. BSD 4.4 June 8, 2001 BSD 4.4
|
route – manually manipulate the routing tables
|
route [-dnqtv] command [[modifiers] args]
| null | null |
mount_webdav
|
The mount_webdav command mounts the WebDAV-enabled server directory at [scheme://]host[:port][/path] at the mount point indicated by node. The user and group IDs for all files and directories are set to unknown, and the permissions default to read, write and execute for user, group and other. The arguments and options are: -s Require that authentication credentials be sent securely to the server. Note: If this option is not set, sending authentication credentials insecurely to the server will be allowed but will be logged. -S Suppresses all user interface including the authentication dialogs and the non-responsive ("disconnect") server dialogs. If the server connection becomes non-responsive, the file system is immediately unmounted when this option has been used. -i Interactive mode, you are prompted for the username and password. -o Options passed to mount(2) are specified with the -o option followed by a comma-separated string of options. See the mount(8) man page for possible options and their meanings. If connecting to a Class 1 compliant WebDAV server, the rdonly option will be set even if it was not specified because mount_webdav will not allow files to be opened with write access on servers which do not support the DAV LOCK method. -v volume_name Allows the volume_name attribute (ATTR_VOL_NAME) returned by getattrlist(2) to be specified. If the volume_name is not specified, the last path component name of the node path is used as the volume_name. [scheme://]host[:port][/path] The WebDAV-enabled server directory (collection resource) to mount as a volume. The scheme, if specified, must be "http://" or "https://". If the scheme is not specified, then "http://" is used. If the port is not specified, then port 80 is used when the scheme is "http://" or port 443 is used when the scheme is "https://". If the path is not specified, then the path "/" is used. node Path to mount point. Note: The mount point directory must be created or exist before issuing the mount_webdav command.
|
mount_webdav – mount a WebDAV filesystem
|
mount_webdav [-s] [-S] [-i] [-v volume_name] [-o options] [scheme://]host[:port][/path] node
| null |
The following example illustrates how to mount the WebDAV-enabled server directory http://idisk.mac.com/membername/ at the mount point /Volumes/mntpnt/. Note: The mountpoint directory /Volumes/mntpnt/ must be created before issuing the mount_webdav command. mount_webdav http://idisk.mac.com/membername/ /Volumes/mntpnt/ DIAGNOSTICS The mount_webdav utility exits 0 on success, and >0 if an error occurs. Here is a list of common results (other error results not listed may be returned): 0 mount_webdav successfully mounted the server directory. [ENOENT] The server directory could not be mounted by mount_webdav because the node path is invalid. [ENODEV] The server directory could not be mounted by mount_webdav because it is not WebDAV-enabled or because it does not exist, or because node does not have proper access. [ECANCELED] The server directory could not be mounted by mount_webdav because the user did not provide proper authentication credentials. COMPATIBILITY As noted above, the -afd option is considered deprecated in Mac OS X 10.4 and may not be supported in future releases. Use the FSMountServerVolumeSync() and FSMountServerVolumeAsync() APIs in CarbonCore/Files.h instead. SEE ALSO mount(2), unmount(2), mount(8) getattrlist(2) HISTORY The mount_webdav command first appeared Mac OS X Version 10.0. Support for HTTP Digest Access authentication was added in Mac OS X Version 10.1.1. Support for the https URL scheme, and for additional authentication methods and proxies supported by the CFNetwork framework were added in Mac OS X Version 10.4. Mac OS X October 27, 2008 Mac OS X
|
fsck_hfs
|
The fsck_hfs utility verifies and repairs HFS+ file systems. The first form of fsck_hfs quickly checks the specified file systems to determine whether they were cleanly unmounted. The second form of fsck_hfs preens the specified file systems. It is normally started by fsck(8) run from /etc/rc.boot during automatic reboot, when a HFS file system is detected. When preening file systems, fsck_hfs will fix common inconsistencies for file systems that were not unmounted cleanly. If more serious problems are found, fsck_hfs does not try to fix them, indicates that it was not successful, and exits. The third form of fsck_hfs checks the specified file systems and tries to repair all detected inconsistencies. If no options are specified fsck_hfs will always check and attempt to fix the specified file systems. The options are as follows: -c size Specify the size of the cache used by fsck_hfs internally. Bigger size can result in better performance but can result in deadlock when used with -l option. Size can be specified as a decimal, octal, or hexadecimal number. If the number ends with a ``k'', ``m'', or ``g'', the number is multiplied by 1024 (1K), 1048576 (1M), or 1073741824 (1G), respectively. -d Display debugging information. This option may provide useful information when fsck_hfs cannot repair a damaged file system. -D flags Print extra debugging information. The flags are a bitmap that control which kind of debug information is printed. The following values are currently implemented: 0x0001 Informational messages 0x0002 Error messages 0x0010 Extended attributes related messages 0x0020 Overlapped extents related messages -b size Specify the size, in bytes, of the physical blocks used by the -B option. -B path Print the files containing the physical blocks listed in the file path. The file should contain one or more decimal, octal (with leading 0) or hexadecimal (with leading 0x) numbers separated by white space. The physical block numbers are relative to the start of the partition, so if you have block numbers relative to the start of the device, you will have to subtract the block number of the start of the partition. The size of a physical block is given with the -b option; the default is 512 bytes per block. -f When used with the -p option, force fsck_hfs to check `clean' file systems, otherwise it means force fsck_hfs to check and repair journaled HFS+ file systems. -g Causes fsck_hfs to generate its output strings in GUI format. This option is used when another application with a graphical user interface (like Mac OS X Disk Utility) is invoking the fsck_hfs tool. -x Causes fsck_hfs to generate its output strings in XML (plist) format. This option implies the -g option. -l Lock down the file system and perform a test-only check. This makes it possible to check a file system that is currently mounted, although no repairs can be made. -m mode Mode is an octal number that will be used to set the permissions for the lost+found directory when it is created. The lost+found directory is only created when a volume is repaired and orphaned files or directories are detected. fsck_hfs places orphaned files and directories into the lost+found directory (located at the root of the volume). The default mode is 01777. -p Preen the specified file systems. -q Causes fsck_hfs to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message is printed to standard output describing whether the volume was clean or dirty. -y Always attempt to repair any damage that is found. -n Never attempt to repair any damage that is found. -E Cause fsck_hfs to exit (with a value of 47) if it encounters any major errors. A ``major error'' is considered one which would impact using the volume in normal usage; an inconsistency which would not impact such use is considered ``minor'' for this option. Only valid with the -n option. -S Cause fsck_hfs to scan the entire device looking for I/O errors. It will attempt to map the blocks with errors to names, similar to the -B option. -R flags Rebuilds the requested btree. The following flags are supported: a Attribute btree c Catalog btree e Extents overflow btree Rebuilding a btree will only work if there is enough free space on the file system for the new btree file, and if fsck_hfs is able to traverse each of the nodes in the requested btree successfully. -r Rebuild the catalog btree. This is synonymous with -Rc. Because of inconsistencies between the block device and the buffer cache, the raw device should always be used. EXIT VALUES fsck_hfs indicates some status by exit value. The current list of exit status results is: 0 No errors found, or successfully repaired. 3 A quick-check (the -n option) found a dirty filesystem; no repairs were made. There is a potential corruption in the filesystem, and either the journal could not be read, or a runtime corruption was present so the HFS Volume Inconsistent bit was set. 4 During boot, the root filesystem was found to be dirty; repairs were made, and the filesystem was remounted. The system should be rebooted. 8 A corrupt filesystem was found during a check, or repairs did not succeed. 47 A major error was found with -E. SEE ALSO fsck(8) BUGS fsck_hfs is not able to fix some inconsistencies that it detects. HISTORY The fsck_hfs command appeared in Mac OS X Server 1.0 . Mac OS X October 27, 2020 Mac OS X
|
fsck_hfs – HFS file system consistency check
|
fsck_hfs -q [-df] special ... fsck_hfs -p [-df] special ... fsck_hfs [-n | -y | -r] [-dfgxlES] [-D flags] [-b size] [-B path] [-m mode] [-c size] [-R flags] special ...
| null | null |
nfsd
|
nfsd runs on an NFS server machine to service NFS and MOUNT protocol requests from NFS client machines. In order for a machine to act as an NFS server an NFS exports file, /etc/exports, must exist and the nfsd service must be enabled. nfsd listens for NFS service requests at the port indicated in the NFS server specification (2049) and the mountd thread listens for MOUNT service requests at an available port registered with portmap(8). For more information on the NFS and MOUNT protocols see Network File System Protocol Specification, RFC1094 and NFS: Network File System Version 3 Protocol Specification. The nfsd daemon is a multi-threaded process that includes a number of threads processing NFS requests, a thread to accept new socket connections and a thread that processes NFS MOUNT protocol requests. When nfsd is started, it loads the export host addresses and options into the kernel using the nfssvc(2) system call. After changing the list of exports (either directly or indirectly via a change in netgroup membership), a hangup signal should be sent to the daemon to get it to reload the export information. This can be accomplished with the update command described below. Any errors encountered while processing the export entries will be logged via syslog(3). nfsd is normally launched by launchd(8); however, the nfsd command may also be used to manipulate the service using the following commands: enable Enables the nfsd service. disable Disables the nfsd service. start Starts the nfsd service. Note: if the service is disabled it will not be restarted on reboot. Use the enable command to make the change permanent. stop Stops the nfsd service. Note: if the service is enabled it will be restarted on reboot. Use the disable command to make the change permanent. restart Restarts the nfsd service (by stopping the service - it will restart automatically if the /etc/exports file exists). update Sends a SIGHUP to the running nfsd daemon to cause it to update its configuration. status Displays whether the nfsd service is enabled and whether the nfsd daemon is currently running. checkexports Checks the exports file and reports any errors (to stderr). Note that this can be useful to verify the validity of an alternate exports file (using the -F option below) prior to putting the changes in place and updating nfsd. verbose [up|down]+ Sends USR1 and/or USR2 signal(s) to the running nfsd daemon to cause it to increase and/or decrease its logging level. (See below for details about nfsd's logging). Logging is performed via syslog(3) using the LOG_DAEMON facility. By default, only messages up to priority LOG_WARNING are logged. Setting the verbose level to one will add LOG_NOTICE messages which includes logging failed mount attempts. A verbose level of two will increase the log level to LOG_INFO which includes logging successful mount attempts. A log level of three or more will add LOG_DEBUG messages and cause increasing amounts of debug information to be logged. The debug information exposes lots of information about nfsd's inner workings which is typically only useful to developers. Note: the syslog(8) configuration may need to be adjusted in order to see the increased verbosity. The nfsd utility exits 0 on success, and >0 if an error occurs. When given the status command, it exits 0 if the service is enabled, and 1 if the service is disabled. The following is a list of command line options that are available. However, since nfsd is normally started by launchd(8), configuration of these options should be controlled using the equivalent settings in the NFS configuration file (see nfs.conf(5)). -F exports_file The exports_file argument specifies an alternate location for the exports file (useful with the checkexports command). -N Allow non-root mount requests to be served. This should only be specified if there are clients that require it. -P # Specifies which port to use for the MOUNT service. -R Allow mount RPCs requests for regular files to be served. Although this seems to violate the mount protocol specification, some diskless workstations do mount requests for their swapfiles and expect them to be regular files. Since a regular file cannot be specified in /etc/exports, the -alldirs option will need to be used on the export in which the swap files reside. -n # Specifies how many NFS server threads to create. -p # Specifies which port to use for the NFS service (instead of the default of 2049). -r Register the NFS service with portmap(8). This option can be used to re-register the NFS services if the portmap server is restarted. This option is equivalent to the update command. -t Serve TCP NFS clients. Note: only TCP will be used if no other options are specified. -u Serve UDP NFS clients. Note: only UDP will be used if no other options are specified. -v Increase nfsd's logging level by one (may be used multiple times). CONFIGURATION Unless otherwise specified, eight NFS server threads are started and both UDP and TCP transports are supported. A server should run enough threads to handle the maximum level of concurrency from its clients. See nfs.conf(5) for a list of tunable parameters. NOTES The exports list displayed via showmount(8) may contain additional information about the status of each export. This information is reported as entries in the export's group list. If an export is currently unavailable, the group list will begin with the entry "<offline>" (or "<offline*>" if it is unavailable to some but not all clients exported to). If an export allows non-default security mechanisms, the group list will contain an entry indicating what security mechanisms are allowed. For example: "<krb5:sys>". The mechanisms are listed in no particular order and may not be available to all clients. If an export is available to all clients, the group list is usually empty. But if additional status information is returned in the group list, then the list will also contain an explicit "(Everyone)" entry to indicate that the export is available to all clients. If nfsd does not have read access to an export, mount would fail with "Permission denied" and checkexports command would report the following error: sandbox_check failed. nfsd has no read access to <path> This could be resolved by granting nfsd "Full Disk Access" under "Privacy" tab of the "Security & Privacy" preference in the "System Preferences" followed by restart of nfsd service. FILES /etc/exports The list of exported filesystems. /var/run/nfsd.pid The pid of the currently running nfsd. /var/run/mountd.pid The pid of the currently running mountd (provided for backwards compatibility with scripts that may HUP mountd to update exports). /var/run/mountdtab The current list of outstanding mounts served. /var/run/mountdexptab Information about exported file systems and directories (UUIDs, handles, ...). /System/Library/LaunchDaemons/com.apple.nfsd.plist The nfsd service's property list file for launchd(8). SEE ALSO exports(5), nfs.conf(5), showmount(8), nfsstat(1), nfssvc(2), portmap(8), rpc.rquotad(8), launchd(8) HISTORY The nfsd and mountd utilities first appeared in 4.4BSD. mountd functionality was merged into nfsd in Darwin 9. macOS 14.5 November 10, 2008 macOS 14.5
|
nfsd – NFS server daemon
|
nfsd [command] nfsd [-F exports_file] checkexports nfsd [-NRrtuv] [-F exports_file] [-n num_servers] [-p nfsport] [-P mountport] [command]
| null | null |
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. When the system is halted with the halt command, the system is powered off. The options are as follows: -l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call halt or reboot and log this themselves. -N The file system cache is not flushed during the initial process clean-up, however the kernel level reboot(2) is still processed with a sync. This option can be useful for performing a “best-effort” reboot when devices might be unavailable. This can happen when devices have been disconnected. -n The file system cache is not flushed. This option should probably not be used. -q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n option is not specified). This option should probably not be used. Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom and cleanly terminating specific programs. SIGTERM TO SIGKILL INTERVAL The SIGKILL will follow the SIGTERM by an intentionally indeterminate period of time. Programs are expected to take only enough time to flush all dirty data and exit. Developers are encouraged to file a bug with the OS vendor, should they encounter an issue with this functionality. SEE ALSO getutxent(3), wtmp(5), shutdown(8), sync(8) HISTORY A reboot utility appeared in 4.0BSD. macOS 14.5 June 6, 2023 macOS 14.5
|
halt, reboot – stopping and restarting the system
|
halt [-lNnq] reboot [-lNnq]
| null | null |
nfsiod
|
nfsiod is deprecated. See nfs.conf(5) for NFS configuration info. nfsiod controls the maximum number of asynchronous I/O threads used for NFS mounts. Historically, it has consisted of a daemon that never exits. However, asynchronous I/O requests are now serviced by threads launched on demand in the kernel and the nfsiod command simply sets the configuration limit. Having asynchronous I/O threads improves performance but is not required for correct operation. The options are as follows: -n Specify maximum number of asynchronous I/O threads to be used. If no maximum is specified, nfsiod displays the current value. The default value is 16. A client should allow enough threads to handle its maximum level of concurrency. The nfsiod utility exits 0 on success, and >0 if an error occurs. SEE ALSO nfs.conf(5), mount_nfs(8), nfsstat(1) HISTORY The nfsiod utility first appeared in 4.4BSD. It's use was deprecated in Darwin 9. macOS 14.5 October 25, 2006 macOS 14.5
|
nfsiod – local NFS asynchronous I/O
|
nfsiod [-n num_threads]
| null | null |
fsck_cs
|
The fsck_cs utility verifies and repairs CoreStorage logical volume group metadata. The device parameter(s) should be path(s) to the "raw" (character special) disk device(s) such as /dev/rdisk1s1 that constitute the CoreStorage logical volume group. If you specify a "non-raw" (block special) path such as /dev/disk1s1, or just the disk name such as disk1s1, it will automatically be converted to the corresponding raw disk device (/dev/rdisk1s1). The options are as follows: -q Performs a "quick" check and indicates if any corruptions were found via the exit status. In this mode stale MLV segments are not checked, nor is proactive MLV mirror scrubbing performed. -p Operates in "preen" mode. MLV mirror blocks are repaired where necessary. Newer transactions may be invalidated to force a roll-back to an older, but consistent, filesystem state. -y Causes fsck_cs to assume "yes" as the answer to all questions. In other words, always attempt to repair any errors that are found. -n Causes fsck_cs to assume "no" as the answer to all questions. In other words, never attempt to repair any errors that are found. -x Causes fsck_cs to produce its output in an XML-like (plist) format. This option is used when another application with a graphical user interface (like OS X Disk Utility) is invoking the fsck_cs tool and processing the output. -g Causes fsck_cs to produce its output in GUI-compatible form. This is similar in usage to the -x option. -l logfile Reproduce all console output, as well as additional status and error messages, to the specified file. Alternatively device can be specified as the UUID of the CoreStorage logical volume group or as the name of a CoreStorage-hosted logical volume within that group, causing fsck_cs to derive the constituent raw device(s) from the IORegistry. In these cases you must indicate what object is being supplied to identify the logical volume group: --pv the component CoreStorage physical volume(s) directly --uuid the CoreStorage logical volume group (as a UUID) --lv a CoreStorage logical volume (as a device name) DIAGNOSTICS The fsck_cs utility exits with 0 if no corruption was detected or if all corruptions were repaired, and with >0 if any unrepaired corruption remains. BUGS fsck_cs does not perform an exhaustive validation, nor is it able to fix many of the inconsistencies that it does detect. HISTORY The fsck_cs utility first appeared along with CoreStorage in OS X 10.7.0. OS X July 22, 2011 OS X
|
fsck_cs – verify and repair CoreStorage logical volume groups
|
fsck_cs -q device ... fsck_cs -p device ... fsck_cs [-y | -n] [-x | -g] [-l logfile] device ...
| null | null |
fsck_apfs
|
The fsck_apfs utility verifies and repairs APFS containers and volumes. fsck_apfs checks the specified APFS containers and volumes and tries to repair all detected inconsistencies. Because of inconsistencies between the block device and the buffer cache, the raw device should always be used. In its current state, fsck_apfs checks the integrity of various container data structures. The options are as follows: -q Causes fsck_apfs to quickly check whether the device is `clean'. If device is an APFS volume, fsck_apfs will quickly check the APFS container and the specified APFS volume. If device is an APFS container, fsck_apfs will quickly check the APFS container and all the APFS volumes in it. By default, no repairs are attempted during a quick check. -n Never attempt to repair any damage that is found. -y Always attempt to repair any damage that is found. -l Enable live verification mode. This makes it possible to check an APFS container which is currently mounted read-write, although no repairs can be made. Note that live verification mode may cause your system to stop responding until fsck_apfs completes. -s Print space verification summary. -S Skip iteration of snapshots (top-level snapshot structures will still be checked), although no repairs can be made. -o Repair overallocations; please do not run an older fsck_apfs on newer systems with this option. -b <num> Set the default cache block size to num KB. -c Enable the gathering and printing of cache statistics. -C Force a sync of the container prior to freezing it in live verification mode. -d Print extra debugging information. -E <path> Write warning and error summary information to path in addition to the standard location (/var/log/fsck_apfs_error.log). Pass - to write it to stdout. -F Force checking of encrypted volumes, requiring the volumes to be unlocked. -M Skip checks requiring decryption of volume data. Unencrypted volume metadata is still checked. -g Use "GUI" mode for the output. Output is in a form suitable for parsing by other programs. -x Output will be in XML. -W Treat warnings as fatal. By default, fsck_apfs will exit with a return code of 0 if there are warnings but no errors. This option will cause it to exit with an appropriate error code in that situation. -T Enable B-Tree node repairs. Only used when repairing so either -y must be present, or both -n and -q must be absent. -D When doing B-Tree node repairs, allow searching free blocks for candidate nodes. This requires the -T option as well. EXIT STATUS fsck_apfs exits with 0 on success, and >0 if error occurs. SEE ALSO fsck(8) Mac OS X May 6, 2023 Mac OS X
|
fsck_apfs – APFS consistency check
|
fsck_apfs [-n | -y] [-q] [-l] [-s] [-S] [-o] [-b num] [-c] [-C] [-d] [-E path] [-F | -M] [-g | -x] [-W] [-T] [-D] device
| null | null |
fstyp_msdos
|
The fstyp_msdos utility is not intended to be run directly, but rather called by fstyp(8) while it is trying to determine which file system type is present on the given device. It returns 1 if it thinks the device contains an MSDOS FAT volume, and 0 otherwise. SEE ALSO fstyp(8) macOS 14.5 August 15, 2005 macOS 14.5
|
fstyp_msdos – check for an MSDOS FAT volume
|
fstyp_msdos device
| null | null |
disklabel
|
The disklabel utility manipulates ``Apple Label'' partition metadata. ``Apple Label'' partitions allow for a disk device to have a consistent name, ownership, and permissions across reboots, even though uses a dynamic pseudofilesystem for /dev. The ``Apple Label'' partition uses a set of metadata (as a plist) in a reserved area of the partition. This metadata describes the owner, name, and so forth. When -create is used, the -msize argument can specify the size of metadata area; the default is 128Kbytes. The default size unit is bytes, but the following suffixes may be used to multiply by the given factor: ``b'' (512), ``k'' (1024), ``m'' (1048576), and ``g'' (1073741824). Although any key-value pair can be specified for the properties, certain keys are used by the system: owner-uid The user (as either a string or numeric value) to own the device. owner-gid The group (as either a string or numeric value) associated with the device. owner-mode The permissions (as a numeric value) for the device. dev-name The name for the device. If the owner-uid and owner-gid properties are given as strings, the disklabel utility will attempt to look up the names (as users or groups, as appropriate), and will store the numeric values in the metadata. If it cannot find the names, and the values are not given as numbers, it will print an error, and not store the key/value pairs in the metadata. The owner-mode property may be given in decimal, or in octal by using a preceding ``0'' (e.g., ``0666''). Any property may be forced to be treated as a string by enclosing it in double-quotation marks; bear in mind that shell escapes will probably be necessary in this sitation. The -properties directive can print out all keys (if no arguments are given), a requested set of keys (if a list of key names is given), or can modify (or add) keys (if a key-value pairs are given). disklabel also maintains a checksum of the metadata; the -status directive verifies this checksum.
|
disklabel – manipulate and query an Apple Label disk label
|
disklabel -create disk-device [-msize=size] [property=value] [...] disklabel -status disk-device disklabel -properties disk-device [property[=value]] [...] disklabel -destroy disk-device
| null |
The following example will create a device with 1MByte of metadata area, owned by fred, with a device name of fred, and be writable by fred: disklabel -create /dev/rdisk1s1 -msize=1M owner-uid=fred dev-name=fred owner-mode=0644 The following example will then print out the key-value pairs from the above: disklabel -properties /dev/rdisk1s1 SEE ALSO pdisk(8) macOS 14.5 September 3, 2004 macOS 14.5
|
mount_lifs
| null | null | null | null | null |
mount_msdos
|
The mount_msdos command attaches the MS-DOS filesystem residing on the device special to the global filesystem namespace at the location indicated by node. This command is normally executed by mount(8) at boot time, but can be used by any user to mount an MS-DOS file system on any directory that they own (provided, of course, that they have appropriate access to the device that contains the file system). The options are as follows: -o options Use the specified mount options, as described in mount(8). -u uid Set the owner of the files in the file system to uid. The default owner is the owner of the directory on which the file system is being mounted. -g gid Set the group of the files in the file system to gid. The default group is the group of the directory on which the file system is being mounted. -m mask Specify the maximum file permissions for files in the file system. (For example, a mask of 755 specifies that, by default, the owner should have read, write, and execute permissions for files, but others should only have read and execute permissions. See chmod(1) for more information about octal file modes.) Only the nine low-order bits of mask are used. The default mask is taken from the directory on which the file system is being mounted. SEE ALSO mount(2), unmount(2), fstab(5), mount(8) CAVEATS FreeBSD 2.1 and earlier versions could not handle cluster sizes larger than 16K. Just mounting an MS-DOS file system could cause corruption to any mounted file system. Cluster sizes larger than 16K are unavoidable for file system sizes larger than 1G, and also occur when filesystems larger than 1G are shrunk to smaller than 1G using FIPS. HISTORY The mount_msdos utility first appeared in FreeBSD 2.0. Its predecessor, the mount_pcfs utility appeared in FreeBSD 1.0, and was abandoned in favor of the more aptly-named mount_msdos. macOS 14.5 April 7, 1994 macOS 14.5
|
mount_msdos – mount an MS-DOS file system
|
mount_msdos [-o options] [-u uid] [-g gid] [-m mask] special node
| null | null |
fsck_msdos
|
The fsck_msdos utility verifies and repairs FAT file systems (more commonly known as DOS file systems). The first form of fsck_msdos quickly checks the specified file systems to determine whether they were cleanly unmounted. The second form of fsck_msdos preens the specified file systems. It is normally started by fsck(8) run from /etc/rc.boot during automatic reboot, when a FAT file system is detected. When preening file systems, fsck_msdos will fix common inconsistencies non-interactively. If more serious problems are found, fsck_msdos does not try to fix them, indicates that it was not successful, and exits. The third form of fsck_msdos checks the specified file systems and tries to repair all detected inconsistencies, requesting confirmation before making any changes. The default behavior is to always ask for confirmation of each change. Use the -n or -y options to override this default behavior. The options are as follows: -q Causes fsck_msdos to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message is printed to standard output describing whether the volume was clean or dirty. -f This option is ignored by fsck_msdos and is present only for compatibility with programs that check other file system types for consistency. -n Causes fsck_msdos to assume no as the answer to all operator questions, except “CONTINUE?”. -p Preen the specified file systems. -y Causes fsck_msdos to assume yes as the answer to all operator questions. EXIT VALUES fsck_msdos exits with a value of 0 when the filesystem is clean (or has been repaired), and 8 otherwise. SEE ALSO fsck(8) BUGS fsck_msdos is still under construction. NetBSD 1.1 August 13, 1995 NetBSD 1.1
|
fsck_msdos – DOS/Windows (FAT) file system consistency check
|
fsck_msdos -q special ... fsck_msdos -p [-f] special ... fsck_msdos [-fny] special ...
| null | null |
ifconfig
|
The ifconfig utility is used to assign an address to a network interface and/or configure network interface parameters. The following options are available: address For the DARPA-Internet family, the address is either a host name present in the host name data base, hosts(5), or a DARPA Internet address expressed in the Internet standard “dot notation”. It is also possible to use the CIDR notation (also known as the slash notation) to include the netmask. That is, one can specify an address like 192.168.0.1/16. For the “inet6” family, it is also possible to specify the prefix length using the slash notation, like ::1/128. See the prefixlen parameter below for more information. The link-level (“link”) address is specified as a series of colon-separated hex digits. This can be used to e.g. set a new MAC address on an ethernet interface, though the mechanism used is not ethernet-specific. If the interface is already up when this option is used, it will be briefly brought down and then brought back up again in order to ensure that the receive filter in the underlying ethernet hardware is properly reprogrammed. address_family Specify the address family which affects interpretation of the remaining parameters. Since an interface can receive transmissions in differing protocols with different naming schemes, specifying the address family is recommended. The address or protocol families currently supported are “inet”, “inet6”, and “link”. The default is “inet”. “ether” and “lladdr” are synonyms for “link”. dest_address Specify the address of the correspondent on the other end of a point to point link. interface This parameter is a string of the form “name unit”, for example, “en0”. The following parameters may be set with ifconfig: add Another name for the alias parameter. Introduced for compatibility with BSD/OS. alias Establish an additional network address for this interface. This is sometimes useful when changing network numbers, and one wishes to accept packets addressed to the old interface. If the address is on the same subnet as the first network address for this interface, a non-conflicting netmask must be given. Usually 0xffffffff is most appropriate. -alias Remove the network address specified. This would be used if you incorrectly specified an alias, or it was no longer needed. If you have incorrectly set an NS address having the side effect of specifying the host portion, removing all NS addresses will allow you to respecify the host portion. anycast (Inet6 only.) Specify that the address configured is an anycast address. Based on the current specification, only routers may configure anycast addresses. Anycast address will not be used as source address of any of outgoing IPv6 packets. arp Enable the use of the Address Resolution Protocol (arp(4)) in mapping between network level addresses and link level addresses (default). This is currently implemented for mapping between DARPA Internet addresses and IEEE 802 48-bit MAC addresses (Ethernet, FDDI, and Token Ring addresses). -arp Disable the use of the Address Resolution Protocol (arp(4)). broadcast (Inet only.) Specify the address to use to represent broadcasts to the network. The default broadcast address is the address with a host part of all 1's. debug Enable driver dependent debugging code; usually, this turns on extra console error logging. -debug Disable driver dependent debugging code. delete Another name for the -alias parameter. down Mark an interface “down”. When an interface is marked “down”, the system will not attempt to transmit messages through that interface. If possible, the interface will be reset to disable reception as well. ether Another name for the lladdr parameter. lladdr addr Set the link-level address on an interface. This can be used to e.g. set a new MAC address on an ethernet interface, though the mechanism used is not ethernet-specific. The address addr is specified as a series of colon-separated hex digits. If the interface is already up when this option is used, it will be briefly brought down and then brought back up again in order to ensure that the receive filter in the underlying ethernet hardware is properly reprogrammed. media type If the driver supports the media selection system, set the media type of the interface to type. Some interfaces support the mutually exclusive use of one of several different physical media connectors. For example, a 10Mbit/s Ethernet interface might support the use of either AUI or twisted pair connectors. Setting the media type to 10base5/AUI would change the currently active connector to the AUI port. Setting it to 10baseT/UTP would activate twisted pair. Refer to the interfaces' driver specific documentation or man page for a complete list of the available types. mediaopt opts If the driver supports the media selection system, set the specified media options on the interface. The opts argument is a comma delimited list of options to apply to the interface. Refer to the interfaces' driver specific man page for a complete list of available options. -mediaopt opts If the driver supports the media selection system, disable the specified media options on the interface. rxcsum, txcsum If the driver supports user-configurable checksum offloading, enable receive (or transmit) checksum offloading on the interface. Some drivers may not be able to enable these flags independently of each other, so setting one may also set the other. The driver will offload as much checksum work as it can reliably support, the exact level of offloading varies between drivers. -rxcsum, -txcsum If the driver supports user-configurable checksum offloading, disable receive (or transmit) checksum offloading on the interface. These settings may not always be independent of each other. tso If the driver supports tcp(4) segmentation offloading, enable TSO on the interface. Some drivers may not be able to support TSO for ip(4) and ip6(4) packets, so they may enable only one of them. -tso If the driver supports tcp(4) segmentation offloading, disable TSO on the interface. It will always disable TSO for ip(4) and ip6(4). lro If the driver supports tcp(4) large receive offloading, enable LRO on the interface. -lro If the driver supports tcp(4) large receive offloading, disable LRO on the interface. av If supported by the driver, enable 802.1 AVB on the interface. -av If supported by the driver, disable 802.1 AVB on the interface. vlanmtu, vlanhwtag If the driver offers user-configurable VLAN support, enable reception of extended frames or tag processing in hardware, respectively. Note that this must be issued on a physical interface associated with vlan(4), not on a vlan(4) interface itself. -vlanmtu, -vlanhwtag If the driver offers user-configurable VLAN support, disable reception of extended frames or tag processing in hardware, respectively. create Create the specified network pseudo-device. If the interface is given without a unit number, try to create a new device with an arbitrary unit number. If creation of an arbitrary device is successful, the new device name is printed to standard output unless the interface is renamed or destroyed in the same ifconfig invocation. destroy Destroy the specified network pseudo-device. plumb Another name for the create parameter. Included for Solaris compatibility. unplumb Another name for the destroy parameter. Included for Solaris compatibility. metric n Set the routing metric of the interface to n, default 0. The routing metric is used by the routing protocol (routed(8)). Higher metrics have the effect of making a route less favorable; metrics are counted as additional hops to the destination network or host. mtu n Set the maximum transmission unit of the interface to n, default is interface specific. The MTU is used to limit the size of packets that are transmitted on an interface. Not all interfaces support setting the MTU, and some interfaces have range restrictions. netmask mask (Inet only.) Specify how much of the address to reserve for subdividing networks into sub-networks. The mask includes the network part of the local address and the subnet part, which is taken from the host field of the address. The mask can be specified as a single hexadecimal number with a leading ‘0x’, with a dot-notation Internet address, or with a pseudo-network name listed in the network table networks(5). The mask contains 1's for the bit positions in the 32-bit address which are to be used for the network and subnet parts, and 0's for the host part. The mask should contain at least the standard network portion, and the subnet field should be contiguous with the network portion. The netmask can also be specified in CIDR notation after the address. See the address option above for more information. prefixlen len (Inet6 only.) Specify that len bits are reserved for subdividing networks into sub-networks. The len must be integer, and for syntactical reason it must be between 0 to 128. It is almost always 64 under the current IPv6 assignment rule. If the parameter is omitted, 64 is used. The prefix can also be specified using the slash notation after the address. See the address option above for more information. remove Another name for the -alias parameter. Introduced for compatibility with BSD/OS. link[0-2] Enable special processing of the link level of the interface. These three options are interface specific in actual effect, however, they are in general used to select special modes of operation. An example of this is to enable SLIP compression, or to select the connector type for some Ethernet cards. Refer to the man page for the specific driver for more information. -link[0-2] Disable special processing at the link level with the specified interface. up Mark an interface “up”. This may be used to enable an interface after an “ifconfig down”. It happens automatically when setting the first address on an interface. If the interface was reset when previously marked down, the hardware will be re-initialized. The following parameters are for ICMPv6 Neighbor Discovery Protocol. Note that the address family keyword “inet6” is needed for them: nud Perform network unreachability detection (NUD). -nud Do not perform network unreachability detection (NUD). ifdisabled Disable all IPv6 communication on the interface. -ifdisabled Do not disable all IPv6 communication on the interface. insecure Disable the processing of Secure Neighbor Discovery (SEND). -insecure Do not disabled the processing of Secure Neighbor Discovery (SEND). dad Perform duplicate address detection (DAD). -dad Do not perform duplicate address detection (DAD). replicated Modify duplicate address detection (DAD) protocol to expect that interface configuration is replicated at a network sleep proxy. Ignores certain NA messages and disables optimistic DAD. -replicated Do not use modified duplicated address detection (DAD) protocol. The following parameters are specific to link aggregate interfaces: bonddev iface If the interface is a bond pseudo device, associate physical interface iface with it. By default, the bond pseudo device is in LACP (Link Aggregation Control Protocol) mode (see bondmode below). In this mode, the device conforms to the IEEE 802.3ad Link Aggregation specification. If this is the first physical interface to be associated with the bond interface, the bond interface inherits the ethernet address from the physical interface. Physical interfaces that are added to the bond have their ethernet address re-programmed so that all members of the bond have the same ethernet address. If the physical interface is subsequently removed from the bond using -bonddev, a new ethernet address is chosen from the remaining interfaces, and all interfaces are re-programmed again with the new ethernet address. If no remaining interfaces exist, the bond interface's ethernet address is cleared. If the specified physical interface iface is not capable of having its ethernet address re-programmed, the bonddev command will fail. Once the physical interface iface is successfully associated with the bond interface, all received packets are diverted to the bond interface. The physical interface is no longer useable on its own, and remains that way until it is removed from the bond using -bonddev. It is possible that the specified interface iface is not capable of aggregating, and may remain unused until the operating conditions change. The link status of the bond interface depends on the state of link aggregation. If no active partner is detected, the link status will remain inactive. To monitor the 802.3ad Link Aggregation state, use the -b option. A physical interface that is associated with a vlan pseudo device cannot at the same time be associated with a bond pseudo device. A physical interface cannot be associated with more than one bond pseudo device at the same time. It is not possible to associate a bond with pseudo interfaces such as vlan. Only physical ethernet interfaces may be associated with a bond. -bonddev iface If the interface is a bond pseudo device, disassociate the physical interface iface from it. Before the interface is removed from the bond, the bond device announces to the link partner that the interface is now individual and no longer aggregatable. If the physical iface is the last interface in the bond, the bond interface clears its link address. bondmode lacp | static If the interface is a bond pseudo device, this option will set the mode on the bond interface. The two currently supported modes are lacp and static. The default mode is lacp. To enable static mode (and turn off LACP), specify static. In static mode, a member interface is made an active part of the link aggregate as long as the link status is active. To re-enable LACP mode, specify lacp. The following parameters are specific to IP tunnel interfaces, gif(4): tunnel src_addr dest_addr Configure the physical source and destination address for IP tunnel interfaces. The arguments src_addr and dest_addr are interpreted as the outer source/destination for the encapsulating IPv4/IPv6 header. -tunnel Unconfigure the physical source and destination address for IP tunnel interfaces previously configured with tunnel. deletetunnel Another name for the -tunnel parameter. The following parameters are specific to bridge interfaces: addm interface Add the interface named by interface as a member of the bridge. The interface is put into promiscuous mode so that it can receive every packet sent on the network. deletem interface Remove the interface named by interface from the bridge. Promiscuous mode is disabled on the interface when it is removed from the bridge. maxaddr size Set the size of the bridge address cache to size. The default is 100 entries. timeout seconds Set the timeout of address cache entries to seconds seconds. If seconds is zero, then address cache entries will not be expired. The default is 240 seconds. addr Display the addresses that have been learned by the bridge. static interface-name address Add a static entry into the address cache pointing to interface-name. Static entries are never aged out of the cache or re-placed, even if the address is seen on a different interface. deladdr address Delete address from the address cache. flush Delete all dynamically-learned addresses from the address cache. flushall Delete all addresses, including static addresses, from the address cache. discover interface Mark an interface as a “discovering” interface. When the bridge has no address cache entry (either dynamic or static) for the destination address of a packet, the bridge will forward the packet to all member interfaces marked as “discovering”. This is the default for all interfaces added to a bridge. -discover interface Clear the “discovering” attribute on a member interface. For packets without the “discovering” attribute, the only packets forwarded on the interface are broadcast or multicast packets and packets for which the destination address is known to be on the interface's segment. learn interface Mark an interface as a “learning” interface. When a packet arrives on such an interface, the source address of the packet is entered into the address cache as being a destination address on the interface's segment. This is the default for all interfaces added to a bridge. -learn interface Clear the “learning” attribute on a member interface. stp interface Enable Spanning Tree protocol on interface. The if_bridge(4) driver has support for the IEEE 802.1D Spanning Tree protocol (STP). Spanning Tree is used to detect and remove loops in a network topology. -stp interface Disable Spanning Tree protocol on interface. This is the default for all interfaces added to a bridge. maxage seconds Set the time that a Spanning Tree protocol configuration is valid. The default is 20 seconds. The minimum is 6 seconds and the maximum is 40 seconds. fwddelay seconds Set the time that must pass before an interface begins forwarding packets when Spanning Tree is enabled. The default is 15 seconds. The minimum is 4 seconds and the maximum is 30 seconds. hellotime seconds Set the time between broadcasting of Spanning Tree protocol configuration messages. The hello time may only be changed when operating in legacy stp mode. The default is 2 seconds. The minimum is 1 second and the maximum is 2 seconds. priority value Set the bridge priority for Spanning Tree. The default is 32768. The minimum is 0 and the maximum is 61440. ifpriority interface value Set the Spanning Tree priority of interface to value. The default is 128. The minimum is 0 and the maximum is 240. ifpathcost interface value Set the Spanning Tree path cost of interface to value. The default is calculated from the link speed. To change a previously selected path cost back to automatic, set the cost to 0. The minimum is 1 and the maximum is 200000000. ifmaxaddr interface size Set the maximum number of hosts allowed from an interface, packets with unknown source addresses are dropped until an existing host cache entry expires or is removed. Set to 0 to disable. hostfilter interface address Configure the bridge to accept incoming packet on the interface only if they match the given MAC address and IP address -- use the command twice to set both type of addresses. Other filtering restrictions apply. -hostfilter interface Allow traffic from any host on that interface. The following parameters are specific to vlan interfaces: vlan vlan_tag Set the VLAN tag value to vlan_tag. This value is a 16-bit number which is used to create an 802.1Q VLAN header for packets sent from the vlan(4) interface. Note that vlan and vlandev must both be set at the same time. vlandev iface Associate the physical interface iface with a vlan(4) interface. Packets transmitted through the vlan(4) interface will be diverted to the specified physical interface iface with 802.1Q VLAN encapsulation. Packets with 802.1Q encapsulation received by the parent interface with the correct VLAN tag will be diverted to the associated vlan(4) pseudo-interface. The vlan(4) interface is assigned a copy of the parent interface's flags and the parent's ethernet address. The vlandev and vlan must both be set at the same time. If the vlan(4) interface already has a physical interface associated with it, this command will fail. To change the association to another physical interface, the existing association must be cleared first. Note: if the hardware tagging capability is set on the parent interface, the vlan(4) pseudo interface's behavior changes: the vlan(4) interface recognizes that the parent interface supports insertion and extraction of VLAN tags on its own (usually in firmware) and that it should pass packets to and from the parent unaltered. -vlandev [iface] If the driver is a vlan(4) pseudo device, disassociate the parent interface from it. This breaks the link between the vlan(4) interface and its parent, clears its VLAN tag, flags and its link address and shuts the interface down. The iface argument is useless and hence deprecated. tbr rate Set a token bucket regulator that limits the egress bandwidth to rate, measured in bps, Kbps, Mbps or Gbps. If the specified rate is zero, the token bucket regulator is disabled. The ifconfig utility displays the current configuration for a network interface when no optional parameters are supplied. If a protocol family is specified, ifconfig will report only the details specific to that protocol family. If the -m flag is passed before an interface name, ifconfig will display the capability list and all of the supported media for the specified interface. If -L flag is supplied, address lifetime is displayed for IPv6 addresses, as time offset string. Optionally, the -a flag may be used instead of an interface name. This flag instructs ifconfig to display information about all interfaces in the system. The -d flag limits this to interfaces that are down, and -u limits this to interfaces that are up. When no arguments are given, -a is implied. The -l flag may be used to list all available interfaces on the system, with no other additional information. Use of this flag is mutually exclusive with all other flags and commands, except for -d (only list interfaces that are down) and -u (only list interfaces that are up). The -v flag may be used to get more verbose status for an interface. The -C flag may be used to list all of the interface cloners available on the system, with no additional information. Use of this flag is mutually exclusive with all other flags and commands. The -r flag may be used to show additional information related to the count of route references on the network interface. For bridge interfaces, the list of addresses learned by the bridge is not shown when displaying information about all interfaces except when the -v flag is used. The -X flag may be used to list interfaces whose names match the regular expression in the pattern. See re_format(7) for more information on regular expressions. This flag may be used with the -a flag and the -l flag to further restrict the set of interfaces to be listed. The -f flag may be used to control the output format of ifconfig. The format is specified as a comma-separated list of type:format pairs (see the EXAMPLES section for more information). The -f flag can be supplied multiple times. The types and their associated format strings are: addr Adjust the display of inet and inet6 addresses: default Default format, numeric fqdn Fully qualified domain names (FQDN) host Unqualified hostnames numeric Numeric format ether Adjust the display of link-level ethernet (MAC) addresses: colon Separate address segments with a colon dash Separate address segments with a dash default Default format, colon inet Adjust the display of inet address subnet masks: cidr CIDR notation, for example: ‘203.0.113.224/26’ default Default format, hex dotted Dotted quad notation, for example: ‘255.255.255.192’ hex Hexadecimal format, for example: ‘0xffffffc0’ inet6 Adjust the display of inet6 address prefixes (subnet masks): cidr CIDR notation, for example: ‘::1/128’ or ‘fe80::1%lo0/64’ default Default format, numeric numeric Integer format, for example: ‘prefixlen 64’ Only the super-user may modify the configuration of a network interface. NOTES The media selection system is relatively new and only some drivers support it (or have need for it).
|
ifconfig – configure network interface parameters
|
ifconfig [-L] [-m] [-r] [-f type:format] interface [create] [address_family] [address [dest_address]] [parameters] ifconfig interface destroy ifconfig -a [-L] [-d] [-m] [-r] [-u] [-v] [-f type:format] [address_family] ifconfig -l [-d] [-u] [address_family] ifconfig [-L] [-d] [-m] [-r] [-u] [-v] [-C] [-f type:format] ifconfig interface vlan vlan-tag vlandev iface ifconfig interface -vlandev iface ifconfig interface bonddev iface ifconfig interface -bonddev iface ifconfig interface bondmode lacp | static ifconfig -X pattern [parameters]
| null |
Assign the IPv4 address 192.0.2.10, with a network mask of 255.255.255.0, to the interface en0: # ifconfig en0 inet 192.0.2.10 netmask 255.255.255.0 Add the IPv4 address 192.0.2.45, with the CIDR network prefix /28, to the interface en0, using add as a synonym for the canonical form of the option alias: # ifconfig en0 inet 192.0.2.45/28 add Remove the IPv4 address 192.0.2.45 from the interface en0: # ifconfig en0 inet 192.0.2.45 -alias Add the IPv6 address 2001:DB8:DBDB::123/48 to the interface en0: # ifconfig en0 inet6 2001:db8:bdbd::123 prefixlen 48 alias Note that lower case hexadecimal IPv6 addresses are acceptable. Remove the IPv6 address added in the above example, using the / character as shorthand for the network prefix, and using delete as a synonym for the canonical form of the option -alias: # ifconfig en0 inet6 2001:db8:bdbd::123/48 delete Configure the interface en1, to use 100baseTX, full duplex Ethernet media options: # ifconfig en1 media 100baseTX mediaopt full-duplex Create the software network interface gif1: # ifconfig gif1 create Destroy the software network interface gif1: # ifconfig gif1 destroy Display inet and inet6 address subnet masks in CIDR notation # ifconfig -f inet:cidr,inet6:cidr DIAGNOSTICS Messages indicating the specified interface does not exist, the requested address is unknown, or the user is not privileged and tried to alter an interface's configuration. SEE ALSO netstat(1), netintro(4), sysctl(8) HISTORY The ifconfig utility appeared in 4.2BSD. BUGS Basic IPv6 node operation requires a link-local address on each interface configured for IPv6. Normally, such an address is automatically configured by the kernel on each interface added to the system; this behaviour may be disabled by setting the sysctl MIB variable net.inet6.ip6.auto_linklocal to 0. If you delete such an address using ifconfig, the kernel may act very odd. Do this at your own risk. macOS 14.5 June 20, 2008 macOS 14.5
|
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. When the system is halted with the halt command, the system is powered off. The options are as follows: -l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call halt or reboot and log this themselves. -N The file system cache is not flushed during the initial process clean-up, however the kernel level reboot(2) is still processed with a sync. This option can be useful for performing a “best-effort” reboot when devices might be unavailable. This can happen when devices have been disconnected. -n The file system cache is not flushed. This option should probably not be used. -q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n option is not specified). This option should probably not be used. Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom and cleanly terminating specific programs. SIGTERM TO SIGKILL INTERVAL The SIGKILL will follow the SIGTERM by an intentionally indeterminate period of time. Programs are expected to take only enough time to flush all dirty data and exit. Developers are encouraged to file a bug with the OS vendor, should they encounter an issue with this functionality. SEE ALSO getutxent(3), wtmp(5), shutdown(8), sync(8) HISTORY A reboot utility appeared in 4.0BSD. macOS 14.5 June 6, 2023 macOS 14.5
|
halt, reboot – stopping and restarting the system
|
halt [-lNnq] reboot [-lNnq]
| null | null |
mount_9p
|
The mount_9p command mounts the 9P filesystem associated with fs_tag. The options are as follows: -r Mount filesystem as read-only. DIAGNOSTICS The mount_9p utility exits 0 on success, and >0 if an error occurs. SEE ALSO mount(2), unmount(2), fstab(5), mount(8) Mac OS X April 18, 2019 Mac OS X
|
mount_9p – mount a 9P volume
|
mount_9p [-r] fs_tag
| null | null |
newfs_apfs
|
The newfs_apfs command creates a new APFS container on the device and/or adds a new APFS volume to a container. The first, more traditional, form of newfs_apfs formats the given special as a container with a single volume inside it. The second form creates a container only, with no volumes. The third form is used to non- destructively add additional volumes inside an existing container. The fourth form reformats an existing volume by effectively deleting and re- creating it; in this usage (only) special indicates a volume inside the container. The special parameter should be the path to a disk device node, such as /dev/disk1s2, although can be specified as simply disk1s2. The options are as follows: -b block-size The block size of the container. All volumes within this container will use this block size. The default is 4096 bytes. -o options Additional volume formatting options. Currently only: conformance The volume will be UNIX conformant. -i Creates a case-insensitive volume. This is the default on macOS. -e Creates a case-sensitive volume. -U uid The UID of the root volume. Defaults to current UID. -G uid The GID of the root volume. Defaults to current GID. -q volume-quota Places a quota, or upper limit, on the size of the volume. If specified then no more than this much space will be used for its content, even if there is additional free space in the container; however it is not guaranteed that the entire quota will always be available. By default a volume has no assigned quota. -r volume-reserve Reserves an amount of space for this volume. If specified it is guaranteed that at least this much space will be available for its content; the volume may also grow beyond this size (up to its quota limit, if any) if additional free space in the container. By default a volume has no assigned reserve. -s volume-size The fixed size of the volume. If specified then the volume is guaranteed that exactly this much space will be available for its content. Setting -s is equivalant to setting both -q and -r to that same value. If not specified then the available space is dynamic and determined by the usage of other volumes within the same container (space-sharing). -v volume-name The name of the volume. The default is "untitled". -A Add a volume to an existing container. There is a limit to the number of volumes that may reside inside a container. -C Create a container only, with no volume. newfs_apfs -A may be used later to format volumes inside that container. -E Enable volume encryption. The volume metadata is also encrypted. -D Opt in of UUID from role. The volume UUID will be a based on volume's role, not a random one (the default behavior). -W Empty password flag. Must be placed after -E -S password Key used for volume encryption. If the password option is omitted for an encrypted volume, a prompt will request a password for the new volume. This option is unsecure because other non-privileged users (on multi-user systems) have means to see command-line arguments, including passwords, and is therefore not recommended for use (use the prompt instead). -F special Format as a Fusion device (with the secondary device specified here). -w Wait for the volume to be fully published in I/O Registry before returning. -R role Set the OS "role" of the volume within the container. The role may be one of the following characters: b Preboot - will contain information used to help boot System volumes r Recovery - will contain the RecoveryOS v VM - will contain swapfiles and hibernate image EXIT STATUS The newfs_apfs utility exits 0 on success, and >0 if an error occurs.
|
newfs_apfs – construct a new APFS volume
|
newfs_apfs [-o options] [-i] [-b block-size] [-s volume-size | -q volume-quota -r volume-reserve] [-v volume-name] [-E] [-R role] special newfs_apfs -C [-o options] [-i] [-b block-size] special newfs_apfs -A [-o options] [-i] [-s volume-size | -q volume-quota -r volume-reserve] [-v volume-name] [-E -W (empty password) | -E -S -passphrase] [-R role] special newfs_apfs [-o options] [-i] [-s volume-size | -q volume-quota -r volume-reserve] [-v volume-name] [-E] [-R role] special
| null |
The following formats a new container and a volume named "Macintosh" on the /dev/disk1s2 device: newfs_apfs -v Macintosh disk1s2 And then this adds another volume, named "Data" with a fixed size of 100 GB, to that container: newfs_apfs -v Data -s 100g -A disk1s2 SEE ALSO mount_apfs(8) HISTORY The newfs_apfs utility first appeared in OS X 10.12. Mac OS X September 15, 2015 Mac OS X
|
umount
|
The umount command unmounts a mounted filesystem (volume), removing it from the filesystem namespace. It calls the unmount(2) system call to remove a special device or the remote node (rhost:path) from the filesystem tree at the point node. If either special or node are not provided, the appropriate information is taken from the list of filesystems provided by getfsent(3). The options are as follows: -a All the filesystems described via getfsent(3) are unmounted. -A All the currently mounted filesystems except the root are unmounted. -f The filesystem is forcibly unmounted. Active special devices continue to work, but all other files return errors if further accesses are attempted. The root filesystem cannot be forcibly unmounted. -h host Only filesystems mounted from the specified host will be unmounted. This option implies the -A option and, unless otherwise specified with the -t option, will only unmount NFS filesystems. -t type Is used to indicate the actions should only be taken on filesystems of the specified type. More than one type may be specified in a comma separated list. The list of filesystem types can be prefixed with “no” to specify the filesystem types for which action should not be taken. For example, the umount command: umount -A -t nfs,hfs umounts all currently-mounted filesystems of the type NFS and HFS. (The -a option only unmounts entries in the /etc/fstab list.) -v Verbose, additional information is printed out as each filesystem is unmounted. NOTES Due to the complex and interwoven nature of Mac OS X, umount may fail often. It is recommended that diskutil(1) (as in, ``diskutil unmount /mnt'') be used instead. SEE ALSO unmount(2), getfsent(3), mount(8), diskutil(1) HISTORY A umount command appeared in Version 6 AT&T UNIX. BSD 4 May 8, 1995 BSD 4
|
umount – unmount filesystems
|
umount [-fv] special | node umount -a | -A [-fv] [-h host] [-t type]
| null | null |
fstyp
|
The fstyp utility attempts to determine what sort of volume is present on the given device. It operates by iterating over directories that are typically part of the path, searching for files matching the pattern fstyp_* and running them. If it finds a match, it will print out the file system type name and exit with a return value of 1. If it does not find a match, it will not print out anything, and the return value will be 0. macOS 14.5 August 15, 2005 macOS 14.5
|
fstyp – identify a file system
|
fstyp device
| null | null |
kextunload
|
The kextunload program is used to terminate and unregister I/O Kit objects associated with a kernel extension (kext) and to unload the code and personalities for that kext. kextunload must run with superuser privileges. If another loaded kext has a dependency on the kext being unloaded, the unload will fail. You can determine whether a kext has dependents using the kextstat(8) tool. kextunload is a formal interface for unloading kexts in the Darwin OS and in macOS. Software and installers can rely on its presence and invoke it in order to unload kexts. Note that long options are present as of Mac OS X 10.6 (Snow Leopard). The arguments and options are: kext Unload the loaded kext whose bundle identifier matches the CFBundleIdentifier of kext. All instances of IOService subclasses defined by the loaded kext and in the IOService plane of the I/O Registry are terminated; the kext is checked to make sure no instances of its libkern C++ classes remain; the kext's C++ static destructores and module stop routine are invoked; then the kext's executable and IOKitPersonalities are unloaded from the kernel. Failure at any stage prevents kext unload. -b identifier, -bundle-id identifier Unload executable and IOKitPersonalities (as described immediately above) for the kext whose CFBundleIdentifier is identifier. -c classname, -class classname Terminate all instances of class classname that are in the IOService plane of the I/O Registry, if possible, but do not unload the defining kext or its IOKitPersonalities. New load requests for devices that were driven by these terminated instances may result in the same class being instantiated at any time. -h, -help Print a help message describing each option flag and exit with a success result, regardless of any other options on the command line. -m identifier Same as -b (remains for backward compatibility). -p, -personalities-only Terminate services and remove personalities only; do not unload kexts. -q, -quiet Quiet mode; print no informational or error messages. -v [0-6 | 0x####], -verbose [0-6 | 0x####] Verbose mode; print information about program operation. Higher levels of verbosity include all lower levels. By default kextunload prints only warnings and errors. You can specify a level from 0-6, or a hexadecimal log specification (as described in kext_logging(8)). The levels of verbose output are: 0 Print only errors (that is, suppress warnings); see also -quiet. 1 (or none) Print basic information about program operation. 2 Prints information about unload stages. 3 Prints information about removal of personalities. 4 Prints information about module stop functions and C++ class destruction. 5 Prints detailed information internal operations such as bookkeping. 6 Identical to level 5 for kextunload. Unlike in other kext tools, the -verbose flag in kextunload applies to all kexts (that is, it turns on hexadecimal bit 0x8 by default). See kext_logging(8) for more information on verbose logging. DIAGNOSTICS kextunload exits with a zero status upon success, or prints an error message and exits with a nonzero status upon failure. BUGS Many single-letter options are inconsistent in meaning with (or directly contradictory to) the same letter options in other kext tools. SEE ALSO kmutil(8), kernelmanagerd(8), kextcache(8), kextd(8), kextload(8), kextstat(8), kext_logging(8) Darwin March 6, 2009 Darwin
|
kextunload – terminate driver I/O Kit driver instances and unload kernel extensions (kexts)
|
kextunload [options] [--] [kext ...] DEPRECATED The kextunload utility has been deprecated. Please use the kmutil(8) equivalent: kmutil unload.
| null | null |
mpioutil
|
mpioutil is a utility to manage multiple paths to a SCSI Logical Unit. VERBS, DIRECT OBJECTS, AND SPECIFIC ARGUMENTS list Lists all multipathed logical units. info -i <lun identifier> Get information on a multipathed logical unit. The -i flag may also be expressed as --id. modify lun -i <lun identifier> -a <load balancing algorithm> -b <round robin batch count> Modify a logical unit. The -i, -a, -b flags may also be expressed as --id, --algorithm, and --batchCount respectively. modify path -l <lun identifier> -i <path identifier> -e | -d Modify a path on a logical unit. The -l, -i, -e, and -d flags may also be expressed as --lun, --id, --enable, and --disable respectively.
|
mpioutil – Tool for configuring paths to multipathed logical units.
|
mpioutil verb direct-object arguments
| null |
mpioutil list Lists all multipathed logical units. mpioutil info --id 22F2000155A508ED Get information for a multipathed lun with id 22F2000155A508ED. mpioutil modify lun --id 22F2000155A508ED --algorithm RoundRobin --batchCount 16 Modify a multipathed lun's algorithm to be RoundRobin with a batch count of 16. mpioutil modify lun --id 22F2000155A508ED --algorithm LeastIO Modify a multipathed lun's algorithm to be LeastIO. mpioutil modify path --lun 22F2000155A508ED --id 26010001553560BF00000001 --disable Disable a path that belongs to a multipathed logical unit. Darwin 4/12/10 Darwin
|
fstyp_ntfs
|
The fstyp_ntfs utility is not intended to be run directly, but rather called by fstyp(8) while it is trying to determine which file system type is present on the given device. It returns 1 if it thinks the device contains a Windows NT File System (NTFS) volume, and 0 otherwise. SEE ALSO fstyp(8) macOS 14.5 September 30, 2006 macOS 14.5
|
fstyp_ntfs – check for a Windows NT File System (NTFS) volume
|
fstyp_ntfs device
| null | null |
mount_nfs
|
The mount_nfs command calls the mount(2) system call to prepare and graft a remote NFS file system ( server:/path ) on to the file system tree at the point directory. This command is expected to be executed by the mount(8) command. Direct use of mount_nfs to mount NFS file systems is strongly discouraged because there is little practical benefit of using it instead of mount(8). For NFS versions that use a separate mount protocol, mount_nfs implements the mount protocol as described in RFC 1094, Appendix A and NFS: Network File System Version 3 Protocol Specification, RFC 1813, Appendix I. By default, mount_nfs will attempt the mount twice before exiting with an error. If the -o bg option is given, it will attempt the mount once and then background itself to continue trying another 10,000 times (pausing for one minute between attempts). The option -o retrycnt=⟨num⟩ can be used if a different retry behavior is desired for a mount. If the server becomes unresponsive while an NFS file system is mounted, any new or outstanding file operations on that file system will hang uninterruptibly until the server comes back (or that NFS file system is forcibly unmounted). To modify this default behaviour, see the -o intr and -o soft mount options. Mount options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. The following NFS-specific options are also available: bg Retry mount in background. If an initial attempt to contact the server fails, fork off a child to keep trying the mount in the background. Useful for startup scripts where the file system mount is not critical to multiuser operation. retrycnt=⟨num⟩ Set the retry count for doing the mount to the specified value. The default is 1 for foreground mounts and 10,000 for background mounts. Setting retrycnt to 0, in addition to only trying to establish connection once, will case nfs client code to use quick time out value (default 8s) instead of regular mount time out (default 30s) value while establishing initial connection. udp Use UDP transport protocol. tcp Use the TCP transport protocol instead of UDP. The default is to try TCP first, then fall back to UDP if the server doesn't support TCP. inet Use only IPv4 addresses. inet6 Use only IPv6 addresses. proto=⟨netid⟩ Use the transport protocol and address family as specified by the given ONC RPC Netid (RFC 5665). Valid netid values are: tcp (TCP over IPv4), udp (UDP over IPv4), tcp6 (TCP over IPv6), and udp6 (UDP over IPv6). Note that this option differs from the separate tcp and udp options described above in that each netid value specifies both a transport protocol and address family (IP version). mntudp Force the mount protocol to use UDP transport, even for TCP NFS mounts. (Necessary for some old BSD servers.) mountport=⟨port-number⟩ Connect to the NFS server's mount daemon using the given port number. port=⟨port-number⟩ Connect to an NFS server at the given port number. noconn Do not connect UDP sockets. For UDP mount points, do not do a connect(2). This must be used for servers that do not reply to requests from the standard NFS port number 2049. It may also be required for servers with more than one IP address if replies come from an address other than the one specified in the requests. resvport Use a reserved socket port number. This is useful for mounting servers that require clients to use a reserved port number on the mistaken belief that this makes NFS more secure. (For the rare case where the client has a trusted root account but untrustworthy users and the network cables are in secure areas this does help, but for normal desktop clients this does not apply.) root permission is required to mount using resvport mount option. intr Make the mount interruptible, which implies that file system calls that are delayed due to an unresponsive server will fail with EINTR when a termination signal is posted for the process. soft Make the mount soft, which means that file system calls will fail after retrans round trip timeout intervals. Note: mounts which are both soft and read-only will also have the locallocks mount option enabled by default - unless explicitly overridden with a lock option (for example, nolocks or nolocallocks ). vers=⟨num[.num]⟩[-⟨num[.num]⟩] nfsvers=⟨num[.num]⟩[-⟨num[.num]⟩] NFS protocol version number - 2 for NFSv2, 3 for NFSv3 and 4 for NFSv4. The default is to try version 3 first, and fall back to version 2 if the mount fails. A range of versions can be specified by including a dash and another version with no spaces between versions and the dash. In that case the highest version is tried first and if not successful fall back to each version down to the lowest version specified until the mount succeeds or the lowest version fails. Note minor versions may be specified for versions greater than or equal to four by appending a dot and then the minor version number. Currently NFSv4 is the highest supported version with a minor version of zero. If no minor version is specified, zero is assumed. Specifying a non supported version or minor version will print a warning and ignore the vers or nfsvers option. Versions 2 or 3 do not support minor versioning so minor versions greater than zero are treated as above. nfsv2 nfsv3 nfsv4 Deprecated. Use -o vers=⟨num⟩ to specify NFS protocol version. sec=⟨mechanism⟩ Force a specific security mechanism to be used for the mount, where mechanism is one of: krb5p, krb5i, krb5, or sys. When this option is not given the security mechanism will be negotiated transparently with the remote server. etype=⟨encryption-type⟩ Use the specified encryption type for the mount, where encryption-type is one of: des3, des3-cbc-sha1, des3-cbc-sha1-kd, aes128, aes128-cts-hmac-sha1, aes128-cts-hmac-sha1-96, aes256-cts-hmac-sha1, or aes256-cts-hmac-sha1-96. realm=⟨realm⟩ Use the default credential for realm or security domain. For Kerberos realms are usually uppercase. If the realm specified does not begin with an “@”, an “@” sign will be prepended to it. Note specifying the realm is typically used for automounter maps when clients may have multiple credential caches, and tells the client what cache to use on the mount. principal=⟨principal⟩ Use the specified principal for acquiring credentials for the mount. That principal will be used for all accesses by the mounting credential on the mounted file system. Note specifying a principal is useful for user initiated command line mounts, where the user knows the particular credential to use. sprincipal=⟨server-principal⟩ Use the specified server-principal for establishing credentials for the mount. That server principal will be use for all mount access. If no server principal is specified, then the GSS_C_NT_HOSTBASED_SERVICE nfs@server is used, where server is taken from the mount argument server:/path. Note its rare to use this option. rsize=⟨readsize⟩ Set the read data size to the specified value. The default is 8192 for UDP mounts and 32768 for TCP mounts. It should normally be a power of 2 greater than or equal to 1024. Values greater than 4096 should be multiples of 4096. It may need to be lowered for UDP mounts when the “fragments dropped due to timeout” value is getting large while actively using a mount point. (Use netstat(1) with the -s option to see what the “fragments dropped due to timeout” value is.) wsize=⟨writesize⟩ Set the write data size to the specified value. Ditto the comments w.r.t. the rsize option, but using the “fragments dropped due to timeout” value on the server instead of the client. Note that both the rsize and wsize options should only be used as a last ditch effort at improving performance when mounting servers that do not support TCP mounts. rwsize=⟨size⟩ Set both the read data size and write data size to the specified value. dsize=⟨readdirsize⟩ Set the directory read size to the specified value. The value should normally be a multiple of DIRBLKSIZ that is <= the read size for the mount. The default is 8192 for UDP mounts and 32768 for TCP mounts. readahead=⟨maxreadahead⟩ Set the maximum read-ahead count to the specified value. The default is 16. This may be in the range of 0 - 128, and determines how many Read RPCs will be read ahead when a large file is being read sequentially. Trying larger values for this is suggested for mounts with a large bandwidth * delay product. rdirplus / nordirplus Used with NFS v3/v4 to specify that directory read operations should retrieve additional information about each entry (e.g. use the NFSv3 ReaddirPlus RPC). This option typically reduces RPC traffic for cases such as directory listings that use or display basic attributes (e.g. “ls -F” and “find . -type f” ). Note that the long directory listing format case (i.e. “ls -l” ) may not be helped much when the file system does not natively support extended attributes. Older implementations tended to flood the vnode and name caches with prefetched entries which may not be referenced. The current implementation avoids creating those entries until they are referenced. Try this option and see whether performance improves or degrades. Probably most useful for client to server network interconnects with a large bandwidth times delay product. Default value is rdirplus. acregmin=⟨seconds⟩ acregmax=⟨seconds⟩ acdirmin=⟨seconds⟩ acdirmax=⟨seconds⟩ acrootdirmin=⟨seconds⟩ acrootdirmax=⟨seconds⟩ These options set the minimum and maximum attribute cache timeouts for directories, the root directory and "regular" (non- directory) files. The default minimum is 5 seconds and the default maximum is 60 seconds. If not specified, the values of acrootdirmin and acrootdirmax will be assigned to those of acdirmin and acdirmax respectively, to maintain backward compatibility. Setting all the minimum and maximum to zero will disable attribute caching. The algorithm to calculate the timeout is based on the age of the file or directory. The older it is, the longer the attribute cache is considered valid, subject to the limits above. Note that the effectiveness of this algorithm depends on how well the clocks on the client and server are synchronized. actimeo=⟨seconds⟩ Set all attribute cache timeouts to the same value. noac Disable attribute caching. Equivalent to setting actimeo to 0. nonegnamecache Disable negative name caching. locallocks For NFSv2/v3 mounts, perform all file locking operations locally on the NFS client (in the VFS layer) instead of on the NFS server. This option can provide file locking support on an NFS file system for which the server does not support file locking. However, because the file locking is only performed on the client, the NFS server and other NFS clients will have no knowledge of the locks. Note: mounts which are both soft and read-only will also have the locallocks mount option enabled by default - unless explicitly overridden with a lock option (for example, nolocks or nolocallocks ). nolocks nolockd nolock nonlm For NFSv2/v3 mounts, do not support NFS file locking operations. Any attempt to perform file locking operations on this mount will return the error ENOTSUP regardless of whether or not the NFS server supports NFS file locking. noquota Do not support file system quota operations that would normally be serviced by using the RQUOTA protocol. Any attempt to perform quota operations on this mount will return the error ENOTSUP regardless of whether or not the NFS server supports the RQUOTA service. maxgroups=⟨num⟩ Set the maximum size of the group list for the credentials to the specified value. This should be used for mounts on old servers that cannot handle a group list size of 16, as specified in RFC 1057. Try 8, if users in a lot of groups cannot get a response from the mount point. dumbtimer Turn off the dynamic retransmit timeout estimator. This may be useful for UDP mounts that exhibit high retry rates, since it is possible that the dynamically estimated timeout interval is too short. timeo=⟨timeout⟩ Set the initial retransmit timeout to the specified value (in tenths of a second). The default is 1 second. May be useful for fine tuning UDP mounts over internetworks with high packet loss rates or an overloaded server. Try increasing the interval if nfsstat(1) shows high retransmit rates while the file system is active or reducing the value if there is a low retransmit rate but long response delay observed. (Normally, the dumbtimer option should be specified when using this option to manually tune the timeout interval.) retrans=⟨count⟩ Set the retransmit timeout count for soft mounts to the specified value. The default value is 10. deadtimeout=⟨timeout⟩ If the mount is still unresponsive timeout seconds after it is initially reported unresponsive, then mark the mount as dead so that it will be forcibly unmounted. Note: mounts which are both soft and read-only will also have the deadtimeout mount option set to 60 seconds. This can be explicitly overridden by setting deadtimeout=0. mutejukebox When NFS requests repeatedly get jukebox errors (NFS3ERR_JUKEBOX, NFS4ERR_DELAY) from the server the NFS file system is reported as being unresponsive. Use of this option will prevent the file system from being included in the list of unresponsive file systems that would be included in a dialog presented to the user. This option may be useful when a file system is expected to get such errors during normal operation. For example, when it's backed by a hierarchical storage management system. async Assume that unstable write requests have actually been committed to stable storage on the server, and thus will not require resending in the event that the server crashes. Use of this option may improve performance but only at the risk of data loss if the server crashes. Note: this mount option will only be honored if the nfs.client.allow_async option in nfs.conf(5) is also enabled. sync Perform I/O requests (specifically, write requests) synchronously. The operation will not return until a response is received from the server. (The default, nosync, behavior is to return once the I/O has been queued up.) nocallback For NFSv4 mounts, don't support callback requests from the server. This should effectively disable features that require callback requests such as delegations. nonamedattr For NFSv4 mounts, don't support named attributes even if the server does. This is the default. namedattr For NFSv4 mounts, if the server appears to support named attributes, they will be used to store extended attributes and named streams (e.g. FinderInfo and resource forks). noacl For NFSv4 mounts, don't support ACLs even if the server does. ACLs are currently disabled by default to avoid issues with the way ACLs and modes are handled differently on other operating systems. This may be overriden by specifying the acl option. aclonly For NFSv4 mounts, only support ACLs; do not support the mode attribute. (Any mode attribute values returned will have all permission bits set - regardless of the value of any ACL or access mode stored in the file system.) This option overrides the noacl option. nfc Convert name strings to Unicode Normalization Form C (NFC) when sending them to the NFS server. This option may be used to improve interoperability with NFS clients and servers that typically use names in the NFC form. nfs.conf(5) can be used to configure some NFS client options. In particular, nfs.client.mount.options can be used to specify default mount options. This can be useful in situations where it is not easy to configure the command-line options. Some NFS client options in nfs.conf(5) correspond to kernel configuration values which will get set by mount_nfs when performing a mount. To update these values without performing a mount, use the command: mount_nfs configupdate. COMPATIBILITY The following mount_nfs command line flags have equivalent -o option forms (shown in parentheses) and their use is strongly discouraged. These command line flags are deprecated and the -o option forms should be used instead. -2 (vers=2), -3 (vers=3), -4 (vers=4), -L (nolocks), -P (resvport), -T (tcp), -U (mntudp), -b (bg), -c (noconn), -d (dumbtimer), -i (intr), -l (rdirplus), -m (nordirplus), -s (soft), -I readdirsize (dsize=#), -R retrycnt (retrycnt=#), -a maxreadahead (readahead=#), -g maxgroups (maxgroups=#), -r readsize (rsize=#), -t timeout (timeo=#), -w writesize (wsize=#), -x retrans (retrans=#).
|
mount_nfs – mount NFS file systems
|
mount_nfs [-o options] server:/path directory
| null |
The simplest way to invoke mount_nfs is with a command like: mount remotehost:/filesystem /localmountpoint or: mount -t nfs remotehost:/filesystem /localmountpoint PERFORMANCE As can be derived from the comments accompanying the options, performance tuning of NFS can be a non-trivial task. Here are some common points to watch: • Use of the sync option will probably have a detrimental affect on performance. Its use is discouraged as it provides little benefit. • Use of the async option may improve performance, but only at the risk of losing data if the server crashes because the client will not be making sure that all data is committed to stable storage on the server. • Increasing the read and write size with the rsize and wsize options respectively will increase throughput if the network interface can handle the larger packet sizes. The default read and write sizes are 8K when using UDP, and 32K when using TCP. Values over 16K are only supported for TCP, where 2M is the maximum. Any value over 32K is unlikely to get you more performance, unless you have a very fast network. • If the network interface cannot handle larger packet sizes or a long train of back to back packets, you may see low performance figures or even temporary hangups during NFS activity. This can especially happen with lossy network connections (e.g. wireless networks) which can lead to a lot of dropped packets. In this case, decreasing the read and write size, using TCP, or a combination of both will usually lead to better throughput. • For connections that are not on the same LAN, and/or may experience packet loss, using TCP is strongly recommended. ERRORS Some common problems with mount_nfs can be difficult for first time users to understand. mount_nfs: can't access /foo: Permission denied This message means that the remote host is either not exporting the file system you requested or is not exporting it to your host. If you believe the remote host is indeed exporting a file system to you, make sure the exports(5) file is exporting the proper directories. The program showmount(8) can be used to see a server's exports list. The command “showmount -e remotehostname” will display what file systems the remote host is exporting. A common mistake is that mountd(8) will not export a file system with the -alldirs option, unless it is a mount point on the exporting host. It is not possible to remotely mount a subdirectory of an exported mount, unless it is exported with the -alldirs option. The following error: NFS Portmap: RPC: Program not registered means that the remote host is not running nfsd(8). or mountd(8). The program rpcinfo(8) can be used to determine if the remote host is running nfsd and mountd by issuing the command: rpcinfo -p remotehostname If the remote host is running nfsd, mountd, rpc.statd, and rpc.lockd it would display: program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100005 1 udp 950 mountd 100005 3 udp 950 mountd 100005 1 tcp 884 mountd 100005 3 tcp 884 mountd 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100024 1 udp 644 status 100024 1 tcp 918 status 100021 0 udp 630 nlockmgr 100021 1 udp 630 nlockmgr 100021 3 udp 630 nlockmgr 100021 4 udp 630 nlockmgr 100021 0 tcp 917 nlockmgr 100021 1 tcp 917 nlockmgr 100021 3 tcp 917 nlockmgr 100021 4 tcp 917 nlockmgr The following error: mount_nfs: can't resolve host indicates that mount_nfs could not resolve the name of the remote host. The following error: mount_nfs: can't mount <dst-path> from <dst-ip> onto <local-path>: RPC prog. not avail In case the remote host is not running rpc.statd and the client is mounting the NFS directory with remote locks (enabled by default), mount_nfs should fail with EPROGUNAVAIL. rpc.statd status can be verified using rpcinfo (see above). The following warning: mount_nfs: wsize/rsize ratio is high: this could end up with unexpected readahead RPCs indicates that provided wsize is much greater than rsize. which could end up with a different amount of readahead RPCs compared to the amount requested by the user. SEE ALSO mount(2), unmount(2), mount(8), umount(8), nfsstat(1), netstat(1), rpcinfo(8), showmount(8), automount(8), nfs.conf(5), nfs(5) CAVEATS An NFS server shouldn't loopback-mount its own exported file systems because it's fundamentally prone to deadlock. macOS 14.5 February 28, 2010 macOS 14.5
|
newfs_udf
|
The newfs_udf command builds the UDF filesystem on the specified special device. The options are as follows: General options: -N Causes the file system parameters to be printed out without really creating the file system. -w Stop processing on warnings, default: no --wipefs yes|no Whether wipe existing file systems on the volume before formatting it. Default: wipe existing file systems when media- type is block device (blk), access-type is overwrite (ow), and the Keep Disc Open option (-o) is not specified; do not wipe existing file systems by default in all other cases. --largesparse Format the volume to use a non UDF-compliant format to efficiently support very large sparse files (up to 2^63 - 1, or 9,223,372,036,854,775,807 bytes). Sparse files on this volume that has holes larger than 1GB cannot be accessed by other UDF implementations. Disc properties: -b block-size The block size of the file system, in bytes, default: the native block size of the device, or 2048 for an image file -d The file system manages defects by creating a sparable partition, default: no -e Use extended file entry instead of file entry, default: no -E ecc-in-blks ECC block size in number of blocks -m media-type The type of the media, can be blk (block device), var-packet (varible size packet writing), fix-packet (fixed size packet writing), or pow (pseudo overwrite), default: blk -t access-type The access type of the partition, can be wo (writeonce), ow (overwrite), or pow (pseudo overwrite), default: ow -o Keep the disc as open by only writing the first AVDP (e.g., background formating haven't finish, so the write of the last two AVDPs is not possible), default: close the disc for overwrite media, and keep it open for write once media -p packet-size The size of a packet in number of blocks, default: 1 -s size Size of the file system in blocks, default: size of the device UDF parameters: General: -r rev UDF version number, can be 1.02, 1.50, 2.00, 2.01, 2.50, or 2.60, default: 2.01 -u Creates unique id table (or unique id stream), default: no --unalloc-spc blk-addr num-blks Unallocated space recorded in unallocated space descriptor, default: no unallocated spc -v vol-name Volume identifier, max 127 ascii or 63 unicode chars, default: "Untitled UDF Volume" --enc encoding-name The character encoding of the volume name, can be "utf8" or "utf16", default: utf8 Virtual partitions (for CD-R, DVD-R SL/DL, DVD+R SL/DL, and HD DVD-R SL/DL): -S start-block-address The start block address of the last session. Newfs_udf will search for this value for optical media Sparable partitions (for CD-RW, DVD-RW, and DVD+RW): --spare-blks n Total number of sparing blocks (2 sparing tables are always used), default: 128 -D defect-file-name The name of the file containing all defect blocks. This file is a text file, contains the physical block address of the media that has defects. When one block of a packet is defective, the whole packet is marked as defective. The block numbers in the file is delimited by space. Multiple numbers can be on the same line. Metadata partitions (for BD-R with POW, BD-RE and other overwritable media with UDF 2.50 or higher ): --dup-meta-part-file Duplicate the content of the metadata file in the metadata mirror file, default: no --meta-part-alloc-unit n The allocation unit size of the metadata partition in number of blocks, default: max(32, eccSizeInBlks, packetSize) --meta-part-align-unit n The alignment unit size of the metadata partition in number of blocks, default: max(eccSizeInBlks, packetSize) --meta-part-init-size n The initial size of the metadata partition in number of blocks, default: 32 --userid uid or -U uid Use the specified uid (numeric value only) as the owner of the root directory. --groupid gid or -G gid Use the specified gid (numeric value only) as the group of the root directory. SEE ALSO newfs(8) BUGS Unallocated space is not supported yet. HISTORY The newfs_udf utility first appeared in Mac OS X Leopard (10.5.0). Mac OS X July 12, 2005 Mac OS X
|
newfs_udf – construct a new UDF file system.
|
newfs_udf [-Ndeouw] [-b block-size] [-D defect-file-name] [--dup-meta-part-file] [-E ecc-in-blks] [--enc encoding-name] [-v vol-name] [-m media-type] [--meta-part-alloc-unit n] [--meta-part-align-unit n] [--meta-part-init-size n] [-p packet-size] [-r rev] [-s size] [-S start-block-address] [--spare-blks n] [-t access-type] [--unalloc-spc blk-addr num-blks] [--wipefs yes|no] [--userid uid] [-U uid] [--groupid gid] [-G gid] special
| null | null |
mount_ftp
|
The mount_ftp command mounts a FTP-enabled server directory at ftp://host[:port][/path] at the mount point indicated by node. If the -i option is not used, all the required information to establish a login to the remote server must be available in the ftp URL, including username & password if needed. The user ID for all files and folders is set to the user's real user ID. The group ID for all files and directories is set to unknown, and the permissions default to read and execute for user, group and other. The options are: -i Interactive mode, you are prompted for the username and password if you did not supply one in the url. -o Options passed to mount(2) are specified with the -o option followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. The rdonly option will be set even if it was not specified because mount_ftp does not allow files to be opened with write access on servers. ftp://host[:port][/path] The FTP-enabled server directory to mount as a volume. If port is not specified, then port 21 is used. If path is not specified, then the path "/" is used. node Path to mount point.
|
mount_ftp – mount a FTP filesystem
|
mount_ftp [-i] [-o options] ftp://host[:port][/path] node
| null |
The following example illustrates how to mount the FTP-enabled server directory ftp.apple.com/ at the mount point /Volumes/mntpnt/ mount_ftp ftp://ftp.apple.com/ /Volumes/mntpnt/ SEE ALSO mount(2), unmount(2), mount(8) HISTORY The mount_ftp command first appeared Mac OS X Version 10.2. RETURN VALUES 0 mount_ftp successfully mounted the server directory. [ENOENT] The server directory could not be mounted by mount_ftp because the node path is invalid. [ENODEV] The server directory could not be mounted by mount_ftp because it is not FTP-enabled or because it does not exist, or because node does not have proper access. [ECANCELED] The server directory could not be mounted by mount_ftp because the user did not provide proper authentication credentials. BUGS mount_ftp only supports mounting read-only. Mac OS X June 6, 2003 Mac OS X
|
pfctl
|
The pfctl utility communicates with the packet filter device. It allows ruleset and parameter configuration and retrieval of status information from the packet filter. Packet filtering restricts the types of packets that pass through network interfaces entering or leaving the host based on filter rules as described in pf.conf(5). The packet filter can also replace addresses and ports of packets. Replacing source addresses and ports of outgoing packets is called NAT (Network Address Translation) and is used to connect an internal network (usually reserved address space) to an external one (the Internet) by making all connections to external hosts appear to come from the gateway. Replacing destination addresses and ports of incoming packets is used to redirect connections to different hosts and/or ports. A combination of both translations, bidirectional NAT, is also supported. Translation rules are described in pf.conf(5). The packet filter does not itself forward packets between interfaces. Forwarding can be enabled by setting the sysctl(8) variables net.inet.ip.forwarding and/or net.inet6.ip6.forwarding to 1. Set them permanently in sysctl.conf(5). The pfctl utility provides several commands. The options are as follows: -A Load only the queue rules present in the rule file. Other rules and options are ignored. -a anchor Apply flags -f, -F, and -s only to the rules in the specified anchor. In addition to the main ruleset, pfctl can load and manipulate additional rulesets by name, called anchors. The main ruleset is the default anchor. Anchors are referenced by name and may be nested, with the various components of the anchor path separated by ‘/’ characters, similar to how file system hierarchies are laid out. The last component of the anchor path is where ruleset operations are performed. Evaluation of anchor rules from the main ruleset is described in pf.conf(5). Private tables can also be put inside anchors, either by having table statements in the pf.conf(5) file that is loaded in the anchor, or by using regular table commands, as in: # pfctl -a foo/bar -t mytable -T add 1.2.3.4 5.6.7.8 When a rule referring to a table is loaded in an anchor, the rule will use the private table if one is defined, and then fall back to the table defined in the main ruleset, if there is one. This is similar to C rules for variable scope. It is possible to create distinct tables with the same name in the global ruleset and in an anchor, but this is often bad design and a warning will be issued in that case. By default, recursive inline printing of anchors applies only to unnamed anchors specified inline in the ruleset. If the anchor name is terminated with a ‘*’ character, the -s flag will recursively print all anchors in a brace delimited block. For example the following will print the “authpf” ruleset recursively: # pfctl -a 'authpf/*' -sr To print the main ruleset recursively, specify only ‘*’ as the anchor name: # pfctl -a '*' -sr -D macro=value Define macro to be set to value on the command line. Overrides the definition of macro in the ruleset. -d Disable the packet filter. -X token Release the pf enable reference represented by the token passed. -e Enable the packet filter. -E Enable the packet filter and increment the pf enable reference count. -F modifier Flush the filter parameters specified by modifier (may be abbreviated): -F nat Flush the NAT rules. -F queue Flush the queue rules. -F rules Flush the filter rules. -F states Flush the state table (NAT and filter). -F Sources Flush the source tracking table. -F info Flush the filter information (statistics that are not bound to rules). -F Tables Flush the tables. -F osfp Flush the passive operating system fingerprints. -F all Flush all of the above. -f file Load the rules contained in file. This file may contain macros, tables, options, and normalization, queueing, translation, and filtering rules. With the exception of macros and tables, the statements must appear in that order. Use of this option, could result in flushing of rules present in the main ruleset added by the system at startup. See /etc/pf.conf for further details. -g Include output helpful for debugging. -h Help. -i interface Restrict the operation to the given interface. -K host | network Kill all of the source tracking entries originating from the specified host or network. A second -K host or -K network option may be specified, which will kill all the source tracking entries from the first host/network to the second. -k host | network Kill all of the state entries originating from the specified host or network. A second -k host or -k network option may be specified, which will kill all the state entries from the first host/network to the second. For example, to kill all of the state entries originating from “host”: # pfctl -k host To kill all of the state entries from “host1” to “host2”: # pfctl -k host1 -k host2 To kill all states originating from 192.168.1.0/24 to 172.16.0.0/16: # pfctl -k 192.168.1.0/24 -k 172.16.0.0/16 A network prefix length of 0 can be used as a wildcard. To kill all states with the target “host2”: # pfctl -k 0.0.0.0/0 -k host2 -m Merge in explicitly given options without resetting those which are omitted. Allows single options to be modified without disturbing the others: # echo "set loginterface fxp0" | pfctl -mf - -M Enable port to name translation while displaying rule. -N Load only the NAT rules present in the rule file. Other rules and options are ignored. -n Do not actually load rules, just parse them. -O Load only the options present in the rule file. Other rules and options are ignored. -o level Control the ruleset optimizer, overriding any rule file settings. -o none Disable the ruleset optimizer. -o basic Enable basic ruleset optimizations. This is the default behaviour. -o profile Enable basic ruleset optimizations with profiling. For further information on the ruleset optimizer, see pf.conf(5). -p device Use the device file device instead of the default /dev/pf. -q Only print errors and warnings. -R Load only the filter rules present in the rule file. Other rules and options are ignored. -r Perform reverse DNS lookups on states when displaying them. -s modifier Show the filter parameters specified by modifier (may be abbreviated): -s nat Show the currently loaded NAT rules. -s queue Show the currently loaded queue rules. When used together with -v, per-queue statistics are also shown. When used together with -v -v, pfctl will loop and show updated queue statistics every five seconds, including measured bandwidth and packets per second. -s rules Show the currently loaded filter rules. When used together with -v, the per-rule statistics (number of evaluations, packets and bytes) are also shown. Note that the “skip step” optimization done automatically by the kernel will skip evaluation of rules where possible. Packets passed statefully are counted in the rule that created the state (even though the rule isn't evaluated more than once for the entire connection). -s Anchors Show the currently loaded anchors directly attached to the main ruleset. If -a anchor is specified as well, the anchors loaded directly below the given anchor are shown instead. If -v is specified, all anchors attached under the target anchor will be displayed recursively. -s states Show the contents of the state table. -s Sources Show the contents of the source tracking table. -s info Show filter information (statistics and counters). When used together with -v, source tracking statistics are also shown. -s References Show pf-enable reference statistics (pid/name of enabler, token, timestamp). -s labels Show per-rule statistics (label, evaluations, packets total, bytes total, packets in, bytes in, packets out, bytes out) of filter rules with labels, useful for accounting. -s timeouts Show the current global timeouts. -s memory Show the current pool memory hard limits. -s Tables Show the list of tables. -s osfp Show the list of operating system fingerprints. -s Interfaces Show the list of interfaces and interface drivers available to PF. When used together with -v, it additionally lists which interfaces have skip rules activated. When used together with -vv, interface statistics are also shown. -i can be used to select an interface or a group of interfaces. -s all Show all of the above, except for the lists of interfaces and operating system fingerprints. -T command [address ...] Specify the command (may be abbreviated) to apply to the table. Commands include: -T kill Kill a table. -T flush Flush all addresses of a table. -T add Add one or more addresses in a table. Automatically create a nonexisting table. -T delete Delete one or more addresses from a table. -T expire number Delete addresses which had their statistics cleared more than number seconds ago. For entries which have never had their statistics cleared, number refers to the time they were added to the table. -T replace Replace the addresses of the table. Automatically create a nonexisting table. -T show Show the content (addresses) of a table. -T test Test if the given addresses match a table. -T zero Clear all the statistics of a table. -T load Load only the table definitions from pf.conf(5). This is used in conjunction with the -f flag, as in: # pfctl -Tl -f pf.conf For the add, delete, replace, and test commands, the list of addresses can be specified either directly on the command line and/or in an unformatted text file, using the -f flag. Comments starting with a ‘#’ are allowed in the text file. With these commands, the -v flag can also be used once or twice, in which case pfctl will print the detailed result of the operation for each individual address, prefixed by one of the following letters: A The address/network has been added. C The address/network has been changed (negated). D The address/network has been deleted. M The address matches (test operation only). X The address/network is duplicated and therefore ignored. Y The address/network cannot be added/deleted due to conflicting ‘!’ attributes. Z The address/network has been cleared (statistics). Each table maintains a set of counters that can be retrieved using the -v flag of pfctl. For example, the following commands define a wide open firewall which will keep track of packets going to or coming from the OpenBSD FTP server. The following commands configure the firewall and send 10 pings to the FTP server: # printf "table <test> { ftp.openbsd.org }\n \ pass out to <test>\n" | pfctl -f- # ping -qc10 ftp.openbsd.org We can now use the table show command to output, for each address and packet direction, the number of packets and bytes that are being passed or blocked by rules referencing the table. The time at which the current accounting started is also shown with the “Cleared” line. # pfctl -t test -vTshow 129.128.5.191 Cleared: Thu Feb 13 18:55:18 2003 In/Block: [ Packets: 0 Bytes: 0 ] In/Pass: [ Packets: 10 Bytes: 840 ] Out/Block: [ Packets: 0 Bytes: 0 ] Out/Pass: [ Packets: 10 Bytes: 840 ] Similarly, it is possible to view global information about the tables by using the -v modifier twice and the -s Tables command. This will display the number of addresses on each table, the number of rules which reference the table, and the global packet statistics for the whole table: # pfctl -vvsTables --a-r- test Addresses: 1 Cleared: Thu Feb 13 18:55:18 2003 References: [ Anchors: 0 Rules: 1 ] Evaluations: [ NoMatch: 3496 Match: 1 ] In/Block: [ Packets: 0 Bytes: 0 ] In/Pass: [ Packets: 10 Bytes: 840 ] In/XPass: [ Packets: 0 Bytes: 0 ] Out/Block: [ Packets: 0 Bytes: 0 ] Out/Pass: [ Packets: 10 Bytes: 840 ] Out/XPass: [ Packets: 0 Bytes: 0 ] As we can see here, only one packet - the initial ping request - matched the table, but all packets passing as the result of the state are correctly accounted for. Reloading the table(s) or ruleset will not affect packet accounting in any way. The two “XPass” counters are incremented instead of the “Pass” counters when a “stateful” packet is passed but doesn't match the table anymore. This will happen in our example if someone flushes the table while the ping(8) command is running. When used with a single -v, pfctl will only display the first line containing the table flags and name. The flags are defined as follows: c For constant tables, which cannot be altered outside pf.conf(5). p For persistent tables, which don't get automatically killed when no rules refer to them. a For tables which are part of the active tableset. Tables without this flag do not really exist, cannot contain addresses, and are only listed if the -g flag is given. i For tables which are part of the inactive tableset. This flag can only be witnessed briefly during the loading of pf.conf(5). r For tables which are referenced (used) by rules. h This flag is set when a table in the main ruleset is hidden by one or more tables of the same name from anchors attached below it. -t table Specify the name of the table. -v Produce more verbose output. A second use of -v will produce even more verbose output including ruleset warnings. See the previous section for its effect on table commands. A third use of -v will produce additional queue statistics related information. -w wait Show queue statistics at intervals of wait seconds. -x level Set the debug level (may be abbreviated) to one of the following: -x none Don't generate debug messages. -x urgent Generate debug messages only for serious errors. -x misc Generate debug messages for various errors. -x loud Generate debug messages for common conditions. -z Clear per-rule statistics. FILES /etc/pf.conf Packet filter rules file. /etc/pf.os Passive operating system fingerprint database. SEE ALSO pf.conf(5), pf.os(5), sysctl.conf(5), ftp-proxy(8), sysctl(8) HISTORY The pfctl program and the packet filter mechanism first appeared in OpenBSD 3.0. macOS 14.5 July 1, 2007 macOS 14.5
|
pfctl – control the packet filter (PF) and network address translation (NAT) device
|
pfctl [-AdeghmNnOqRrvz] [-a anchor] [-D macro= value] [-F modifier] [-f file] [-i interface] [-K host | network] [-k host | network] [-o level] [-p device] [-s modifier] [-t table -T command [address ...]] [-x level]
| null | null |
mknod
|
The mknod command creates device special files, or fifos. To make nodes manually, the arguments are: -r Replace an existing file if its type is incorrect. -R Replace an existing file if its type is incorrect. Correct the mode, user and group. -F fmt Create device nodes that may be used by an operating system which uses device numbers packed in a different format than NetBSD uses. This is necessary when NetBSD is used as an NFS server for netbooted computers running other operating systems. The following values for the fmt are recognized: native, 386bsd, 4bsd, bsdos, freebsd, hpux, isc, linux, netbsd, osf1, sco, solaris, sunos, svr3, svr4, and ultrix. -g gid Specify the group for the device node. The gid operand may be a numeric group ID or a group name. If a group name is also a numeric group ID, the operand is used as a group name. Precede a numeric group ID with a # to stop it being treated as a name. -m mode Specify the mode for the device node. The mode may be absolute or symbolic, see chmod(1). name Device name, for example “sd” for a SCSI disk on an HP300 or a “pty” for pseudo-devices. b | c | p Type of device. If the device is a block type device such as a tape or disk drive which needs both cooked and raw special files, the type is b. All other devices are character type devices, such as terminal and pseudo devices, and are type c. Specifying p creates fifo files. driver | major The major device number is an integer number which tells the kernel which device driver entry point to use. If the device driver is configured into the current kernel it may be specified by driver name or major number. (e.g. /usr/src/sys/arch/vax/vax/conf.c). minor The minor device number tells the kernel which one of several similar devices the node corresponds to; for example, it may be a specific serial port or pty. unit and subunit The unit and subunit numbers select a subset of a device; for example, the unit may specify a particular SCSI disk, and the subunit a partition on that disk. (Currently this form of specification is only supported by the bsdos format, for compatibility with the BSD/OS mknod). number A single opaque device number. Useful for netbooted computers which require device numbers packed in a format that isn't supported by -F. -l List the device drivers configured into the current kernel together with their block and character major numbers. SEE ALSO chmod(1), mkfifo(1), mkfifo(2), mknod(2) HISTORY A mknod command appeared in Version 4 AT&T UNIX. The -F option appeared in NetBSD 1.4. The -g, -l, -m, -r, -R, and -u options, and the ability to specify a driver by name appeared in NetBSD 2.0. macOS 14.5 September 12, 2016 macOS 14.5
|
mknod – make device special file
|
mknod [-rR] [-F fmt] [-g gid] [-m mode] name [c | b] [driver | major] minor mknod [-rR] [-F fmt] [-g gid] [-m mode] name [c | b] major unit subunit mknod [-rR] [-g gid] [-m mode] name [c | b] number mknod [-rR] [-g gid] [-m mode] name p mknod -l
| null | null |
fstyp_udf
|
The fstyp_udf utility is not intended to be run directly, but rather called by fstyp(8) while it is trying to determine which file system type is present on the given device. It returns 1 if it thinks the device contains a UDF volume, and 0 otherwise. SEE ALSO fstyp(8) macOS 14.5 August 15, 2005 macOS 14.5
|
fstyp_udf – check for a UDF volume
|
fstyp_udf device
| null | null |
dmesg
|
Dmesg displays the contents of the system message buffer. This command needs to be run as root. SEE ALSO syslogd(8) HISTORY The dmesg command appeared in 4.0BSD. BSD 4 June 5, 1993 BSD 4
|
dmesg – display the system message buffer
|
dmesg [-M core] [-N system]
| null | null |
mount
|
The mount command calls the mount(2) system call to prepare and graft a special device or the remote node (rhost:path) on to the file system tree at the point mount_point, which must be a directory. If either special or mount_point are not provided, the appropriate information is obtained via the getfsent(3) library routines. The system maintains a list of currently mounted file systems. If no arguments are given to mount, this list is printed. The options are as follows: -a All the filesystems listed via getfsent(3) are mounted. Exceptions are those marked as ``noauto;'' excluded by the -t flag (see below); entries that are neither ``ro,'' ``rw,'' or ``rq;'' ``nfs'' entries that also have ``net'' as an option; and already-mounted ``nfs'' entries. -d Causes everything to be done except for the actual system call. This option is useful in conjunction with the -v flag to determine what the mount command is trying to do. -f Forces the revocation of write access when trying to downgrade a filesystem mount status from read-write to read-only. -k In the course of the mount system call, the kernel should not follow any symlinks that may be present in the provided mount-on directory. -o Options are specified with a -o flag followed by a comma separated string of options. The following options are available: async All I/O to the file system should be done asynchronously. This can be somewhat dangerous with respect to losing data when faced with system crashes and power outages. This is also the default. It can be avoided with the noasync option. force The same as -f; forces the revocation of write access when trying to downgrade a filesystem mount status from read-write to read-only. noasync This filesystem should not force all I/O to be written asynchronously. noauto This filesystem should be skipped when mount is run with the -a flag. nodev Do not interpret character or block special devices on the file system. This option is useful for a server that has file systems containing special devices for architectures other than its own. noexec Do not allow execution of any binaries on the mounted file system. This option is useful for a server that has file systems containing binaries for architectures other than its own. noowners Ignore the ownership field for the entire volume. This causes all objects to appear as owned by user ID 99 and group ID 99. User ID 99 is interpreted as the current effective user ID, while group ID 99 is used directly and translates to ``unknown''. nosuid Do not allow set-user-identifier or set-group-identifier bits to take effect. rdonly The same as -r; mount the file system read-only (even the super-user may not write it). sync All I/O to the file system should be done synchronously. update The same as -u; indicate that the status of an already mounted file system should be changed. union Causes the namespace to appear as the union of directories of the mounted filesystem with corresponding directories in the underlying filesystem. Lookups will be done in the mounted filesystem first. If those operations fail due to a non-existent file the underlying directory is then accessed. noatime Do not update the file access time when reading from a file. This option is useful on file systems where there are large numbers of files and performance is more critical than updating the file access time (which is rarely ever important). strictatime Always update the file access time when reading from a file. Without this option the filesystem may default to a less strict update mode, where some access time updates are skipped for performance reasons. This option could be ignored if it is not supported by the filesystem. nobrowse This option indicates that the mount point should not be visible via the GUI (i.e., appear on the Desktop as a separate volume). nofollow This option indicates that in the course of the mount system call, the kernel should not follow any symlinks that may be present in the provided mount-on directory. This is the same as the -k option. Any additional options specific to a filesystem type that is not one of the internally known types (see the -t option) may be passed as a comma separated list; these options are distinguished by a leading “-” (dash). Options that take a value are specified using the syntax -option=value. For example, the mount command: mount -t hfs -o nosuid,-w,-m=755 /dev/disk2s9 /tmp causes mount to execute the equivalent of: /sbin/mount_hfs -o nosuid -w -m 755 /dev/disk2s9 /tmp -r Mount the file system read-only (even the super-user may not write it). The same as the “rdonly” argument to the -o option. -t lfs | external type The argument following the -t is used to indicate the file system type. There is no default local file system for use with mount. A type must be specified in order to mount a non-NFS filesystem. The -t option can be used to indicate that the actions should only be taken on filesystems of the specified type. More than one type may be specified in a comma separated list. The list of filesystem types can be prefixed with “no” to specify the filesystem types for which action should not be taken. For example, the mount command: mount -a -t nonfs,hfs mounts all filesystems except those of type NFS and HFS. If the type is not one of the internally known types, mount will attempt to execute a program in /sbin/mount_XXX where XXX is replaced by the type name. For example, nfs filesystems are mounted by the program /sbin/mount_nfs. -u The -u flag indicates that the status of an already mounted file system should be changed. Any of the options discussed above (the -o option) may be changed; also a file system can be changed from read-only to read-write or vice versa. An attempt to change from read-write to read-only will fail if any files on the filesystem are currently open for writing unless the -f flag is also specified. The set of options is determined by first extracting the options for the file system from the filesystem table (see getfsent(3)) then applying any options specified by the -o argument, and finally applying the -r or -w option. -v Verbose mode. -w Mount the file system read-write. The options specific to NFS filesystems are described in the mount_nfs(8) manual page. SEE ALSO mount(2), getfsent(3), mount_afp(8), mount_cd9660(8), mount_cddafs(8), mount_fdesc(8), mount_hfs(8), mount_apfs(8), mount_msdos(8), mount_nfs(8), mount_smbfs(8), mount_udf(8), mount_webdav(8), umount(8) BUGS It is possible for a corrupted file system to cause a crash. HISTORY A mount command appeared in Version 6 AT&T UNIX. BSD 4 June 16, 1994 BSD 4
|
mount – mount file systems
|
mount [-adfrkuvw] [-t lfs | external_type] mount [-dfrkuvw] special | mount_point mount [-dfrkuvw] [-o options] [-t lfs | external_type] special mount_point
| null | null |
fibreconfig
| null |
fibreconfig – Tool for configuring settings for Fibre Channel controllers and targets.
|
fibreconfig [-r] [-c xx:xx:xx:xx:xx:xx:xx:xx] [-a AL_PA] [-s port_speed] [-t topology_type] [-l] [-v]
|
The available options are as follows: -r Dynamically updates system settings. Note: Cannot be used in conjunction with -c option. -c Defines the host port used for an operation. By default, if no other options are specified, fibreconfig will display information about the specified host port. -a Sets the AL_PA for specified host port. The AL_PA must be one of the values defined in Table 1.1 located in the examples section. -s Sets speed to [ 1gigabit, 2gigabit, 4gigabit, auto ] for specified host port. -t Sets topology to [ nport, nlport, auto ] for specified host port. -l Lists all known information about all nodes ( controllers, targets, and their LUNs ). -v Display version number. RETURN VALUES Returned Error Code 0 No error. -50 Error in user parameter list. FILES /sbin/fibreconfig Executable for version 2.0 and later.
|
1. Set the AL_PA to 1E for a given host port. fibreconfig -c 00:11:22:33:44:55:66:77 -a 1E 2. Disable the AL_PA for a given host port. fibreconfig -c 00:11:22:33:44:55:66:77 -a FF 3. Set the speed to auto for a given host port. fibreconfig -c 00:11:22:33:44:55:66:77 -s auto 4. Set the topology to nlport for a given host port. fibreconfig -c 00:11:22:33:44:55:66:77 -t nlport 5. Table 1.1 List of valid AL_PA settings: ======================================= 01 02 04 08 0F 10 17 18 1B 1D 1E 1F 23 25 26 27 29 2A 2B 2C 2D 2E 31 32 33 34 35 36 39 3A 3C 43 45 46 47 49 4A 4B 4C 4D 4E 51 52 53 54 55 56 59 5A 5C 63 65 66 67 69 6A 6B 6C 6D 6E 71 72 73 74 75 76 79 7A 7C 80 81 82 84 88 8F 90 97 98 9B 9D 9E 9F A3 A5 A6 A7 A9 AA AB AC AD AE B1 B2 B3 B4 B5 B6 B9 BA BC C3 C5 C6 C7 C9 CA CB CC CD CE D1 D2 D3 D4 D5 D6 D9 DA DC E0 E1 E2 E4 E8 EF DIAGNOSTICS Return value on exit provides information about the success or failure of the utility. ERRORS See return values. HISTORY Last updated February 1, 2005. BUGS Known issues: 1. Currently only displays information for Apple shipped Fibre Channel cards. Mac OS X October 27, 2004 Mac OS X
|
fstyp_hfs
|
The fstyp_hfs utility is not intended to be run directly, but rather called by fstyp(8) while it is trying to determine which file system type is present on the given device. It returns 1 if it thinks the device contains an HFS volume, and 0 otherwise. SEE ALSO fstyp(8) macOS 14.5 August 15, 2005 macOS 14.5
|
fstyp_hfs – check for an HFS volume
|
fstyp_hfs device
| null | null |
newfs_hfs
|
Newfs_hfs builds an HFS Plus file system on the specified special device. Before running newfs_hfs the disk should be partitioned using the Disk Utility application or pdisk(8). The file system default parameters are calculated based on the size of the disk partition. Typically the defaults are reasonable, however newfs_hfs has several options to allow the defaults to be selectively overridden. The options are as follows: -N [partition-size] Causes the file system parameters to be printed out without really creating the file system. If the argument following the -N starts with a decimal digit, it is assumed to be a partition size. The paritition size may be given in decimal, octal (with leading `0'), or hexadecimal (with leading `0x'). The partition size argument can be specified in 512-byte blocks (with a `b' suffix), petabytes (`p' suffix), terabytes (`t' suffix), gigabytes (`g' suffix), megabytes (`m' suffix), or kilobytes (`k' suffix). All suffixes indicate binary, not decimal, multipliers (e.g., `1k' is 1024 bytes). If no suffix is specified, the value is assumed to be in bytes; if an illegal suffix is specified, it results in a size of 0 bytes. If the partition size is given, then no special device argument shall be provided. If no partition size is given, then the size of the given special device is used instead, and the special device will not be written to. -U uid Set the owner of the file system's root directory to uid. -G gid Set the group of the file system's root directory to gid. -M mask Specify the octal access permissions mask for the file system's root directory. -P Set kHFSContentProtectionBit in the volume's attributes, which will cause the volume to be mounted with the "protect" option if the kernel supports it. -s Creates a case-sensitive HFS Plus filesystem. By default a case-insensitive filesystem is created. Case-sensitive HFS Plus file systems require a Mac OS X version of 10.3 (Darwin 7.0) or later. -b block-size The allocation block size of the file system. The default value is 4096. -c clump-size-list This specifies the clump and/or initial sizes, in allocation blocks, for the various metadata files. Clump sizes are specified with the -c option followed by a comma separated list of the form arg=blocks. Example: -c c=5000,e=500 a=blocks Set the attribute file clump size. b=blocks Set the allocation bitmap file clump size. c=blocks Set the catalog file clump size. d=blocks Set the data fork clump size. e=blocks Set the extent overflow file clump size. r=blocks Set the resource fork clump size. -i first-cnid This specifies the initial catalog node ID for user files and directories. The default value is 16. -I initial-size-list This specifies the initial size, in allocation blocks, for the various metadata files. Initial sizes are specified with the -I option followed by a comma separated list of the form arg=blocks. Example: -I c=5000,e=500 a=blocks Set the initial attribute file size. c=blocks Set the initial catalog file size. e=blocks Set the initial extent overflow file size. -J [journal-size] Creates a journaled HFS+ volume. The default journal size varies, based on the size of the volume. Appending an 'M' to the journal size implies megabytes (i.e. 64M is 64 megabytes). The maximum journal size is 1024 megabytes. -D journal-device Creates the journal on special device journal-device. -n node-size-list This specifies the b-tree node sizes, in bytes, for the various b-tree files. Node sizes are specified with the -n option followed by a comma separated list of the form arg=bytes. The node size must be a power of two and no larger than 32768 bytes. Example: -n c=8192,e=4096 a=bytes Set the attribute b-tree node size. c=bytes Set the catalog b-tree node size. e=bytes Set the extent overflow b-tree node size. -v volume-name Volume name (file system name) in ascii or UTF-8 format. SEE ALSO mount(8), pdisk(8) HISTORY The newfs_hfs command appeared in Mac OS X Server 1.0 . As of Mac OS X 10.6, this utility no longer generates HFS standard file systems. Mac OS X June 19, 2008 Mac OS X
|
newfs_hfs – construct a new HFS Plus file system
|
newfs_hfs [-N] [-U uid] [-G gid] [-M mask] [-P] [-s] [-b block-size] [-c clump-size-list] [-i first-cnid] [-J [journal-size]] [-D journal-device] [-n node-size-list] [-v volume-name] special newfs_hfs -N partition-size [-U uid] [-G gid] [-M mask] [-P] [-h | -w] [-s] [-b block-size] [-c clump-size-list] [-i first-cnid] [-J [journal-size]] [-D journal-device] [-n node-size-list] [-v volume-name]
| null | null |
dynamic_pager
|
The dynamic_pager daemon can be used to specify a base name for swapfile names using the "-F" command line option or by modifying the configuration plist file.
|
dynamic_pager – swap configuration daemon
|
dynamic_pager [-F filename]
|
-F The base name of the filename to use for the swapfiles. By default this is /private/var/vm/swapfile. FILES /private/var/vm/swapfile* Swapfiles. /System/Library/LaunchDaemons/com.apple.dynamic_pager.plist Configuration file. macOS July 8, 2003 macOS
| null |
launchd
|
launchd manages processes, both for the system as a whole and for individual users. The primary and preferred interface to launchd is via the launchctl(1) tool which (among other options) allows the user or administrator to load and unload jobs. Where possible, it is preferable for jobs to launch on demand based on criteria specified in their respective configuration files. launchd also manages XPC services that are bundled within applications and frameworks on the system. During boot launchd is invoked by the kernel to run as the first process on the system and to further bootstrap the rest of the system. You cannot invoke launchd directly. NOTES On Darwin operating systems, the canonical way to launch a daemon is through launchd as opposed to traditional POSIX and POSIX-like mechanisms or mechanisms provided in earlier versions of OS X. These alternate methods should be considered deprecated and not suitable for new projects. In the launchd lexicon, a daemon is, by definition, a system-wide service of which there is one instance for all clients. An agent is a service that runs on a per-user basis. Daemons should not attempt to display UI or interact directly with a user's login session. Any and all work that involves interacting with a user should be done through agents. XPC services which are marked with a ServiceType of System are functionally equivalent to daemons and run in the same environment, sharing the same Mach bootstrap namespace. XPC services which are marked with a ServiceType of User are equivalent to agents with the LimitLoadToSessionType key specifying the Background session and run in the same environment, sharing the same Mach bootstrap namespace. See launchd.plist(5) for more information about user sessions. On Darwin platforms, a user environment includes a specific Mach bootstrap subset, audit session and other characteristics not recognized by POSIX. Therefore, making the appropriate setuid(2) and setgid(2) system calls is not sufficient to completely assume the identity for a given user. Running a service as a launchd agent or a per-user XPC service is the only way to run a process with a complete identity of that user. FILES ~/Library/LaunchAgents Per-user agents provided by the user. /Library/LaunchAgents Per-user agents provided by the administrator. /Library/LaunchDaemons System-wide daemons provided by the administrator. /System/Library/LaunchAgents Per-user agents provided by Apple. /System/Library/LaunchDaemons System-wide daemons provided by Apple. SEE ALSO launchctl(1), launchd.plist(5), DEVELOPER DOCUMENTATION The Daemons and Services Programming Guide can be found at the following URL: https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/Introduction.html Darwin 25 November, 2013 Darwin
|
launchd – System wide and per-user daemon/agent manager
| null | null | null |
newfs_exfat
|
The newfs_exfat utility creates an ExFAT file system on device special. If the -R option is not given, and the device is already formatted as ExFAT, it will preserve the partition offset, bytes per cluster, FAT offset and size, number of FATs, offset to start of clusters, number of clusters, volume serial number, and volume name (label). If a volume name was specified via the -v option, that name is used instead of the volume's previous name. The options are as follow: -N Don't create a file system: just print out parameters. -R Do not check whether the device is currently formatted as ExFAT. Always derive the partition offset, bytes per cluster, FAT offset and size, and offset to start of clusters based on the device type and size. -I volume-serial-number Volume ID, a 32-bit integer. -S bytes-per-sector Number of bytes per sector. Acceptable values are powers of 2 in the range 512 through 4096. -a sectors-per-FAT Number of sectors per FAT. -b bytes-per-cluster File system block size (bytes per cluster). Acceptable values are powers of 2 in the range 512 through 33554432. -c sectors-per-cluster Sectors per cluster. Acceptable values are powers of 2 in the range 1 through 65536. -n number-of-FATs Number of FATs. Acceptable values are 1 or 2. The default is 1. Using any value other than 1 is discouraged, and may be incompatible with other devices. -s total-sectors The total number of sectors in the device. -v volume-name Volume name (label). The name will be converted to UTF-16, and must be no longer than 11 UTF-16 characters. ASCII control characters and some punctuation characters are not allowed (similar to DOS 8.3-style names). NOTE: The volume name may be an empty (zero-length) string.
|
newfs_exfat – construct a new ExFAT file system
|
newfs_exfat [-N] [-R] [-I volume-serial-number] [-S bytes-per-sector] [-a sectors-per-FAT] [-b bytes-per-cluster] [-c sectors-per-cluster] [-n number-of-FATs] [-s total-sectors] [-v volume-name] special
| null |
newfs_exfat /dev/disk0s1 Create a file system, using default parameters (or existing ExFAT layout), on /dev/rdisk0s1. newfs_exfat -v Hello disk2s1 Create a file system with the name "Hello" on /dev/rdisk2s1. SEE ALSO mount_exfat(8), fsck_exfat(8) DIAGNOSTICS Exit status is 0 on success and 1 on error. HISTORY The newfs_exfat command appeared in Mac OS X 10.6.3. Darwin January 19, 2010 Darwin
|
apfs_unlockfv
|
The apfs_unlockfv utility unlocks an APFS-formatted FileVault-encrypted data volume. The path parameter is optional, but if provided should be a path on a mounted APFS System volume. (This volume must have the System role, and must be in a volume group with a locked Data volume.) If path is not provided, apfs_unlockfv will attempt to unlock the data volume paired to the system volume at / . Upon invocation, apfs_unlockfv will prompt the user for a password. This password can be for any user on the volume being unlocked, including the Disk user. The options are as follows: -h Print a usage message. -W Unlock with empty password. EXIT STATUS apfs_unlockfv exits with 0 on success, and >0 if an error occurs. If the volume was already unlocked, apfs_unlockfv also exits with 0. SEE ALSO diskutil(8), mount_apfs(8), newfs_apfs(8) HISTORY The apfs_unlockfv utility was introduced in macOS 11. macOS 14.5 June 1, 2020 macOS 14.5
|
apfs_unlockfv – unlock an APFS FileVault data volume
|
apfs_unlockfv [-h] apfs_unlockfv [-W] [path]
| null | null |
apfs_hfs_convert
|
The apfs_hfs_convert command converts an existing HFS file system to a new APFS file system. It is recommended not to run the apfs_hfs_convert directly, but to run `diskutil apfs convert`. The device-path parameter should be the path to a disk device node, such as /dev/disk1s2, with an existing HFS file system, which needs to be converted. The device-path may be a path to a whole disk, such as /dev/disk0, which contains Lightweight Volume Manager (LwVM) structures; all HFS slices will be converted and LwVM replaced by a GPT partition map with a single partition containing the APFS container. The options are as follows: -e | --estimate Estimate the APFS metadata size after conversion. -v | --verbose Increase verbosity of the output. -s | --force-case-sensitive Force the converted volume to be case-sensitive. By default, the converted volume will have the same case-sensitivity as the original HFS volume. -S path | --stats path Print statistics about the conversion to the supplied path. If the path is - then the statistics are printed to standard output. -n | --dry-run Do not finalize the conversion to APFS. Volume remains HFS. -f | --force Force conversion if volume is dirty (journal is non-empty, volume had inconsistencies, or volume is not journaled and not unmounted cleanly). -F index | --fixed index Volume number index (0-based) should be formatted as fixed-size. Usually used when converting LwVM. -M mount_path | --mount-path mount_path When converting LwVM systems, which require a special "conversion mount" of the underlying device, use the given mount_path as the mount point. If this option is not used, a temporary directory will be created and used. -o nx-apfs-format NX or APFS format options. -g If conversion succeeds, modify the GPT UUID. -D | --skip-single-dirlinks Convert all former and current directory hardlinks to files/aliases. --feature-format Allow for one-off specific formatting features to be toggled on or off during the conversion to APFS. Values must be specified in a CSV string. For example "feature=value,feature2=value2,..." dirents=unhashed is a feature format flag that will specify to the converter that it should produce a volume with legacy (non-standard) directory entries. That is, the resulting volume will have file names that are both normalization-sensitive and case-sensitive. This is not recommended in most cases. EXIT STATUS The apfs_hfs_convert utility exits 0 on success, and >0 if an error occurs.
|
apfs_hfs_convert – convert an existing HFS file system to APFS file system
|
apfs_hfs_convert [-D] [-g] [-e] [-v] [-i] [-S path] [-n] [-f] [-F index] [-M mount_path] [-o nx-apfs-format] <device-path>
| null |
The following converts the HFS file system on the /dev/disk1s2 device: apfs_hfs_convert -v /dev/disk1s2 SEE ALSO mount_apfs(8) , newfs_apfs(8) HISTORY The apfs_hfs_convert utility first appeared in OS X 10.12. Mac OS X September 15, 2015 Mac OS X
|
nologin
|
The nologin is intended as a replacement shell field for accounts that have been disabled. When executed, nologin first writes about the login attempt to syslog(3) and then displays a message that an account is not available. To disable all logins, investigate nologin(5). EXIT STATUS The nologin utility always exits non-zero. SEE ALSO login(1), nologin(5) HISTORY The nologin utility appeared in 4.4BSD. macOS 14.5 April 15, 2020 macOS 14.5
|
nologin – politely refuse a login
|
nologin
| null | null |
mount_afp
|
The mount_afp command mounts the AFP volume denoted by the afp_url afp://[user[;AUTH=uamname][:password]@]host[:port]/volumename at the mount point indicated by node. This command is normally executed by mount(8) when the -t afp option is used. If the -i option is not used, all the required information to establish a login to the remote server must be available in the afp URL, including username & password if needed. The arguments and options are: -i Interactive mode, you are prompted for the password if you did not supply one in the url. -s Soft mount (default). Network errors, e.g. timeouts, will be retried for a much shorter amount of time. If the network errors persist, then the mount will be force unmounted. -k Hard mount. Network errors, e.g. timeouts, will be retried for an extended amount of time. If the network errors persist, then the mount will be force unmounted. -o Options passed to mount(2) are specified with the -o option followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. Additional options supported by the AFP Client are as follows: nobrowse Indicate to the Carbon subsystem that this volume is not to be displayed to the user. automounted Set flags on the mountpoint to indicate that the volume has been mounted by the automounter. afp_url There are two forms of afp URL, one for TCP/IP and one for AppleTalk: afp://[user[;AUTH=uamname][:password]@]host[:port]/volume afp:/at/[user[;AUTH=uamname][:password]@]servername[:zonename]/volume Denotes the afp server and sharepoint to mount. It may also contain the username & password required to log into the server. uamname is the protocol name of the authentication method. If port is not specified, then port 548 is used. node Path to mount point, which must be a directory that the user has write permissions for.
|
mount_afp – mount an afp (AppleShare) filesystem
|
mount_afp [-i] [-s] [-k] [-o options] afp_url node
| null |
The following example illustrates how to mount the afp volume server.company.com/volumename/ at the mount point /Volumes/mntpnt: mkdir /Volumes/mntpnt mount_afp afp://username:userpass@server.company.com/volumename/ /Volumes/mntpnt This example shows the proper url to use to mount the volume guestVolume from the afp server myserver as guest (if no uam and no username, then use guest uam): mkdir /Volumes/guest mount_afp "afp://myserver/guestVolume" /Volumes/guest This example shows the proper url to use to mount the volume myVolume from the afp server myserver using Kerberos authentication: mkdir /Volumes/myVolume mount_afp "afp://;AUTH=Client%20Krb%20v2@myserver/myVolume" /Volumes/myVolume SEE ALSO mount(2), unmount(2), mount(8) HISTORY The mount_afp command first appeared Mac OS X version 10.0. Kerberos authentication was added in Mac OS X version 10.2 RETURN VALUES 0 mount_afp successfully mounted the volume directory. [ENODEV (19)] The server volume could not be mounted by mount_afp because the server was not found or because the sharepoint does not exist, or because node does not have proper access. [EACCES (13)] The volume could not be mounted by mount_afp because the user did not provide proper authentication credentials. [ENOTDIR (20)] The volume could not be mounted by mount_afp because the mountpoint was not a directory. Mac OS X May 8, 2002 Mac OS X
|
mount_virtiofs
|
The mount_virtiofs command attaches the virtio-fs file system associated with fs_tag to the global file system namespace at the location indicated by directory. The options are as follows: -r Mount file system as read-only. -u Set the owner of the files in the file system to uid. The uid may be a username or a numeric value. -g Set the group of the files in the file system to gid. The gid may be a group name or a numeric value. DIAGNOSTICS The mount_virtiofs utility exits 0 on success, and >0 if an error occurs. SEE ALSO mount(2), unmount(2), fstab(5), mount(8), umount(8) macOS September 14, 2020 macOS
|
mount_virtiofs – mount a virtio-fs volume
|
mount_virtiofs [-r] [-u uid] [-g gid] fs_tag directory
| null | null |
mount_smbfs
|
The mount_smbfs command mounts a share from a remote server using SMB/CIFS protocol. The options are as follows: -N Do not ask for a password. At run time, mount_smbfs reads the ~/Library/Preferences/nsmb.conf file for additional configuration parameters and a password. If no password is found, mount_smbfs prompts for it. -o Options passed to mount(2) are specified with the -o option followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. Additional options supported by the mount_smbfs are as follows: nobrowse This option indicates that the mount point should not be visible via the GUI (i.e., appear on the Desktop as a separate volume). automounted Set flags on the mountpoint to indicate that the volume has been mounted by the automounter. nostreams Don't use NTFS Streams even if they are supported by the server. soft Make the mount soft. Fail file system calls after a number of seconds. nonotification Turn off using notifications for this volume. nodatacache Turn off using file data caching for this volume. nomdatacache Turn off using meta data caching for this volume. sessionencrypt Force session encryption to be used shareencrypt Force share encryption to be used for that share and also for IPC$ traffic filemode Specify permissions that should be assigned to files. The value must be specified as an octal number. Default value is taken from mount point. Note that these permissions can differ from the rights granted by SMB server. dirmode Specify permissions that should be assigned to directories. The value must be specified as an octal number. Default value adds execute permission where the file mode gives read permission. Note that these permissions can differ from the rights granted by SMB server. snapshot Do a read only mount using the specific snapshot of the share. A new session is created to allow multiple snapshots of the same share to be mounted. Value must be in GMT format e.g. @GMT-YYYY.MM.DD-HH.MM.SS nopassprompt Do not ask for a password. At run time, mount_smbfs reads the ~/Library/Preferences/nsmb.conf file for additional configuration parameters and a password. If no password is found, mount_smbfs prompts for it. forcenewsession Force a new session to be created to the server. -f mode, -d mode Specify permissions that should be assigned to files and directories. The values must be specified as octal numbers. Default value for the file mode is taken from mount point, default value for the directory mode adds execute permission where the file mode gives read permission. Note that these permissions can differ from the rights granted by SMB server. -h Prints a help message, much like the SYNOPSIS above. -s Force a new session to be created to the server. -t gmt_token Do a read only mount using the specific snapshot of the share. A new session is created to allow multiple snapshots of the same share to be mounted. Value must be in GMT format e.g. @GMT- YYYY.MM.DD-HH.MM.SS -v Prints version. //[domain;][user[:password]@] server[/share] The mount_smbfs command will use server as the NetBIOS name of remote computer, user as the remote user name and share as the resource name on a remote server. Domain and/or password may be specified here. If user is omitted the logged in user id will be used. Omitting share is an error when mount_smbfs is run from the command line, otherwise a browsing dialogue is presented. path Path to mount point. FILES nsmb.conf Keeps static parameters for connections and other information. See man nsmb.conf for details.
|
mount_smbfs – mount a shared resource from an SMB file server
|
mount_smbfs [-N] [-o options] [-d mode] [-f mode] [-h] [-s] [-t gmt_token] [-v] //[domain;][user[:password]@]server[/share] path
| null |
This example shows the proper url to use to mount the share PUBLIC from the SMB server myserver : mkdir /smb/public mount -t smbfs //username:userpass@myserver/PUBLIC /smb/public This example shows the proper url to use to mount the share PUBLIC from the SMB server myserver as guest: mkdir /smb/public mount -t smbfs //guest:@myserver/PUBLIC /smb/public Note: You should always use the system mount command and never call mount_smbfs directly. SEE ALSO mount(2), nsmb.conf(5), mount(8), umount(8) BUGS Please report bugs to Apple. AUTHORS Boris Popov ⟨bp@butya.kz⟩, ⟨bp@FreeBSD.org⟩ FreeBSD March 10, 2000 FreeBSD
|
mount_tmpfs
|
The mount_tmpfs command creates a new tmpfs (in-memory file system) volume and attaches it to the global file system namespace at the location indicated by directory. The options are as follows: -o options Options passed to mount(2) are specified with the -o option followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. -i Make the volume case-insensitive (default). -e Make the volume case-sensitive. -n max_nodes Set the maximum number of nodes available to the file system to max_nodes. -s max_mem_size Set the maximum total file system size to max_mem_size bytes, unless suffixed with one of k, m, g, or t, which denote kilobyte, megabyte, gigabyte and terabyte respectively. DIAGNOSTICS The mount_tmpfs utility exits 0 on success, and >0 if an error occurs. SEE ALSO mount(2), unmount(2), mount(8), umount(8) HISTORY The mount_tmpfs utility first appeared in macOS 11. Mac OS X September 16, 2020 Mac OS X
|
mount_tmpfs – mount a tmpfs volume
|
mount_tmpfs [-o options] [-i | -e] [-n max_nodes] [-s max_mem_size] directory
| null | null |
ping6
|
The ping6 utility uses the ICMPv6 protocol's mandatory ICMP6_ECHO_REQUEST datagram to elicit an ICMP6_ECHO_REPLY from a host or gateway. ICMP6_ECHO_REQUEST datagrams (``pings'') have an IPv6 header, and ICMPv6 header formatted as documented in RFC2463. The options are as follows: -a addrtype Generate ICMPv6 Node Information Node Addresses query, rather than echo-request. addrtype must be a string constructed of the following characters. a requests unicast addresses from all of the responder's interfaces. If the character is omitted, only those addresses which belong to the interface which has the responder's address are requests. c requests responder's IPv4-compatible and IPv4-mapped addresses. g requests responder's global-scope addresses. s requests responder's site-local addresses. l requests responder's link-local addresses. A requests responder's anycast addresses. Without this character, the responder will return unicast addresses only. With this character, the responder will return anycast addresses only. Note that the specification does not specify how to get responder's anycast addresses. This is an experimental option. -b bufsiz Set socket buffer size. -B boundif Bind the socket to interface This option is an Apple addition. boundif for sending. -C Prohibit the socket from using the cellular network interface. -c count Stop after sending (and receiving) count ECHO_RESPONSE packets. If this option is specified in conjunction with ping sweeps, each sweep will consist of count packets. -D Disable IPv6 fragmentation. -d Set the SO_DEBUG option on the socket being used. -f Flood ping. Outputs packets as fast as they come back or one hundred times per second, whichever is more. For every ECHO_REQUEST sent a period “.” is printed, while for every ECHO_REPLY received a backspace is printed. This provides a rapid display of how many packets are being dropped. Only the super-user may use this option. This can be very hard on a network and should be used with caution. -G sweepmaxsize[,sweepminsize[,sweepincrsize]] sweepmaxsize specifies the maximum size of the payload when sending sweeping pings and is required for sweeps. sweepminsize specifies the size of the payload to start with when sending sweeping pings -- the default value is 0. sweepincrsize specifies the number of bytes to increment the size of the payload after each sweep when sending sweeping pings -- the default value is 1. This option is an Apple addition. -g gateway Specifies to use gateway as the next hop to the destination. The gateway must be a neighbor of the sending node. -H Specifies to try reverse-lookup of IPv6 addresses. The ping6 utility does not try reverse-lookup unless the option is specified. -h hoplimit Set the IPv6 hoplimit. -I interface Source packets with the given interface address. This flag applies if the ping destination is a multicast address, or link- local/site-local unicast address. -i wait Wait wait seconds between sending each packet. The default is to wait for one second between each packet. The wait time may be fractional, but only the super-user may specify values less than 0.1 second. This option is incompatible with the -f option. -k trafficclass Specifies the traffic class to use for sending ICMPv6 packets. The supported traffic classes are BK_SYS, BK, BE, RD, OAM, AV, RV, VI, VO and CTL. By default ping6 uses the control traffic class (CTL). This option is an Apple addition. -K netservicetype Specifies the network service type to use for sending ICMPv6 packets. The supported network service type are BK_SYS, BK, BE, RV, AV, RD, OAM, VI, SIG and VO. Note this overrides the default traffic class (-k can still be specified after -K to use both). This option is an Apple addition. -l preload If preload is specified, ping6 sends that many packets as fast as possible before falling into its normal mode of behavior. Only the super-user may use this option. -m By default, ping6 asks the kernel to fragment packets to fit into the minimum IPv6 MTU. The -m option will suppress the behavior in the following two levels: when the option is specified once, the behavior will be disabled for unicast packets. When the option is more than once, it will be disabled for both unicast and multicast packets. -n Numeric output only. No attempt will be made to lookup symbolic names from addresses in the reply. -N Probe node information multicast group (ff02::2:xxxx:xxxx). host must be string hostname of the target (must not be a numeric IPv6 address). Node information multicast group will be computed based on given host, and will be used as the final destination. Since node information multicast group is a link-local multicast group, outgoing interface needs to be specified by -I option. -o Exit successfully after receiving one reply packet. -p pattern You may specify up to 16 “pad” bytes to fill out the packet you send. This is useful for diagnosing data-dependent problems in a network. For example, “-p ff” will cause the sent packet to be filled with all ones. -P policy policy specifies IPsec policy to be used for the probe. -q Quiet output. Nothing is displayed except the summary lines at startup time and when finished. -r Audible. Include a bell (ASCII 0x07) character in the output when any packet is received. -R Audible. Output a bell (ASCII 0x07) character when no packet is received before the next packet is transmitted. To cater for round-trip times that are longer than the interval between transmissions, further missing packets cause a bell only if the maximum number of unreceived packets has increased. -S sourceaddr Specifies the source address of request packets. The source address must be one of the unicast addresses of the sending node, and must be numeric. -s packetsize Specifies the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data. You may need to specify -b as well to extend socket buffer size. -t Generate ICMPv6 Node Information supported query types query, rather than echo-request. -s has no effect if -t is specified. -v Verbose output. ICMP packets other than ECHO_RESPONSE that are received are listed. -w Generate ICMPv6 Node Information DNS Name query, rather than echo-request. -s has no effect if -w is specified. -W Same as -w, but with old packet format based on 03 draft. This option is present for backward compatibility. -s has no effect if -w is specified. -z tclass Use the specified traffic class. --apple-connect Connects the socket to the destination address. This option is an Apple addition. --apple-time Prints the time a packet was received. This option is an Apple addition. hops IPv6 addresses for intermediate nodes, which will be put into type 0 routing header. host IPv6 address of the final destination node. When using ping6 for fault isolation, it should first be run on the local host, to verify that the local network interface is up and running. Then, hosts and gateways further and further away should be “pinged”. Round-trip times and packet loss statistics are computed. If duplicate packets are received, they are not included in the packet loss calculation, although the round trip time of these packets is used in calculating the round-trip time statistics. When the specified number of packets have been sent (and received) or if the program is terminated with a SIGINT, a brief summary is displayed, showing the number of packets sent and received, and the minimum, mean, maximum, and standard deviation of the round-trip times. If ping6 receives a SIGINFO (see the status argument for stty(1)) signal, the current number of packets sent and received, and the minimum, mean, maximum, and standard deviation of the round-trip times will be written to the standard output in the same format as the standard completion message. This program is intended for use in network testing, measurement and management. Because of the load it can impose on the network, it is unwise to use ping6 during normal operations or from automated scripts. DUPLICATE AND DAMAGED PACKETS The ping6 utility will report duplicate and damaged packets. Duplicate packets should never occur when pinging a unicast address, and seem to be caused by inappropriate link-level retransmissions. Duplicates may occur in many situations and are rarely (if ever) a good sign, although the presence of low levels of duplicates may not always be cause for alarm. Duplicates are expected when pinging a broadcast or multicast address, since they are not really duplicates but replies from different hosts to the same request. Damaged packets are obviously serious cause for alarm and often indicate broken hardware somewhere in the ping6 packet's path (in the network or in the hosts). TRYING DIFFERENT DATA PATTERNS The (inter)network layer should never treat packets differently depending on the data contained in the data portion. Unfortunately, data-dependent problems have been known to sneak into networks and remain undetected for long periods of time. In many cases the particular pattern that will have problems is something that does not have sufficient “transitions”, such as all ones or all zeros, or a pattern right at the edge, such as almost all zeros. It is not necessarily enough to specify a data pattern of all zeros (for example) on the command line because the pattern that is of interest is at the data link level, and the relationship between what you type and what the controllers transmit can be complicated. This means that if you have a data-dependent problem you will probably have to do a lot of testing to find it. If you are lucky, you may manage to find a file that either cannot be sent across your network or that takes much longer to transfer than other similar length files. You can then examine this file for repeated patterns that you can test using the -p option of ping6. EXIT STATUS The ping6 utility returns 0 on success (the host is alive), 2 if the transmission was successful but no responses were received, any other non-zero value if the arguments are incorrect or another error has occurred.
|
ping6 – send ICMPv6 ECHO_REQUEST packets to network hosts
|
ping6 [-CDdfHmnNoqtvwW] [-a addrtype] [-b bufsiz] [-B boundif] [-c count] [-G sweepmaxsize[,sweepminsize[,sweepincrsize]]] [-g gateway] [-G sweep] [-h hoplimit] [-I interface] [-i wait] [-k trafficclass] [-K netservicetype] [-l preload] [-P policy] [-p pattern] [-S sourceaddr] [-s packetsize] [-z tclass] [--apple-connect] [--apple-time] [hops ...] host
| null |
Normally, ping6 works just like ping(8) would work; the following will send ICMPv6 echo request to dst.foo.com. ping6 -n dst.foo.com The following will probe hostnames for all nodes on the network link attached to wi0 interface. The address ff02::1 is named the link-local all-node multicast address, and the packet would reach every node on the network link. ping6 -w ff02::1%wi0 The following will probe addresses assigned to the destination node, dst.foo.com. ping6 -a agl dst.foo.com SEE ALSO netstat(1), icmp6(4), inet6(4), ip6(4), ifconfig(8), ping(8), routed(8), traceroute(8), traceroute6(8) A. Conta and S. Deering, Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification, RFC2463, December 1998. Matt Crawford, IPv6 Node Information Queries, draft-ietf-ipngwg-icmp- name-lookups-09.txt, May 2002, work in progress material. HISTORY The ping(8) utility appeared in 4.3BSD. The ping6 utility with IPv6 support first appeared in the WIDE Hydrangea IPv6 protocol stack kit. IPv6 and IPsec support based on the KAME Project (http://www.kame.net/) stack was initially integrated into FreeBSD 4.0. BUGS The ping6 utility is intentionally separate from ping(8). There have been many discussions on why we separate ping6 and ping(8). Some people argued that it would be more convenient to uniform the ping command for both IPv4 and IPv6. The following are an answer to the request: From a developer's point of view: since the underling raw sockets API is totally different between IPv4 and IPv6, we would end up having two types of code base. There would actually be less benefit to uniform the two commands into a single command from the developer's standpoint. From an operator's point of view: unlike ordinary network applications like remote login tools, we are usually aware of address family when using network management tools. We do not just want to know the reachability to the host, but want to know the reachability to the host via a particular network protocol such as IPv6. Thus, even if we had a unified ping(8) command for both IPv4 and IPv6, we would usually type a -6 or -4 option (or something like those) to specify the particular address family. This essentially means that we have two different commands. macOS 14.5 March 29, 2013 macOS 14.5
|
kextload
|
The kextload program is used to explicitly load kernel extensions (kexts). For most kexts, kextload must run as the superuser (root). Kexts installed under /System/ with an OSBundleAllowUserLoad property set to true may be loaded via kextload by non-root users. Notice: On Mac OS X 10.6 (Snow Leopard), the developer functionality of kextload has moved to the new program kextutil(8); all developer-related options have been removed from kextload and are no longer recognized. On Mac OS X 10.6 (Snow Leopard), kextload simply forwards a load request to kextd(8), which performs all communication with the kernel. kextload is a formal interface for kext loading in all versions of Darwin OS and macOS. Software and installers can rely on its presence and invoke it in order to load kexts. Note that long options are present as of Mac OS X 10.6 (Snow Leopard). Mac OS X 10.6 (Snow Leopard) introduces C functions for loading kexts: KextManagerLoadKextWithIdentifier() and KextManagerLoadKextWithURL(), which are described in Apple's developer documentation. ARGUMENTS AND OPTIONS kext The pathname of a kext bundle to load. The kext's plugins are available for dependency resolution. Kexts can also be specified by CFBundleIdentifier with the -bundle-id option. -b identifier, -bundle-id identifier Look up the kext whose CFBundleIdentifier is identifier within the set of known kexts and load it. The kext of the highest CFBundleVersion with the given identifier is used; in the case of version ties, the last such kext specified on the command line is used. See the -dependency and -repository options for more information. -d kext, -dependency kext Add kext and its plugins to the set of known kexts for resolving dependencies. This is useful for adding a single kext from a directory while excluding the others. See the -repository option for more information. -h, -help Print a help message describing each option flag and exit with a success result, regardless of any other options on the command line. -q, -quiet Quiet mode; print no informational or error messages. -r directory, -repository directory Use directory as a repository of kexts. This adds to the set of known kexts for resolving dependencies or looking up by CFBundleIdentifier when using the -bundle-id option. This is not recursive; only kexts directly within the directory, and their plugins, are scanned. See also the -dependency option. -v [0-6 | 0x####], -verbose [0-6 | 0x####] Verbose mode; print information about program operation. Higher levels of verbosity include all lower levels. You can specify a level from 0-6, or a bitmask of flags as a hexadecimal number prefixed with 0x (as described in kext_logging(8)). Because kextload messages kextd(8), to perform the actual work of loading, the decimal levels 1-6 generally have little effect. You may wish to use kextutil(8) if you want verbose output about the kext loading operation. -- End of all options. Only kext names follow.
|
kextload – load kernel extensions (kexts) into the kernel
|
kextload [options] [--] [kext ...] DEPRECATED The kextload utility has been deprecated. Please use the kmutil(8) equivalent: kmutil load.
| null |
To load a kext, run kextload and supply a kext bundle name; no options are required: kextload TabletDriver.kext Alternatively, you can use the -bundle-id (-b) option to specify a kext by its CFBundleIdentifier: kextload -bundle-id com.mycompany.driver.TabletDriver With no additional options kextload looks in the extensions directories (/System/Library/Extensions/ and /Library/Extensions/) for a kext with the given CFBundleIdentifier. Adding repository directories with the -repository option or individual kexts with the -dependency option expands the set of kexts that kextload looks among for dependency resolution and for loading by bundle identifier: kextload -repository /Applications/MyApp.app/Contents/Resources \ TabletDriver.kext FILES /System/Library/Extensions/ The standard system repository of kernel extensions /Library/Extensions/ The standard repository of non Apple kernel extensions DIAGNOSTICS kextload exits with a zero status if all kexts specified load successfully (or are already loaded). If any kext fails to load, kextload prints an error message for that kext, continues trying to load any remaining kexts, then exits with a nonzero status. For a kext to be loadable, it must be valid, authenticated, and all dependencies of the kext must be available and loadable. A valid kext has a well formed bundle, info dictionary, and an executable built for the running kernel's architecture. An authentic kext's component files, not including plugins, are owned by root:wheel, with permissions nonwritable by group and other. If your kext fails to load, try using kextutil(8) to examine the kext for problems. SEE ALSO kmutil(8), kernelmanagerd(8), kextcache(8), kextd(8), kextstat(8), kextunload(8), kextutil(8), kext_logging(8) Darwin November 14, 2012 Darwin
|
mount_cddafs
|
The mount_cddafs command attaches the CDDA filesystem residing on the device special to the global filesystem namespace at the location indicated by node. This command is normally executed by mount(8) at boot time. The options are as follows: -o Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. SEE ALSO mount(2), unmount(2), mount(8) HISTORY The mount_cddafs utility first appeared in MacOS X Public Beta Darwin January 31, 2002 Darwin
|
mount_cddafs – mount an Audio CD
|
mount_cddafs [-o options] special node
| null | null |
mount_fdesc
|
The mount_fdesc command attaches an instance of the per-process file descriptor namespace to the global filesystem namespace. The conventional mount point is /dev and the filesystem should be union mounted in order to augment, rather than replace, the existing entries in /dev. This command is normally executed by mount(8) at boot time. The options are as follows: -o Options are specified with a -o flag followed by a comma separated string of options. See the mount(8) man page for possible options and their meanings. The contents of the mount point are fd, stderr, stdin, stdout and tty. fd is a directory whose contents appear as a list of numbered files which correspond to the open files of the process reading the directory. The files /dev/fd/0 through /dev/fd/# refer to file descriptors which can be accessed through the file system. If the file descriptor is open and the mode the file is being opened with is a subset of the mode of the existing descriptor, the call: fd = open("/dev/fd/0", mode); and the call: fd = fcntl(0, F_DUPFD, 0); are equivalent. The files /dev/stdin, /dev/stdout and /dev/stderr appear as symlinks to the relevant entry in the /dev/fd sub-directory. Opening them is equivalent to the following calls: fd = fcntl(STDIN_FILENO, F_DUPFD, 0); fd = fcntl(STDOUT_FILENO, F_DUPFD, 0); fd = fcntl(STDERR_FILENO, F_DUPFD, 0); Flags to the open(2) call other than O_RDONLY, O_WRONLY and O_RDWR are ignored. The /dev/tty entry is an indirect reference to the current process's controlling terminal. It appears as a named pipe (FIFO) but behaves in exactly the same way as the real controlling terminal device. FILES /dev/fd/# /dev/stdin /dev/stdout /dev/stderr /dev/tty SEE ALSO mount(2), unmount(2), tty(4), fstab(5), mount(8) CAVEATS No ~. and .. entries appear when listing the contents of the /dev/fd directory. This makes sense in the context of this filesystem, but is inconsistent with usual filesystem conventions. However, it is still possible to refer to both ~. and .. in a pathname. This filesystem may not be NFS-exported. HISTORY The mount_fdesc utility first appeared in 4.4BSD. BSD 4.4 March 27, 1994 BSD 4.4
|
mount_fdesc – mount the file-descriptor file system
|
mount_fdesc [-o options] fdesc mount_point
| null | null |
newfs_msdos
|
The newfs_msdos utility creates a FAT12, FAT16, or FAT32 file system on device special, using disktab(5) entry disktype to determine geometry, if required. The options are as follows: -N Don't create a file system: just print out parameters. -B boot Get bootstrap from file. -F FAT-type FAT type (one of 12, 16, or 32). -I volid Volume ID. -O OEM OEM string (up to 8 characters). The default is "BSD 4.4" (with two spaces). -S sector-size Number of bytes per sector. Acceptable values are powers of 2 in the range 128 through 32768. -a FAT-size Number of sectors per FAT. -b block-size File system block size (bytes per cluster). This should resolve to an acceptable number of sectors per cluster (see below). -c cluster-size Sectors per cluster. Acceptable values are powers of 2 in the range 1 through 128. -e dirents Number of root directory entries (FAT12 and FAT16 only). -f format Specify a standard (floppy disk) format. The eight standard formats are (capacities in kilobytes): 160, 180, 320, 360, 640, 720, 1200, 1232, 1440, 2880. -h heads Number of drive heads. -i info Location of the file system info sector (FAT32 only). A value of 0xffff signifies no info sector. -k backup Location of the backup boot sector (FAT32 only). A value of 0xffff signifies no backup sector. -m media Media descriptor (acceptable range 0xf0 to 0xff). -n FATs Number of FATs. Acceptable values are 1 to 16 inclusive. The default is 2. -o hidden Number of hidden sectors. -r reserved Number of reserved sectors. -s total File system size, in sectors. -u track-size Number of sectors per track. -v volume-name Volume name (filesystem name), up to 11 characters. The name should consist of only those characters permitted in regular DOS (8+3) filenames. NOTES FAT file system parameters occupy a "Boot Sector BPB (BIOS Parameter Block)" in the first of the "reserved" sectors which precede the actual file system. For reference purposes, this structure is presented below. struct bsbpb { u_int16_t bps; /* [-S] bytes per sector */ u_int8_t spc; /* [-c] sectors per cluster */ u_int16_t res; /* [-r] reserved sectors */ u_int8_t nft; /* [-n] number of FATs */ u_int16_t rde; /* [-e] root directory entries */ u_int16_t sec; /* [-s] total sectors */ u_int8_t mid; /* [-m] media descriptor */ u_int16_t spf; /* [-a] sectors per FAT */ u_int16_t spt; /* [-u] sectors per track */ u_int16_t hds; /* [-h] drive heads */ u_int32_t hid; /* [-o] hidden sectors */ u_int32_t bsec; /* [-s] big total sectors */ }; /* FAT32 extensions */ struct bsxbpb { u_int32_t bspf; /* [-a] big sectors per FAT */ u_int16_t xflg; /* control flags */ u_int16_t vers; /* file system version */ u_int32_t rdcl; /* root directory start cluster */ u_int16_t infs; /* [-i] file system info sector */ u_int16_t bkbs; /* [-k] backup boot sector */ };
|
newfs_msdos – construct a new MS-DOS (FAT) file system
|
newfs_msdos [-N] [-B boot] [-F FAT-type] [-I volid] [-O OEM] [-S sector-size] [-a FAT-size] [-b block-size] [-c cluster-size] [-e dirents] [-f format] [-h heads] [-i info] [-k backup] [-m media] [-n FATs] [-o hidden] [-r reserved] [-s total] [-u track-size] [-v volume-name] special [disktype]
| null |
newfs_msdos /dev/disk0s1 Create a file system, using default parameters, on /dev/disk0s1. newfs_msdos -f 1440 -v foo fd0 Create a standard 1.44M file system, with volume name "foo", on /dev/fd0. SEE ALSO fdisk(8), mount(8) DIAGNOSTICS Exit status is 0 on success and 1 on error. HISTORY The newfs_msdos command appeared in FreeBSD 3.0. AUTHORS Robert Nordier ⟨rnordier@FreeBSD.org⟩. macOS 14.5 July 6, 1998 macOS 14.5
|
mount_acfs
|
mount_acfs is a mount helper utility that mounts an Xsan volume on client machines. This command is normally executed by mount(8) when the -t acfs option is used. Each client file system must communicate with a File System Manager (FSM) running either locally or on a remote host. The FSM manages all the activity for the client in terms of storage allocation and metadata. Data transfers go directly between disks and the client. The mount_acfs command supports mounting file systems that are running in a cluster other than your default cluster. Your default cluster is defined with the fsmcluster(4) file or, if this doesn't exist, the default is _cluster0/_addom0. When mounting a file system in a non- default cluster, the filesystem must be qualified with the correct cluster information. The syntax is filesystem@<cluster>[/addom].
|
mount_acfs - mount an Xsan volume
|
mount_acfs [options] volume dir
|
Options supported by the mount command: -f LINUX ONLY Fakes the mount process but updates the /etc/mtab file. The mount call will fail if the mtab entry already exists. -n LINUX ONLY Mounts the filesystem without updating the /etc/mtab file. -v Verbose mode. Additional options may be specified in the /etc/fstab file or on the mount(8) command line via the -o parameter. The -o parameter should be specified only once. If multiple options are needed, they should follow the -o in a comma-separated list. ro Default: rw Mount the file system read-only. rw Default: rw Mount the file system read/write. compat32 Default: off When set, force directory offsets to fit into 31 bits and inode numbers to 32 bits. This should only be used when a problem has been identified with using the full size of the struct dirent d_off field from readdir(2) or older clients that are unable to handle large inode numbers. nodev Default: off Do not allow device special files to be accessed on the file system. noexec Default: off Do not allow the execution of programs resident on this file system. nosuid Default: off When executing programs resident on this file system, do not honor the set-user-ID and set-group-ID bits. threads=n Default: 12 Determines the number of kernel threads that are created. These threads will show up as cvfsiod processes in the output of ps. Each client file system dedicates one thread to managing a socket used to communicate with the FSM. The other threads handle unsolicited messages. This setting does not affect other kernel threads, for example, cvfsd, cvfsbufiod, cvfsflusher, cvfs_dputter. The minimum value allowed is 12. diskless={yes|no} Default: no If the diskless option is set to yes then the mount will succeed, even if the volume's disks are unavailable. Any subsequent I/O will fail until the volume's disks are visible through the Xsan portmapper. diskproxy={client|server|both} If the diskproxy option is set to client, then the mount may use a Proxy Server to do its data I/O. If the client host has SAN connectivity to some or all of the disks in the file system, then those disks will be accessed via the SAN connection, not the network. This client is then referred to as a disk proxy hybrid client. When SAN connectivity is used, the server license on the MDC will be charged for this mount. If it is desired that this client use the network for the mount, then the disks should be made unavailable to this host or the cvpaths file should be configured to prevent StorNext from using the directly attached disks. The who subcommand of cvadmin shows the type of proxy mount. If the diskproxy option is set to server, then this system will become a Proxy Server for this file system. A dpserver configuration file must exist to define the operating parameters for the Server. See dpserver(4) and sndpscfg(8) for details. A set of proxy servers may be configured in a sparse manner where each server sees only a subset of the disks in the file system. The servers make use of the "diskless" mount option. The proxy client will issue disk i/o requests to the appropriate server. No special configuration is needed on the client. A proxy server configured this way will not be able to access disks it does not see locally. If the diskproxy option is set to both, then the host acts as both a client and a server. This overcomes the issues of the sparse proxy server configuration mentioned above. This option is only supported on Linux. Note: The diskproxy option is available only on Linux and OS X systems, and the server option is available on Linux systems. The diskproxy selection on Windows clients is made through the Client Configuration utility. proxypath={balance|rotate|sticky|filestickybalance|filestickyrotate} Only used if the diskproxy option is set to client, controls the algorithm used to balance I/O across Proxy Server connections. The proxy client keeps track of bytes of I/O pending, bytes of I/O completed and the elapsed time for each I/O request. It uses these values and certain rules to determine the server that is used for subsequent I/O requests. These collected counters are decayed over time so that only the most recent (minute or so) I/O requests are relevant. There are two main components of the selection - the algorithm itself and the use of file sticky behavior. The algorithms are balance, rotate and sticky. The balance algorithm attempts to keep the same amount of time's worth of I/O outstanding on each connection. i.e. Faster links will tend to get more of the I/O. A link could be faster because a given server is more efficient or less busy. It also may be the case that network traffic over a given link uses higher speed interconnects such as 10G ethernet. The rotate algorithm attempts to keep the same number of bytes of I/O pending on each Proxy Server connection. This is similar to balance in that servers which respond more quickly to I/O requests will have the outstanding I/O bytes reduced at a more rapid pace than slower servers and will thus be used more often than slower links. The difference between balance and rotate is that with balance, higher speed links will have more bytes of I/O outstanding than slower links. In both balance and rotate, if more than one path has the best score, a pseudo-random selection among the winning paths is made to break the tie. The sticky algorithm assigns I/O to specific luns to specific Proxy Server connections. Filesticky behavior attempts to assign I/O for a given file to a specific proxy server. It does this by using the file's inode number modulo the number of servers to select a server index. Since all clients see the same inode number for a given file, all clients will select the same server. If there is more than one path to that server, then the algorithm (balance or rotate) will be used to select among the paths. Filesticky behavior is controlled through a mount option. When no proxypath mount option is specified, the balance option is selected. For mount options balance and rotate, filesticky is not selected. For filestickybalance and filestickyrotate filesticky is selected. Note: The proxypath mount option is available only on Linux, OS X, and Solaris systems. The proxypath options are selected on Windows clients through the Client Configuration utility. proxyclient_max_conns=n Only used if the diskproxy option is set to client. This parameter is used to limit the number of LAN client connections made per gateway. It overrides the server_conn_count parameter in the dpserver(4) file. However, it can only be used to decrease the number of connections. If the value of proxyclient_max_conns is equal to or larger than server_conn_count, it has no effect. The minimum value is 1 and the maximum is 16 which is also the default. proxyclient_rto=n Only used if the diskproxy option is set to client. Defines the starting value in seconds to wait for a Proxy Client I/O read request to complete before disconnecting from the Proxy Server and resubmitting the request to a different Proxy Server. If reads are completing but coming close to the configured timeout, the timeout will be increased. The minimum value is 1 second, maximum is 3600 and the default value is 15. Note: This option is available only on Linux, OS X, and Solaris systems. proxyclient_wto=n Only used if the diskproxy option is set to client. Defines the starting value in seconds to wait for a Proxy Client I/O write request to complete before disconnecting from the Proxy Server and resubmitting the request to a different Proxy Server. If writes are completing but coming close to the configured timeout, the timeout will be increased. The minimum value is 1 second, maximum is 3600 and the default value is 30. Note: This option is available only on Linux and Solaris systems. proxyclient_wrq=n Only used if the diskproxy option is set to client. Defines the number of seconds to wait for lost write requests. A lost write request is an active write through a gateway and the connection to that gateway is unexpectedly lost. These writes may or may not have been flushed to disk or even started at the time the client notices the connection is lost. The default behavior (0) is that lost writes are immediately re-queued to an available gateway. If the connection to the gateway over which the lost writes were sent is reactivated, the gateway will be queried if any writes from this connection are still active. If there are none, such as would be the case if the server unexpectedly re- booted, the client will immediately requeue all lost writes from the previous connection to this gateway. A value of -1 indicates that the client will never time out lost writes. The minimum value is -1, maximum is 2147483647 and the default is 0. Note: This option is available only on Linux systems. atimedelay={yes|no} Default: no Perform lazy atime updates. This option improves performance by waiting until closing a file before updating the atime value of the file. This reduces extra network traffic and latency linked to atime updates. nrtiotokenhold=n Default: 60 The QOS Token Hold Time (nrtiotokenhold) parameter is only applicable when using the Xsan Quality of Service (QOS) feature for real-time I/O. The parameter determines the number of seconds that a client storage pool will hold on to a non- realtime I/O token during periods of inactivity. If no I/O is performed on a storage pool within the specified number of seconds, the token will be released back to the FSM. The parameter should be specified in five second increments; if the parameter is not a multiple of five, it will be rounded up automatically. auto_concwrite={yes|no} Default: no When set to yes, allows multiple threads to write to files concurrently. Note: setting auto_concwrite=yes requires that sparse=no also be specified. Also, protect_alloc=yes is disallowed with auto_concwrite=yes. verbose={yes|no} Default: no When set to yes, mount_acfs will display configuration information about the volume being mounted. debug={yes|no} Default: no When set to yes, mount_acfs will display debugging information. This can be useful in diagnosing configuration or disk problems. mnt_retrans=n Default: 1 Indicates the number of retransmission attempts the file system will make during the execution of the mount(2) system call. Until the volume is mounted, the kernel will only retransmit messages to the FSM mnt_retrans times. This parameter works in conjunction with the mnt_recon parameter. This can help reduce the amount of time a mount command will hang during boot; see the mnt_type option. mnt_recon={hard|soft} Default: soft Controls whether after mnt_retrans attempts at contacting the FSS during the mounting and unmounting of a volume, the kernel will either give up or continue retrying forever. It is advisable to leave this option at soft so that an unresponsive FSS does not hang the client during boot. mnt_type={bg|fg} Default: fg (foreground) Setting mnt_type to bg will cause the mount to run in the background if the mount of the indicated volume fails. mount_acfs will retry the mount mnt_retry number of times before giving up. Without this option, an unresponsive FSM could cause a machine to hang during boot while attempting to mount Xsan volumes. During background mounts, all output is re-directed to /var/adm/SYSLOG. mnt_retry=n Default: Depends on mnt_type. If mnt_type==fg, mnt_retry=5 otherwise mnt_retry=500. If a mount attempt fails, retry the connection up to n times. retrans=n Default: 5 Indicates the number of attempts that the kernel will make to transmit a message to the FSM. If no response to a transmitted message arrives in the amount of time indicated by the timeout parameter, the request will be retransmitted. If the volume was mounted with the recon=soft parameter, the file system will give up after retrans attempts at sending the message to the FSM and will return an error to the user. recon={hard|soft} Default: hard This option controls whether after retrans attempts at sending a message to the FSM, the file system will give up or continue retrying forever. For hard mounted volumes, the kernel will retry the connection attempt forever, regardless of the value of the retrans field. For soft mounted volumes, the kernel will only try retrans number of times before giving up and returning an error of ETIME (62). timeout=n Default: 100 (ten seconds) The timeout value, in tenths of a second (0.1 seconds) to use when sending message to the FSM. If no response is received from the FSM in the indicated period the request is tried again. On heavily loaded systems, you may want to adjust the timeout value higher. syslog={none|notice|info|debug} Default: notice During normal operations, certain messages will be logged to the system console using the syslog facility. debug is the most verbose, with notice being reserved for critical information. It is important to note that the syslog level is global per system, not unique to each volume. Changing the level for one volume will affect all other Xsan volumes. dircachesize=n Default: 10 MB This option sets the size of the directory cache. Directory entries are cached on the client to reduce client-FSM communications during directory reads. Note: the directory cache on a client is shared across all mounted Xsan volumes. If different values of dircachesize are specified for multiple file systems, the maximum is used. When applying this setting, ensure that the system has sufficient kernel memory. Can be specified in bytes (e.g. 2097152), kilobytes (e.g. 2048k), or megabytes (e.g. 2m). cvnode_max=n Default: varies by platform. This option sets the maximum number of cvnode entries cached on the client. Caching cvnode entries improves performance by reducing Client-FSM communication. However, each cached cvnode entry must be maintained by the FSM as well. In environments with many Xsan clients the FSM may be overloaded with cvnode references. In this case reducing the size of the client cvnode cache will alleviate this issue. max_dma=n LINUX ONLY Default: varies by platform. This option tells the kernel the maximum DMA size a user process can issue. This can impact the number of concurrent I/Os the file system issues to the driver for a user I/O. There are other factors that can also limit the number of concurrent I/Os. The default is 512m on Linux. WARNING: Incorrectly setting this value may degrade performance or cause a crash/hang. max_dev=n LINUX ONLY Default: Linux: 512M with Linux DM/Multipath. 512K with StorNext multipath. This option tells the kernel the maximum I/O size to use when issuing I/Os to the underlying disk driver handling a LUN. The file system attempts to get the maximum I/O size using the IOCINFO ioctl. Since the ioctl is not always reliable, this mount option exists to override the ioctl return value. Example usage max_dev=1m or max_dev=256k. WARNING: Incorrectly setting this value may result in I/O failures or cause a crash/hang. For Linux clients, only use when recommended by Quantum Support. sparse={yes|no} Default: yes. Some utilities detect "holes" in a file and assume the file system will fill the hole with zeroes. To ensure that Xsan writes zeroes to allocated, but uninitialized areas on the disk, set sparse=yes. DISK DEVICES mount_acfs will query the local portmapper for the list of all accessible Xsan disk devices. Xsan disks are recognized by their label. This list is matched with the list of devices for each storage pool in the volume. If any disk is missing, I/O will be prohibited, and you will receive I/O errors. RECONNECT A socket is maintained for each unique Xsan client file system for sending and receiving commands to and from the FSM. If the socket connection is lost for any reason, it must be reconnected. There are two daemons involved in re-establishing the connection between an Xsan client and the FSM. The first is the socket input daemon, which is a dedicated daemon that handles all input from the FSM. The second is the reconnect daemon, which handles the work of re- establishing the logical connection with the FSM. Both of these daemons appear as cvfsd in the output from ps. Messages will be printed on the system console and to syslog during reconnect processing; the verbosity of the messages displayed can be controlled via the syslog= parameter and cvdb(8). When the socket input daemon detects that the connection has been lost, it will attempt to first connect to the fsm portmapper process, fsmpm(8). Once it has succeeded and has the port number of the fsm(8) to use, it attempts to create a new socket to the FSM using the port number returned by fsmportmapper. If no response is received from either the Xsan portmapper or the FSM, the daemon will pend for the amount of time specified by the timeout= parameter. The socket input daemon will attempt to reconnect to the FSM forever. If any of the configuration parameters in the FSM configuration file changed, then the connection will be terminated, and no further I/O will be allowed. The only recourse will be to unmount and remount the volumes. See snfs_config(5) (part of the cvfs_server product) for more information on configuring the FSM. INTERRUPTIBLE SLEEPS Whenever a process must go to sleep in the Xsan file system, the sleep is interruptible, meaning that the process can be sent a signal and the operation will fail with an error (usually EINTR). The only exceptions are when a process is executing the exit(2) system call and is closing out all open files; due to Unix limitations, processes are immune to signals at that point.
|
To mount a volume that is described by the FSS configuration file myvolume.cfg on that host: mount -t acfs myvolume /usr/tmp/foo LIMITATIONS Only the Linux and Unix platforms are supported with the mount helper mount_cvfs For Windows instructions mounting filesystemes follow the "StorNext - Getting Started" section of the help page. SEE ALSO cvfsd(8), cvdb(8), mount(8), chkconfig(8), fsmcluster(4) deviceparams(4) Xsan File System August 2022 MOUNT_ACFS(8)
|
mount_devfs
| null | null | null | null | null |
rvictl
| null | null | null | null | null |
studio
| null | null | null | null | null |
pycharm
| null | null | null | null | null |
pst
| null | null | null | null | null |
dart
| null | null | null | null | null |
flutter
| null | null | null | null | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.