Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

system_profiler(8) [osx man page]

SYSTEM_PROFILER(8)					    BSD System Manager's Manual 					SYSTEM_PROFILER(8)

system_profiler -- reports system hardware and software configuration. SYNOPSIS
system_profiler [-usage] system_profiler [-listDataTypes] system_profiler [-xml] dataType1 ... dataTypeN system_profiler [-xml] [-detailLevel level] DESCRIPTION
system_profiler reports on the hardware and software configuration of the system. It can generate plain text reports or XML reports which can be opened with System Progress and error messages are printed to stderr while actual report data is printed to stdout. Redirect stderr to /dev/null to suppress progress and error messages. The following options are available: -xml Generates a report in XML format. If the XML report is redirected to a file with a ".spx" suffix that file can be opened with System -listDataTypes Lists the available datatypes. -detailLevel level Specifies the level of detail for the report: mini report with no personal information basic basic hardware and network information full all available information -timeout Specifies the maximum time to wait in seconds for results. If some information is not available within the specified time limit then an incomplete or partial report will be generated. The default timeout is 180 seconds. Specifying a time- out of 0 means no timeout. -usage Prints usage info and examples. EXAMPLES
system_profiler Generates a text report with the standard detail level. system_profiler -detailLevel mini Generates a short report containing no personal information. system_profiler -listDataTypes Shows a list of the available data types. system_profiler SPSoftwareDataType SPNetworkDataType Generates a text report containing only software and network data. system_profiler -xml > MyReport.spx Creates a XML file which can be opened by System AUTHORS
Apple Computer, Inc. Darwin June 30, 2003 Darwin

Check Out this Related Man Page

ReportCrash(8)						    BSD System Manager's Manual 					    ReportCrash(8)

ReportCrash -- Generates crash reports SYNOPSIS
ReportCrash analyzes crashing processes and saves a crash report to disk. A crash report contains information that can help a developer diagnose the cause of a crash. ReportCrash also records the identity of the crashing process and the location of the saved crash report in the system.log and the ASL log database. ReportCrash is invoked automatically by launchd when a crash is detected. For applications and other processes running in the per-user launchd context, ReportCrash runs as a LaunchAgent and saves crash reports in the user's ~/Library/Logs/DiagnosticReports/ directory. For daemons, other processes running in the system launchd context and other privileged processes, ReportCrash runs as a LaunchDaemon and saves crash reports in the system's /Library/Logs/DiagnosticReports directory where they are only readable by admin users. If there are too many crash reports saved for a particular process, older reports will automatically be removed in order to conserve disk space. launchtl can be used to disable and re-enable crash reporting. To disable crash reporting: launchctl unload -w /System/Library/LaunchAgents/ sudo launchctl unload -w /System/Library/LaunchDaemons/ To re-enable crash reporting: launchctl load -w /System/Library/LaunchAgents/ sudo launchctl load -w /System/Library/LaunchDaemons/ For application crashes (but not background process crashes) ReportCrash will display a dialog notifying the user that the application unex- pectedly quit and offering to reopen the application or send the report to Apple. For developers, the behavior of this dialog can be adjusted using /Developer/Applications/Utilities/ which is installed as part of the developer tools. Crash reports which are sent to Apple are submitted anonymously by the SubmitDiagInfo process. The reports are used by Apple to improve its products. Users who need support should use or other authorized support channels. Developers who are ADC mem- bers should report bugs using in order to allow for two way communication between Apple and the bug reporter. More information about interpreting the contents of crash reports can be found in Technote 2123: notes/tn2004/tn2123.html SEE ALSO
launchd(8), launchd.plist(8), launchctl(8), spindump(8), SubmitDiagInfo(8) Mac OS June 1, 2019 Mac OS
Man Page