Mac OS X 10.4 Tiger requires Apple Remote Desktop v2.2
Apple Remote Desktop 1.2 is not supported in Mac OS X 10.4 "Tiger." If you install Apple Remote Desktop 1.2 on a computer running Tiger, you will find that it does not work properly. Tiger requires Apple Remote Desktop 2.2.
So Ive been a bit confused dealing with ssh keys or something else, who knows maybe someone can help.
I run a set of computers on a network which are all running mac os x lion. I have a lion server serving them all up. I run remote desktop to update them and do anything else "tech"
support... (13 Replies)
Are Mac OS X 10.4.11 Tiger passwords only stored in /var/db/shadow/hash? Or is it also used in NetInfo?
The reason I am asking is because I wonder if I edit the file in /var/db/shadow/hash and replace the hash inside with my own, will it change the password?
Thanks. (0 Replies)
I was installing gdm on the terminal application and my ISP disconnected. When I reconnected and tried to continue the installation, I got the following message:
Waiting for lock on... (0 Replies)
Question:
Can I run a UNIX executable on Mac OS X Tiger?
If so, how is it done?
Background:
I FTP'd my schools UNIX server some C++ code and header files. Then I used Telnet to get g++ to compile them.
I then FTP'd the UNIX executable back to my PowerBook G4.
I've already... (4 Replies)
ReportCrash(8) BSD System Manager's Manual ReportCrash(8)NAME
ReportCrash -- Generates crash reports
SYNOPSIS
ReportCrash
DESCRIPTION
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/com.apple.ReportCrash.plist
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
To re-enable crash reporting:
launchctl load -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
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/CrashReporterPrefs.app 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 http://www.apple.com/support or other authorized support channels. Developers who are ADC mem-
bers should report bugs using http://bugreporter.apple.com 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: http://developer.apple.com/tech-
notes/tn2004/tn2123.html
SEE ALSO launchd(8), launchd.plist(8), launchctl(8), spindump(8), SubmitDiagInfo(8)Mac OS June 1, 2019 Mac OS