brctl(1) [mojave man page]
BRCTL(1) BSD General Commands Manual BRCTL(1) NAME
brctl -- Manage the CloudDocs daemon SYNOPSIS
brctl <command> [command-options and arguments] DESCRIPTION
brctl understands the following commands: diagnose [options] [<diagnosis-output-path>] diagnose and collect logs -M,--collect-mobile-documents[=<container>] (default: all containers) -s,--sysdiagnose Do not collect what's already part of sysdiagnose -n,--name=<name> Change the device name [<diagnosis-output-path>] Specifies the output path of the diagnosis; -n becomes useless. download <path> download a local copy of the document at this path evict <path> evict the local copy of the document at this path log [options] [<command>] -c,--color[={yes,no}] turn on or off color use -d,--path=<logs-dir> use <logs-dir> instead of default -H,--home=<home-dir> use this as the ~ prefix, to look for ~/L/ -f,--filter=<predicate> only show lines matching predicate -m,--multiline[={yes,no}] turn on or off multiple line logging -n=<number> number of initial lines to display -p,--page use paging -w,--wait wait for new logs continuously (syslog -w) -t,--shorten Shorten UUIDs, paths, etc -s,--digest Only print digest logs dump [options] [<container>] dump the CloudDocs database -o,--output=<file-path> redirect output to <file-path> -d,--database-path=<db-path> Use the database at <db-path> [<container>] the container to be dumped monitor [options] <container> use NSMetadataQuery to monitor the container -S,--scope=<scope> restrict the NSMDQ scope to DOCS, DATA, or BOTH versions [options] <path> [ALL|etags...] list the non-local versions of the document at this path. -a,--all List all non-local versions including those that are locally cached SEE ALSO
bird(8) Mac OS May 31, 2019 Mac OS
Check Out this Related Man Page
elcsd.conf(5) File Formats Manual elcsd.conf(5) Name elcsd.conf - error logging configuration file Description The file contains information used by the daemon to configure error logging for the system. The system manager maintains this file. The error logging daemon is dependent on the current order of the entries in the file. Do not change the order. The information in the file shows any defaults and describes what you can enter. A newline is used to delimit each entry in the file, a null entry consists of a newline alone, and comments begin with #. # # elcsd - errlog configuration file # { # delimiter DON'T remove or comment out! 1 # status 1-local,2-logrem,4-remlog,5-remlog+priloglocal # errlog file size limit num. of blocks /usr/adm/syserr # errlog dir. path # backup errlog dir. path / # single user errlog dir. path /usr/adm/syserr # log remote hosts errlog dir. path # remote hostname to log to } # delimiter DON'T remove or comment out! # hosts to log :S - separate file or :R - remotes file (together) remote1:S remote2:S #remote3:S # disabled remote4:S . . . The status line of the file describes where you can log error packets, also called error messages: Logs error packets locally = 1, the default. Logs error packets from a remote system or systems to the local machine = 2. Logs local and remote error packets locally = 3. Logs error packets from the local system to a remote system = 4. Logs error packets from the local system remotely and logs high priority messages locally = 5. The errorlog file size defines the maximum size of an errorlog file. If disk space is limited, you can specify the maximum number of blocks (512 bytes each) you want the errorlog file to be. If you do not specify the maximum number of blocks, the system will notify you when the file system is 98% full. The default errorlog directory path is You can direct error packets to a different directory; if you do, you must change the default for also. For further information, see If the error-logging daemon cannot write to the primary errorlog directory path, it attempts to log to the backup errorlog directory path automatically. The root directory is the default for the single-user errorlog directory path. When the system makes the transition to multiuser mode, errors logged in single-user mode are transferred to the default errorlog directory path You can direct single-user error packets to another directory. To log error packets from a remote system locally, set up an errorlog directory path on the local system. The default is Errorlog packets from remote systems can be logged to separate files or to one file. S sets up a separate errorlog file for each remote system that logs locally. R logs packets from the corresponding remote system to the file syserr.remotes. The default is S. Restrictions You must have superuser privileges to change the file. However, anyone can view the file. Files elcsd daemon messages See Also elcsd(8), eli(8), uerf(8) Guide to the Error Logger System elcsd.conf(5)